Contact at mumbai.academics@gmail.com or 8097636691
Responsive Ads Here

Saturday, 3 February 2018

Portable Cloud Services Using TOSCA(2012)


Portable Cloud Services Using TOSCA(2012)


ABSTRACT:
Underneath all the hype, the essence of cloud computing is the industrialization of IT. Similar to mass production lines in other industries (such as the auto industry), cloud computing standardizes offered services and thus increases automation significantly. Consequently, enterprises are increasingly utilizing cloud technology; however, major challenges such as portability, standardization of service definitions, and security remain inadequately addressed. The ability to move cloud services and their components between providers ensures an adequate and cost-efficient IT environment and avoids vendor lock-in. Research has already addressed movability and migration on a functional level.1,2 However, no one has yet examined cloud service portability with regard to management and operational tasks, which are a significant and increasing cost factor. One reason is the lack of an industry standard for defining composite applications and their management. Without an appropriate standardized format, ensuring compliance, trust, and security  the biggest area of critique preventing the cloud’s wider adoption is difficult. Dealing with these challenges in industry and research has the potential to bring cloud computing to the next level. Here, we present how the portable and standardized management of cloud services is enabled through the Topology and Orchestration Specification for Cloud Applications (TOSCA),3 a recently initiated standardization effort from OASIS. We show how TOSCA plans  which capture the management aspects of cloud services in a reusable way  use existing workflow technologies and research results to facilitate the portable, automated, and reusable management of cloud services throughout their life cycle.
EXISTING SYSTEM:
In the existing system portability, standardization of service definitions and security remain inadequately addressed. The ability to move cloud services and their components between providers ensures an adequate and cost-efficient IT environment and avoids vendor lock-in. The movability and migration on function level with regard to management and operational tasks, which are a significant and increasing cost factor.
Disadvantages:
1) Portability, standardization of service definitions, and security is not effective in existing system.
2) The industry standard for defining composite applications is not efficient.
PROPOSED SYSTEM:
In the offering phase, the cloud service provider creates a cloud service offering based on a service template, adding all provider- and offering-specific information. This includes aspects such as pricing and specific technical information such as IP address range and application configurations. Finally, the offering is published in a service catalog. In the subscription and instantiation phase, the cloud service consumer browsing the service catalog can select and subscribe to the respective offering. The consumer customizes the service through points of variability (for example, selecting “small,” “medium,” or “large” for the service’s size), signs a contract, and accepts the offering’s terms and conditions. This subscription process triggers the instantiation of the cloud service instance. The cloud management platform aggregates all the required resources from the common resource pools, for example infrastructure components, and automatically deploys, installs, and configures the service’s necessary pieces.
Advantages:
1) The management aspects of cloud services in a reusable way.
2) Use existing workflow technologies and research results to facilitate the portable, automated, and reusable management of cloud services throughout their life cycle.
MODULES
1) Cloud Computing Reference Architecture (CCRA):
2) Cloud Service Life Cycle:
3) Topology and Orchestration Specification:
4) Planning Of Topology:
5) Portability of plan:
MODULES DESCRIPTION:
1) Cloud Computing Reference Architecture (CCRA):
Cloud Computing Reference Architecture (CCRA) defines three main roles typically encountered in any cloud computing environment: the cloud service creator, cloud service and cloud service consumer. the service creator develops cloud services; the service provider runs those services, and provides them to service consumers, which can also be IT systems. Consumers can be billed for all (or a subset of) their interactions with cloud services and the provisioned service instances.
2) Cloud Service Life Cycle:
In the definition phase, all management knowledge required for the specific cloud service in particular, how to instantiate is captured in a service template. This knowledge includes information about the cloud service’s internal structure along with operational and management aspects to build, manage, and terminate cloud services.  In the offering phase, the cloud service provider creates a cloud service offering based on a service template, adding all provider- and offering-specific information. This includes aspects such as pricing and specific technical information such as IP address range and application configurations. In instantiation phase, the cloud service consumer browsing the service catalog can select and subscribe to the respective offering. The consumer customizes the service through points of variability signs a contract, and accepts the offering’s terms and conditions.   In the life cycle’s production phase, the cloud management platform uses management plans to manage the service instance for compliance with the service-level agreements (SLAs) negotiated at   subscription time.
3) Topology and Orchestration Specification:
TOSCA describes composite applications and their management in a modular and portable fashion. It thus defines service templates that contain  a cloud service’s topology   and its operational aspects to deploy, terminate, and manage . The creator of a cloud service captures its structure in a service  topology graph with nodes and relationships. TOSCA specifies the metamodel for types and templates   that is, the language for defining them. Concrete types aren’t part of the specification and must be standardized by the respective domain expert groups. Nodes in particular define a range of information to deploy, terminate, and manage the cloud service: instance states represent the node’s internal state during production as part of the topology
4) Planning Of Topology:
Plans use the cloud service topology in three ways: First, plans orchestrate the management interfaces and operations defined in TOSCA nodes. Operations are described in the Web Services Description Language (WSDL), Representational State Transfer (REST), or scripts that implement particular management operations on the respective node. Second the service template is instantiate. Second, plans can inspect the topology model to access a service’s nodes and relationships. This enables flexible plans whose behavior is based on the topology and changes therein the respective nodes. Finally, plans read and write a service’s instance information that is, the node’s instance state, such as properties containing credentials, IP addresses, and so on.
5) Portability of plan:
TOSCA plans’ portability is inherited from the workf low language and engines used. In TOSCA, these services are explicitly described in the nodes as operations. For operations referencing external services, portability isn’t a problem. TOSCA models contain myriad references to files, such as those with additional TOSCA definitions, plans, and other artifacts. TOSCA allows service creators to gather into plans those activities necessary to deploy, manage, and terminate the described cloud service.
HARDWARE REQUIREMENTS:-
ü Processor             -Pentium –III
ü Speed                             -    1.1 Ghz
ü RAM                    -    256 MB(min)
ü Hard Disk            -   20 GB
ü Floppy Drive       -    1.44 MB
ü Key Board            -    Standard Windows Keyboard
ü Mouse                  -    Two or Three Button Mouse
ü Monitor                -    SVGA
SOFTWARE REQUIREMENTS:-
v   Operating System          : Windows95/98/2000/XP
v   Application  Server       : Tomcat5.0/6.X                                        
v   Front End                      : Java, JSP
v    Script                            : JavaScript.
v   Server side Script          : Java Server Pages.
v   Database                        : MYSQL

No comments:

Post a Comment