PORTABLE CLOUD SERVICES USING TOSCA

PORTABLE CLOUD SERVICES USING TOSCA

For cloud services to be portable, their management must also be portable to the targeted environment, as must the application components themselves. Here, the authors show how plans in the Topology and Orchestration Specification for Cloud Applications (TOSCA) can enable portability of these operational aspects 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.

EXISTING SYSTEM:
We present how the portable and standardized management of cloud services is enabled through the Topology and Orchestration Specification for Cloud Applications (TOSCA), 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.

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.

Software Requirements:
Front End – JSP
Language – Java
Back End – MySQL Server
Windows XP

Hardware Requirements:
RAM : 512 Mb
Hard Disk : 80 Gb
Processor : Pentium IV

Comments are closed.