International Journal of Advanced Scientific and Technical Research Available online on http://www.rspublication.com/ijst/index.html

Issue 4 volume 5, Sep.-Oct. 2014 ISSN 2249-9954

______________________________ VENDOR LOCK-IN TO THE META CLOUD FOR CHANGING THE WIND Swati Sugoor

Mrs. Y Prathima

Student, Department of CSE,

Assistant Professor, MRIET

Hyderabad, Andhra Pradesh, India

Hyderabad, Andhra Pradesh, India

Abstract- The cloud computing allows the

IJ

ST

business customer to scale up and down their resource usage based on needs. The cloud computing paradigm has achieved widespread adoption in recent year. The emergence of yet more cloud offerings from a multitude of service providers calls for a Meta cloud to smoothen the edges of the jagged cloud landscape. This Meta cloud could solve the vendor lock-in problems that current public and hybrid cloud users face. In this paper we introduce the concept of a Meta cloud consisting of a combination of design time and runtime Components. Meta cloud abstracts away from technical Incompatibilities of existing offerings, thus mitigating vendor lock-in. It helps to find the right set of cloud services for a particular use case, and supports an applications Initial deployment and runtime migration. Here we migrate the one cloud service provider to another by identifying the cheats of provider.

Firstly, even though availability of public clouds is generally high, eventual outages still occur. If this is the case, businesses locked into such a cloud are essentially at a standstill until the cloud is back on Secondly, public clouds providers generally have no guarantee towards the Particular service level agreements, i.e., Businesses locked into a cloud have no guarantees that this cloud will continue to provide the required Quality of Service (QoS) tomorrow. Thirdly, the terms of service of most public cloud providers forces the Provider to change pricing of their service at any time. Hence, a Business locked in a cloud has no mid- or long-term control over their own IT costs. At the core of all of these problems, we can identify a need for businesses to permanently monitor the cloud they are using, and to be able to rapidly “change horses", i.e., migrate to a different cloud if monitoring discovers problems or estimations foresee issues in the future. However, migration is currently far from trivial. A plethora of cloud providers is flooding the market with a confusing body of services, such as computer services e.g., Amazon Elastic Compute Cloud (EC2) and VMware vCloud, or key-value stores, e.g., Amazon Simple Storage Service (S3). Evidently, some of these services are conceptually similar to each other, others are vastly different, but all of them are, ultimately, technically incompatible and follow their own ways but not standards. To further complicate the situation, many companies are not only building on public clouds , but combine with their own private cloud, leading to so-called hybrid cloud setups. A Meta cloud is useful for identifying the cheats of the provider by lock in to the Meta cloud. In this paper we can upload the data and we can send a mail to the end user.

Keywords— Cloud computing, Meta cloud, Quality of service, Knowledge based systems, automated deployment, and proxy. I.INTRODUCTION The cloud computing paradigm has found widespread adoption throughout the last years. The cloud computing is successful because of the possibility of using services on demand with the pay as you use. Because of low costs and high flexibility, migrating to the cloud is indeed compelling. Despite the obvious advantages of cloud computing, many companies hesitate to move into the cloud, mainly because of concerns related to availability of service, data lock-in, and legal uncertainties. Lock-in which we have used here has some problems.

________________________________________ R S. Publication, [email protected] Page 38

International Journal of Advanced Scientific and Technical Research Available online on http://www.rspublication.com/ijst/index.html

Issue 4 volume 5, Sep.-Oct. 2014 ISSN 2249-9954

______________________________ The Meta cloud includes the runtime components and development component. To some extent, the meta cloud can be realized based on a combination of existing tools and concepts, part of which are presented in the previous section. The main components of the Meta cloud, depicted in Figure 1, show the components of Meta data.

II. MATERIALS AND METHODS USED

ST

Inside the Meta Cloud

IJ

Meta Cloud API. The Meta cloud API is the component of Meta cloud. For customers, the use of the Meta cloud API prevents their application from being hard-wired to a specific cloud service offering. The Meta cloud API is a development component of Meta cloud.

Resource Templates. The Resource template is the development component of the Meta cloud. Developers describe the cloud services necessary to run an application using resource templates. The Meta cloud resource templates are created using a simple domain-specific language (DSL), allowing for the concise specification of required resources. The resource Templates is used for reusing the components in different projects. Moreover, resource templates allow for the definition of constraints based on costs, component proximity, and geographical distribution. Migration/Deployment Recipes. This is the development component of the Meta cloud. Deployment recipes are an important ingredient for automation in the Meta cloud infrastructure. The recipes used for c o n t r o l l i n g t h e d e p l o y m e n t of

Application and establishing links between related components. Migration recipes go one step further and describe how to migrate an application during runtime, migrating storage functionality from one service provider to another. Recipes only describe initial deployment and migration, the actual process is executed by the provisioning strategy and the Meta cloud proxy using aforementioned automation tools. Meta Cloud Proxy. The cloud proxy is the component of the cloud provider. The Meta cloud provides proxy objects, which are deployed with the application and run on the provisioned cloud resources. The Meta cloud proxy acts as a mediator between the application and the cloud provider. The proxies are used for exposing the Meta cloud API to the application, transform application requests into cloud provider specific requests, and forward them to the respective cloud services. The proxy provides means to execute deployment and migration recipes triggered by the Meta cloud's provisioning strategy. The communication between proxies and the Meta cloud is kept at a minimum to avoid the high load and computational bottlenecks. Proxies do not run inside the Meta cloud.

________________________________________ R S. Publication, [email protected] Page 39

International Journal of Advanced Scientific and Technical Research Available online on http://www.rspublication.com/ijst/index.html

Issue 4 volume 5, Sep.-Oct. 2014 ISSN 2249-9954

______________________________ Resource Monitoring. The resource monitoring component is the runtime component of the Meta cloud. The resource monitoring is responsible for receiving data collected by Meta cloud proxies. These received data are preprocessed and then stored in the knowledge base for further processing. This helps to generate comprehensive QoS information of cloud service providers and the particular services they are providing, including response time, availability, and more service specific quality statements.

The Meta cloud use case is used for vendor lock-in to the Meta cloud. This Meta cloud works as follows. In the Meta cloud for initial deployment, the developer submits the applications resource template to the Meta cloud. It not only specifies the three types of the cloud but also their necessary properties and how they are dependent on each other. Each resource can be named in the template. This allows for referencing during the deployment, runtime, and migration. The resource template also shows direct connection between the web service compute instances and the message queue service. The rich information of resource template provides helps the provisioning strategy component that make decision about cloud service ranking. We can explain the working principle of initial deployment with a web search analog, in which resource template as queries and cloud service provider as QOS. After the resource deployment and resources are determined, the Meta cloud deploys the application, together with the Meta proxy. During runtime the Meta proxy acts as a mediator between the application components and Amazon cloud resource and sends to monitoring data to the resource monitoring within the Meta cloud. The next when we send to the monitoring data. It helps the data to refine the application’s resource template and the providers overall QOS values and both are stored in the knowledge base. The provisioning strategy regularly checks the updated information, which might trigger the migration. To avoid Meta cloud lock-in, the community must introduce the new ideas and creates a open Meta cloud with added values for all customer and broad support for different provide and implementation technologies.

ST

Provisioning Strategy. The provisioning strategy component is the runtime component of the Meta cloud. The main task of this component is to match an application's cloud service requirements to actual cloud service providers. It is also helpful to find and rank cloud services based on data in the knowledge base. At runtime, this component is useful for finding the reasons about whether migration of a resource to another resource provider is beneficial based on new insights into the application's behavior and updated cloud provider QoS or pricing data. Decisions of the provisioning strategy result in executing customer defined Deployment or migration scripts.

Meta Cloud Use Case.

IJ

Knowledge Base. The knowledge base is the runtime component of the Meta cloud. The knowledge base serves as store for data about cloud provider services, their pricing and QoS, and information necessary to estimate migration costs. Customer provided resource templates and migration/deployment recipes are stored in the knowledge base as well. Also, the knowledge base indicates which cloud providers are eligible for a certain customer. The knowledge base acts as storage for the data which are collected after processing the data. The Meta cloud can help to mitigate vendor lock-in and promises transparent use of cloud computing services. Most of the basic technologies necessary to realize the Meta clouds are already out there, yet lack integration. The integration of these state of the art tools promises a huge leap towards the Meta cloud, though. For avoiding meta cloud lock-in it is critical that the community drives the ideas, to create a truly open meta cloud with added value for all customers with broad support for different Providers and implementation technologies.

II. PROPOSED SYSTEM Here, we introduce the concept of a Meta cloud that incorporates design time and runtime components. This Meta cloud would abstract away from existing offerings, technical incompatibilities, thus mitigating vendor lock-in. It helps users find the right set of cloud services for a particular use case and supports an application’s initial deployment and runtime migration.

________________________________________ R S. Publication, [email protected] Page 40

International Journal of Advanced Scientific and Technical Research Available online on http://www.rspublication.com/ijst/index.html

Issue 4 volume 5, Sep.-Oct. 2014 ISSN 2249-9954

______________________________ IV.RESULT The result of this paper is Migratating the one service provider to another from identifying the cheats of the provider. The cheats of the provider can be identified by the following modules those are registration, login, file upload, migrate cloud, and send mail. The result of this paper is still in the Execution stage.

Send Mail: The Mail will be sent to the end user along with file decryption key, so as to end user can download the file. Owners send the mail to the users who are registered earlier while uploaded the file into the correct cloud.

V.CONSLUSION

ST

In this paper, we have introduced the Meta cloud for identifying the cheats of providers. The Meta cloud can help mitigate vendor lock-in and promises transparent use of cloud computing services. Most of the basic technologies necessary to realize the Meta cloud already exist, yet lack integration. Thus, integrating these state-of-the-art tools promises a huge leap toward the Meta cloud. To avoid Meta cloud lock in, the community must drive the ideas and create a truly open Meta cloud with added value for all customers and broad support for different providers and implementation technologies.

IJ

REFERENCES

Registration: To execute this register first. In this module if TTP (trusted third party) or provider) have to register first, to access the data base.

project we have to a User or Owner or CSP (cloud service then only he/she has

Login: After registration we have to login by giving their username and password. File Upload: In this module Owner uploads a file into cloud, before it gets uploaded; it subjects into Validation by TTP. Then TTP sends the file to CSP.CSP decrypt the file by using file key. If CSP tries to modify the data of the file, He can’t modify it. If he made an attempt the alert will go to the Owner of the file. It results in the Cloud Migration. Migrate Cloud: The advantage of this Meta cloud is, if we are not satisfied with one CSP, we can switch over to next cloud. So that we are using two clouds at a time. In second cloud, that cannot be modify/corrupt the real data.

1. M. Armbrust et al., “A View of Cloud Computing,” Comm. ACM, vol. 53, no. 4, 2010, pp. 50–58.

2. B.P. Rimal, E. Choi, and I. Lumb, “A Taxonomy and Survey of Cloud Computing Systems,” Proc. Int’l Conf. Networked Computing and Advanced Information Management, IEEE CS Press, 2009, pp. 44–51. 3. J. Skene, D.D. Lamanna, and W. Emmerich, “Precise Service Level Agreements,” Proc. 26th Int’l Conf. Software Eng. (ICSE 04), IEEE CS Press, 2004, pp. 179–188. 4. Q. Zhang, L. Cheng, and R. Boutaba, “Cloud Computing: State-of-the-Art and Research Challenges,” J. Internet Services and Applications, vol. 1, no. 1, 2010, pp. 7–18. 5. M.D. Dikaiakos, A. Katsifodimos, and G. Pallis, “Minersoft: Software Retrieval in Grid and Cloud Computing Infrastructures,” ACM Trans. Internet Technology, vol. 12, no. 1, 2012, pp. 2:1–2:34. Benjamin Satzger is an assistant professor in the Distributed Systems Group at the Vienna University of Technology. Contact him at [email protected].

________________________________________ R S. Publication, [email protected] Page 41

International Journal of Advanced Scientific and Technical Research Available online on http://www.rspublication.com/ijst/index.html

Issue 4 volume 5, Sep.-Oct. 2014 ISSN 2249-9954

______________________________ Waldemar Hummer is a PhD student in the Distributed Systems Group at the Vienna University of Technology. Contact him at [email protected]. Christian Inzinger is a PhD student in the Distributed Systems Group at the Vienna University of Technology. Contact him at [email protected].

IJ

ST

Philipp Leitner is a postdoctoral researcher in computer science in the Distributed Systems Group at the Vienna University of Technology. Contact him at [email protected].

________________________________________ R S. Publication, [email protected] Page 42