Call for Papers - Journal of Electrical Systems (JES), E-ISSN: 1112-5209, ind...
Final Presentation.pptx
1. Candidate Details
Name: BRIJESH PANDEY
Enrolment no.: PhD/15/CSE/1798
Faculty: Engineering & Technology Field: Computer Science
& Engg.
Research Topic: Modeling Variability and Integration of web
services for achieving application portability in cloud computing
Supervisor 1: Dr. Sudhir Singh Soam (IET, Lucknow)
Supervisor 2: Dr. Dharmendra Kumar Yadav (MNNIT,
Prayagraj)
Registration Date: 20, July, 2015
1/4/2024 1
Ph.D Oral Examination
2. Outline
Motivation
Introduction
Contribution
Background
Proposed Work 1
Proposed Work 2
Proposed Work 3
Proposed Work 4
Conclusion
Future Work
1/4/2024 2
Ph.D Oral Examination
3. Motivation
Cloud
Computing
Enormous impact on the organizations
for the usage of IT resources
Ease of accessing computing resources
Pay-as-Per use billing model
1/4/2024 3
Ph.D Oral Examination
4. Motivation
Challenges for
Cloud
Computing
Vendor Lock-in
Portability and
Interoperability challenges
Non-standardization of
Application Programming
Interface (API)
Variation in Software
Stacks
1/4/2024 4
Ph.D Oral Examination
5. Motivation
Remedies for
Challenges
Component based Architectures
Advent use of Containerization
Cloud applications integrate
multiple interacting components
1/4/2024 5
Ph.D Oral Examination
6. Motivation
Research
Problem
Selection and Configuration of an
appropriate runtime environment for
each application component was done
manually
Orchestrating the management of
application components on top of the
selected environment was done
manually
1/4/2024 6
Ph.D Oral Examination
7. Motivation
Research Gap
Analysis
The tool was required where the
developer shall only describe:
Components forming an application
Dependencies occurring between them
Software support needed by each
component
1/4/2024 7
Ph.D Oral Examination
8. Motivation
Research Gap
Analysis
The tool shall automatically:
Select and configure the run
time environment for each
application component
Orchestrate the application
management on top of the
selected environment
1/4/2024 8
Ph.D Oral Examination
9. Motivation
Challenges for new
Scenario
Deployment scenario where more than
one viable solutions are present to
deploy the given application
component on selected environment
Automate multi-platform deployment
of portable software
Automated provisioning of services
such as message queues, databases,
load balancers and etc
1/4/2024 9
Ph.D Oral Examination
10. Introduction
Modeling Variability
and Integration of
Web Service
Component for
Achieving Application
Portability in Cloud
Computing
Application portability
TOSCA
Docker
TosKer
Toskeriser
1/4/2024 10
Ph.D Oral Examination
11. Contributions
Modeling
Variability and
Integration of Web
Service
Component for
Achieving
Application
Portability in Cloud
Computing
Prioritizing non-functional requirement
in the cloud computing domain
Performing application portability
pertaining TOSCA in cloud computing
environment
Orchestration of multi-component
application using Docker containers
Orchestration of multi-component
application using TOSKER
1/4/2024 11
Ph.D Oral Examination
12. Background
Requirement
Engineering
Feasibility Study
Elicitation of Requirement and
Analysis
Specifications of Software
Requirement
Validation of Software Requirements
Management of Software
Requirements
1/4/2024 12
Ph.D Oral Examination
14. Background
Cloud Computing
Cloud refers to a network or internet.
It is something which is present at
remote location
Applications such as e-mail, web
conferencing and etc. all run on cloud
Cloud computing refers to
manipulating, configuring and
accessing the application online
It offers online data storage,
infrastructure and application
1/4/2024 14
Ph.D Oral Examination
17. Background
Service Models
Infrastructure as a service (IaaS)
Virtual machines, servers and storage
network
Platform as a service (PaaS)
Database, web servers and deployment
tools
Software as a service (SaaS)
CRM, Email, games and virtual desktop
1/4/2024 17
Ph.D Oral Examination
27. Proposed Work 1
Prioritizing
Non-functional
Requirements in
Cloud
Computing
Domain
Parameters for modeling NFR in
Cloud Computing:
Portability (OS images, hardware,
etc)
Reliability (MTTF, MTTR and
etc)
Availability (Uptime percentage,
User location and etc)
Efficiency (Throughput,
Workload, Response Time)
1/4/2024 27
Ph.D Oral Examination
28. Proposed Work 1
Prioritizing
Non-functional
Requirements in
Cloud
Computing
Domain
Proposed Approach
NFR Priority Binary
Code
Security Very High 0
Portability Very High 1
Reliability High 10
Agility High 11
Availability HIGH 100
1/4/2024 28
Ph.D Oral Examination
31. Proposed Work 1
Prioritizing
Non-functional
Requirements in
Cloud
Computing
Domain
Evaluation criteria was basically
divided into two main categories:
• Product/Service Value Creation
• Vendor Performance
1/4/2024 31
Ph.D Oral Examination
32. Proposed Work 1
Prioritizing
Non-functional
Requirements in
Cloud
Computing
Domain
Product/Service Value Creation
Sub categories
• Service Portfolio
• Service Experience
• Integration
• Economic factors
• Disruption Potential
1/4/2024 32
Ph.D Oral Examination
34. Proposed Work 1
Prioritizing
Non-functional
Requirements in
Cloud
Computing
Domain
Best Cloud Service Providers as for
NFR mentioned
Amazon Web Services
Google Cloud Platform
Microsoft Azure
IBM Cloud Platform
Digital Ocean
1/4/2024 34
Ph.D Oral Examination
36. Proposed Work 1
Prioritizing
Non-functional
Requirements
in Cloud
Computing
Domain
Implementation
The prototype is developed using
the J2EE Java-based enterprise
edition as Servlet and JSP Java
server pages
Tomcat server is used as a web
server to serve Servlet and JSP
MySQL database is used for
storing cloud and selector
information
1/4/2024 36
Ph.D Oral Examination
37. Proposed Work 1
Prioritizing
Non-functional
Requirements
in Cloud
Computing
Domain
Implementation
HTML, CSS, JAVASCRIPT, and
MATERIALCSS are used for
front-end part designing
Net beans - IDE is used to
develop the software, and
MySQL Workbench is used as a
database client
1/4/2024 37
Ph.D Oral Examination
47. Proposed Work 2
Application
Portability
Pertaining TOSCA
in Cloud
Computing
Environment
Scenario for Application
Portability in Cloud Computing
Customer changing the cloud
service provider
1/4/2024 47
Ph.D Oral Examination
48. Proposed Work 2
Application
Portability
Pertaining TOSCA
in Cloud
Computing
Environment
Scenario for Application
Portability in Cloud Computing
Multiple Providers Providing
Cloud Service to the Customer
1/4/2024 48
Ph.D Oral Examination
49. Proposed Work 2
Application
Portability
Pertaining TOSCA
in Cloud
Computing
Environment
Scenario for Application
Portability in Cloud Computing
Customer Links One Cloud
Service to Another Cloud Service
1/4/2024 49
Ph.D Oral Examination
50. Proposed Work 2
Application
Portability
Pertaining TOSCA
in Cloud
Computing
Environment
Scenario for Application
Portability in Cloud Computing
Customer Binding its Capabilities
with Cloud Services
1/4/2024 50
Ph.D Oral Examination
51. Proposed Work 2
Application
Portability
Pertaining TOSCA
in Cloud
Computing
Environment
Scenario for Application
Portability in Cloud Computing
The Departure of In-house
Application Code of Customer to
Cloud Services
1/4/2024 51
Ph.D Oral Examination
52. Proposed Work 2
Application
Portability
Pertaining TOSCA
in Cloud
Computing
Environment
TOSCA Service Template
Node Template
Relationship Template
Service Template
Topology Model
Topology Template
1/4/2024 52
Ph.D Oral Examination
53. Proposed Work 2
Application
Portability
Pertaining TOSCA
in Cloud
Computing
Environment
TOSCA Relationships Types
tosca.relationships.AttachesTo
for attaching a container to a
volume
tosca.relationships.ConnectsTo
for connecting containers and/or
components
1/4/2024 53
Ph.D Oral Examination
54. Proposed Work 2
Application
Portability
Pertaining TOSCA
in Cloud
Computing
Environment
TOSCA Relationships Types
tosca.relationships.HostedOn
for hosting components on
containers/components
tosca.relationships.DependsOn
for deployment dependencies
1/4/2024 54
Ph.D Oral Examination
62. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Virtual Machine Based
Virtualization
Virtual Machine Monitors
(VMM)
Software Based Virtualization
Hardware Assisted Virtualization
Virtual Box
VMware Workstation Player
1/4/2024 62
Ph.D Oral Examination
63. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Containers
Containers are a form of
operating system virtualization.
Container contains all the
necessary executables, binary
code, libraries, and configuration
files.
1/4/2024 63
Ph.D Oral Examination
64. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Containers
Containers do not
contain operating system
images.
In larger application
deployments, multiple
containers may be
deployed as one or more
container clusters.
1/4/2024 64
Ph.D Oral Examination
65. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Benefits of Containers
Less overhead
Increased portability
More consistent operation
Greater efficiency
Better application development
1/4/2024 65
Ph.D Oral Examination
66. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Containers Based
Virtualization
Development of Linux brought
into the idea that to keep process
isolated from the host file system
and for the purpose of solving
’chroot’ command was created
1/4/2024 66
Ph.D Oral Examination
67. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Containers Based
Virtualization
Namespaces are also the key
feature of Linux for supporting
lightweight virtualization.
1/4/2024 67
Ph.D Oral Examination
68. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Containers Based
Virtualization
Six Namespaces in Linux are:
Mount Namespace
UNIX Timestamp Sharing (UTS)
Interprocess Communication
(IPC)
Process ID (PID)
Network Namespace
User Namespace
1/4/2024 68
Ph.D Oral Examination
69. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Docker utilization to
achieve Application Portability
Build a button that enables any
application to be built and
deployed on any server, anywhere
Docker is an open-source
platform that allows applications
to be deployed inside the
software containers
1/4/2024 69
Ph.D Oral Examination
70. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Docker utilization to
achieve Application Portability
Google, Microsoft, Amazon, and
many others have added support
for Dockers to their platforms
and contributing to the project
To run an application on any
platform, the first step is to bring
out its binaries, scripts, and data
1/4/2024 70
Ph.D Oral Examination
71. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Docker utilization to
achieve Application Portability
The entire application is
packaged inside the pack in
Docker, which is known as image
These images, in turn, are stored
in registries
There is a default registry
available that can be explored
using a browser or Docker search
command
1/4/2024 71
Ph.D Oral Examination
72. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Docker utilization to
achieve Application Portability
The search command returns
repositories containing many
images, but one is distinguished
as ”latest”
An ID uniquely identifies every
image in Docker
An image is run to bring out the
virtualization
1/4/2024 72
Ph.D Oral Examination
73. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Docker utilization to
achieve Application Portability
Docker creates a container and
puts the application from the
image inside it
To run an image, the user can
specify the image ID, repository
name with tag, or repository
name with default tag ”latest”
1/4/2024 73
Ph.D Oral Examination
74. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Docker Orchestration Tool and
API
Docker Swarm
Docker Machine
Docker Daemon
1/4/2024 74
Ph.D Oral Examination
75. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Docker Orchestration Tool and
API
Docker platform uses three
separate APIs to allow interaction
with third-party applications:
Docker Hub API
Docker Registry API
Docker Remote API
1/4/2024 75
Ph.D Oral Examination
76. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Resource Utilization Graph
1/4/2024 76
Ph.D Oral Examination
77. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Resource Utilization Graph
1/4/2024 77
Ph.D Oral Examination
78. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Resource Utilization Graph
1/4/2024 78
Ph.D Oral Examination
79. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Resource Utilization Graph
1/4/2024 79
Ph.D Oral Examination
80. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Resource Utilization Graph
1/4/2024 80
Ph.D Oral Examination
81. Proposed Work 3
Orchestration of
Multi-Component
Application using
Docker Containers
Resource Utilization Graph
1/4/2024 81
Ph.D Oral Examination
82. Proposed Work 4
Orchestration of
Multi-Component
Application using
TosKer
TOSKER
• TosKer is an open-source
solution for enhancing the
current support for cloud
applications
• TOSCA-based representation for
multi-component applications
which can be used to specify only
the application components and
the software support they need
1/4/2024 82
Ph.D Oral Examination
83. Proposed Work 4
Orchestration of
Multi-
Component
Application
using TosKer
TOSKER
Tools for automatically
completing/updating TOSCA
application specifications by
discovering and including Docker-
based runtime environments
providing the software support
needed by the application
components
Engine for orchestrating TOSCA
applications on top of Docker-
enabled hosts
1/4/2024 83
Ph.D Oral Examination
84. Proposed Work 4
Orchestration of
Multi-
Component
Application
using TosKer
TosKer Architecture
1/4/2024 84
Ph.D Oral Examination
85. Proposed Work 4
Orchestration of
Multi-
Component
Application
using TosKer
TosKer Architecture (User
Interface)
User Interface feeds TosKer with
the necessary input
The TosKer includes a CSAR
packaging the TOSCA
specification of a multicomponent
application together with all
artifacts needed to realize its
management and a sequential plan
1/4/2024 85
Ph.D Oral Examination
86. Proposed Work 4
Orchestration of
Multi-
Component
Application
using TosKer
TosKer Architecture (Utilities
Modules)
TOSCA Parser
Plan Checker
State Storage
Orchestrator
Container Manager
Software Manager
Volume Manager
1/4/2024 86
Ph.D Oral Examination
87. Proposed Work 4
Orchestration of
Multi-
Component
Application
using TosKer
TOSCA Nodes Types
tosker.nodes.Container for Docker
containers
tosker.nodes.Volume for Docker
volumes
tosker.nodes.Software for the
software components building an
application
1/4/2024 87
Ph.D Oral Examination
88. Proposed Work 4
Orchestration of
Multi-Component
Application using
TosKer
Toskeriser
TOSKERISER takes as input a file
containing a TOSCA service
specifications in ”CSAR/YAML”
format
TOSKERISER produces the
”CSAR/YAML” file containing the
completed ”TOSCA” application
specifications.
1/4/2024 88
Ph.D Oral Examination
89. Proposed Work 4
Orchestration of
Multi-Component
Application using
TosKer
TOSKERISER Architecture
1/4/2024 89
Ph.D Oral Examination
90. Proposed Work 4
Orchestration of
Multi-Component
Application using
TosKer
Proposed Architecture
1/4/2024 90
Ph.D Oral Examination
91. Proposed Work 4
Orchestration of
Multi-Component
Application using
TosKer
Sequence of Steps for
Proposed Model
Identify the application
components
Categorize them as specific and
generic
Use TOSKER and apply
TOSKERISER for completing
the TOSCA specification of a
specific component
1/4/2024 91
Ph.D Oral Examination
92. Proposed Work 4
Orchestration of
Multi-Component
Application using
TosKer
Sequence of Steps for Proposed
Model
Invoke Docker finder to map the
docker images on the docker hub
by applying the best effort
adaption for the generic
component
Merge the components and
execute the application
1/4/2024 92
Ph.D Oral Examination
93. Proposed Work 4
Orchestration of
Multi-Component
Application using
TosKer
Evaluation Metrics
Deployment of New Application
Initial Effort Required to Deploy
the Ping-pong Application
KPI TOSKERISER Docker-based
Lines of code 141 89
Files 16 3
Languages 2 TOSCA, bash 3 Dockerfile,
Docker
Compose, bash
1/4/2024 93
Ph.D Oral Examination
94. Proposed Work 4
Orchestration of
Multi-Component
Application using
TosKer
Evaluation Metrics
Deployment of New Application
Initial Effort Required to Deploy
the Ping-pong Application
1/4/2024 94
Ph.D Oral Examination
95. Proposed Work 4
Orchestration of
Multi-Component
Application using
TosKer
Evaluation Metrics
Initial Effort Required to Deploy
the Sock-shop Application
KPI TOSKERISE
R
Docker-
based
Lines of
code
303 268
Files 26 8
Languages 2 TOSCA,
bash
3 Dockerfile,
Docker
Compose,
bash
1/4/2024 95
Ph.D Oral Examination
96. Proposed Work 4
Orchestration of
Multi-
Component
Application
using TosKer
Evaluation Metrics
Initial Effort Required to Deploy
the Sock-shop Application
1/4/2024 96
Ph.D Oral Examination
97. Proposed Work 4
Orchestration of
Multi-
Component
Application
using TosKer
Evaluation Metrics
Initial Effort Required to Deploy
WordPress Hotel Reservation
System Application
KPI TOSKERISE
R
Docker-
based
Lines of
code
117 62
Files 24 6
Languages 2 TOSCA,
bash
3 Dockerfile,
Docker
Compose,
bash
1/4/2024 97
Ph.D Oral Examination
98. Proposed Work 4
Orchestration of
Multi-
Component
Application
using TosKer
Evaluation Metrics
Initial Effort Required to Deploy
WordPress Hotel Reservation
System Application
1/4/2024 98
Ph.D Oral Examination
99. Proposed Work 4
Orchestration of
Multi-
Component
Application
using TosKer
Maintenance of Third Party
Existing Application
Effort Needed to Update the
Deployment of the Sock-Shop
Application, in order to provide its
frontend with the new version of
npm it requires
KPI TOSKERISE
R
Docker-
based
Lines of
code
1 1
Files 1 1
Languages 1 TOSCA 2 Dockerfile,
bash
1/4/2024 99
Ph.D Oral Examination
100. Proposed Work 4
Orchestration of
Multi-
Component
Application
using TosKer
Maintenance of Third Party Existing
Application
Effort Needed to Update the
Deployment of the Sock-Shop
Application, in order to provide its
frontend with the new version of npm
it requires
1/4/2024 100
Ph.D Oral Examination
101. Proposed Work 4
Orchestration of
Multi-
Component
Application
using TosKer
Maintenance of Third Party
Existing Application
Effort Needed to Update the
Deployment of the WordPress
Hotel reservation Application by
Changing its Theme (front end
change)
KPI TOSKERIS
ER
Docker-
based
Lines of
code
1 1
Files 1 1
Languages 1 TOSCA 2
Dockerfile,
bash
1/4/2024 101
Ph.D Oral Examination
102. Proposed Work 4
Orchestration of
Multi-
Component
Application
using TosKer
Maintenance of Third Party
Existing Application
Effort Needed to Update the
Deployment of the WordPress
Hotel reservation Application by
Changing its Theme (front end
change)
1/4/2024 102
Ph.D Oral Examination
103. Conclusion
Modeling
Variability and
Integration of Web
Service
Component for
Achieving
Application
Portability in Cloud
Computing
Concluding Remarks
Docker based orchestration is more
suited to a simple application
But when it comes to complex
application, the TOSKER based
orchestration holds the edge
In case there are more specific
components than the service has to be
made from scratch using the tool
TOSKERISER, which is embedded in
TOSKER based orchestration
1/4/2024 103
Ph.D Oral Examination
104. Future Work
Modeling
Variability and
Integration of Web
Service
Component for
Achieving
Application
Portability in Cloud
Computing
Future Work
Feature-based models have been
very flexible and showing
competency in modeling large
variability of information.
Therefore, future research should
keep this modeling technique on
top of the charts
1/4/2024 104
Ph.D Oral Examination
105. Future Work
Modeling
Variability and
Integration of Web
Service
Component for
Achieving
Application
Portability in Cloud
Computing
Future Work
Deployment on a server or
laptop is something very
incompatible to the PaaS
environment and is more like
working on the IaaS layer. To
compose this with an
automated IaaS approach it
could be beneficially suited
for the future scope
1/4/2024 105
Ph.D Oral Examination
106. Future Work
Modeling
Variability and
Integration of Web
Service
Component for
Achieving
Application
Portability in Cloud
Computing
Future Work
Further, the future scope could always
be replacement and updating of codes
and databases that are already defined
within the TOSCA standard
1/4/2024 106
Ph.D Oral Examination
107. References
Modeling
Variability and
Integration of Web
Service
Component for
Achieving
Application
Portability in Cloud
Computing
References
Brogi A, Rinaldi L, Soldani J. TosKer: A synergy between
TOSCA and Docker for orchestrating multi-component
applications. Softw Pract Exper. 2018;1–19.
Antonio Brogi, Davide Neri, Luca Rinaldi, Jacopo Soldani
Orchestrating incomplete TOSCA applications with
Docker Science of Computer Programming 166 (2018)
194–213.
Jacopo Soldani, Tobias Binz , Uwe Breitenbucher, Frank
Leymann, Antonio Brogi Tosca Mart: A method for
adapting and reusing cloud applications The Journal of
Systems and Software 113 (2016) 395–406.
https://di-unipi-socc.github.io/tosker-types/. The
TosKer Open Source Environment. Antonio Brogi,
Davide Neri, Luca Rinaldi, Jacopo Soldani.
https://github.com/di-unipi-socc/TosKer
https://github.com/di-unipi-socc/DockerFinder
1/4/2024 107
Ph.D Oral Examination
108. Published Papers
Modeling
Variability and
Integration of Web
Service
Component for
Achieving
Application
Portability in Cloud
Computing
Dissemination of the Research Work
1. “Application Portability Pertaining TOSCA
in cloud computing environment" published
in International Journal of Advance Trends in
Computer Science and Engineering (
IJATCSE) ISSN 2278-3091 Volume -8 No-5,
October 2019 by Brijesh Pandey,
Dr.D.K.Yadav and Dr.S.S.Soam. (Scopus
Indexed) Page number 2252-2259
2. "Modeling the frameworks for evaluating
the Non-functional requirements affecting
application efficacy in a cloud computing
domain” published in International Journal of
Engineering and Advanced Technology
(IJEAT) ISSN 2249-8958 Volume-9, Issue-1,
October 2019 by Brijesh Pandey,
Dr.S.S.Soam and Dr.D.K.Yadav. (Scopus
Indexed). Page number 1924-1930
1/4/2024 108
Ph.D Oral Examination
109. Published Papers
Modeling
Variability and
Integration of Web
Service
Component for
Achieving
Application
Portability in Cloud
Computing
Dissemination of the Research Work
3. "Achieving Application Portability in cloud
computing environment"' published in
International Journal of Innovative
Technology and Exploring Engineering
(IJITEE) ISSN 2278-3075 Volume-8 Issue-12,
October 2019 by Brijesh Pandey,
Dr.S.S.Soam and Dr.D.K.Yadav. (Scopus
Indexed).Page number 3359-3369
4. “Orchestration of Multi-Component
application using TosKer "published in
International Journal of Grid and Distributed
Computing (IGDC) ISSN 2005-4262 Volume-
13 No-1, (2020), pp. 840-850 by Brijesh
Pandey, Dr.D.K.Yadav and Dr.S.S.Soam.
(ESCI Indexed).
1/4/2024 109
Ph.D Oral Examination
