Winds of change from vendor lock-in to meta cloud review 1

1

Winds of Change: From Vendor Lock-In to the Meta Cloud

Ramachandrapuram,Tirupati-517561

PRIYADARSHINI INSTITUTE OF TECHNOLOGY

SUBMITTED BY:N.NAWAZ KHAN (103P1A0548)M.GOWRI SANKAR (103P1A0547)K. SREENUVASULU (103P1A0532)T.MUKESH (103P1A0563)

UNDER THE GUIDANCE OF:R.ROOPA, M.TechAsst. ProfessorPDIT

pdit, tpt

2pdit, tpt

CONTENTS Abstract Introduction Existing system Disadvantages Proposed system Advantages Hardware requirements Software requirements Architecture Modules Uml diagrams Execution slides Conclusion & future work

pdit, tpt 3

ABSTRACT The cloud computing paradigm has achieved

widespread adoption in recent years. Low costs and high flexibility make migrating to the

cloud compelling. Despite its obvious advantages, however, many

companies hesitate to “move to the cloud,” mainly because of concerns related to service availability, data lock-in, and legal uncertainties.

Lock in is particularly problematic, even though public

cloud availability is generally high, outages still occur.

pdit, tpt 4

INTRODUCTION A need for businesses to permanently monitor the cloud they’re

using and be able to rapidly “change horses” that is, migrate to a different cloud if they discover problems or if their estimates predict future issues.

Myriad cloud providers are flooding the market with a confusing body of services, including compute services such as the Amazon Elastic Compute Cloud

This meta cloud would abstract away from existing offerings’ technical incompatibilities, 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.

pdit, tpt 5

EXISTING SYSTEM

Cloud providers are flooding the market with a confusing body of services, including computer services such as the Amazon Elastic Compute Cloud (EC2) and VMware v Cloud, or key-value stores, such as the Amazon Simple Storage Service (S3).

Some of these services are conceptually comparable to each other, whereas others are vastly different, but they’re all, ultimately, technically incompatible and follow no standards but their own.

pdit, tpt 6

DISADVANTAGES

Its success is due largely to customers’ ability to use services on demand with a pay-as-you go pricing model, which has proved convenient in many aspects.

Low costs and high flexibility make migrating to the cloud compelling.

pdit, tpt 7

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.

pdit, tpt 8

Reasons to migrate• Expected cost saving• Better efficiency and time to market• Increased security• Greater access to data• Decreased or less infrastructure maintenance• Creates innovation• Greater storage capacity• Minimum contract terms• Ability to scale• Increased control over SLA’s

pdit, tpt 9

ADVANTAGES

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.

pdit, tpt 10

HARDWARE REQUIREMENTS

Processor - Pentium –IIISpeed - 1.1 GHzRAM - 256 MB (min)Hard Disk - 20 GBFloppy Drive - 1.44 MBKey Board - Standard Windows KeyboardMouse - Two or Three Button MouseMonitor - SVGA

pdit, tpt 11

SOFTWARE REQUIREMENTS

•Operating System : Windows95/98/2000/XP •Application Server : Tomcat5.0/6.X • Front End : HTML, Java, Jsp• Scripts : JavaScript.•Server side Script : Java Server Pages.•Database : My sql•Database Connectivity : JDBC.

pdit, tpt 12

ARCHITECTURE

13pdit, tpt

Meta Cloud API

The meta cloud API provides a unified programming interface to abstract from the differences among provider API implementations.

Resource Templates

Developers describe the cloud services necessary to run an application using resource templates.

They can specify service types with additional

proper ties, and a graph model expresses the interrelation and functional dependencies between services.

14pdit, tpt

Migration and Deployment Recipes Allows for controlled deployment of the application, including installing packages, starting required services, managing package and application parameters, and establishing links between related components.

Meta Cloud ProxyThe meta cloud provides proxy objects, which are deployed with the application and run on the provisioned cloud resources. They serve as mediators between the application and the cloud provider.

15pdit, tpt

Resource MonitoringOn an application’s request, the resource monitoring component receives data collected by meta cloud proxies about the resources they’re using. The component filters and processes the data and then stores them on the knowledge base for further processing.

Provisioning StrategyThe provisioning strategy component primarily matches an application’s cloud service requirements to actual cloud service providers. It finds and ranks cloud services based on data

in the knowledge base.

pdit, tpt 16

Knowledge BaseThe knowledge base stores data about cloud provider services, their pricing and QoS, and information necessary to estimate migration costs. It also stores customer-provided resource templates and migration or deployment recipes.

pdit, tpt 17

MODULES

1.Registration2.Login3.File Upload 4.Migrate Cloud5.Send Mail

pdit, tpt 18

Registration

In this module if an User or Owner or TTP(trusted third party) or CSP(cloud service provider) have to register first, then only he/she has to access the data base.

pdit, tpt 19

Login

In this module, person have to login, they should login by giving their username and password .

pdit, tpt 20

File Upload

In this module Owner uploads a file(along with meta data) 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 cant modify it. If he made an attempt the alert will go to the Owner of the file. It results in the Cloud Migration.

pdit, tpt 21

Migrate Cloud

The advantage of this meta cloud is ,if we are not satisfy with one CSP, we can switch over to next cloud. so that we are using two clouds at a time. In second cloud, their cant modify/corrupt the real data, if they made an attempt, the will fail.

pdit, tpt 22

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. Owner send the mail to the users who are registered earlier while uploaded the file into the correct cloud.

23pdit, tpt

UML DIAGRAMSWHAT IS UML? Unified Modeling Language is a

standardized, general-purpose modeling language in the field of software engineering.

The Unified Modeling Language includes a set of graphic notation techniques to create visual models of object-oriented software-intensive systems.

pdit, tpt 24

TYPES OF UML DIAGRAMS USED IN

THIS PROJECT

• CLASS DIAGRAM• USECASE DIAGRAM• SEQUENCE DIAGRAM• COLLABORATION DIAGRAM• ACTIVITY DIAGRAM• STATE CHART DIAGRAM• DATA FLOW DIAGRAM

pdit, tpt 25

CLASS DIAGRAM• It shows a set of class interfaces

and collaborations and their relationships.• These diagrams addresses strategic

design view of a system, it includes active classes addresses of a system.

pdit, tpt 26

pdit, tpt 27

USECASE DIAGRAM

• An usecase diagram shows a set of courses and actors and their relation ships.

• Usecase diagram represents the static view of a system.

• These diagrams are essentially important in organizing and modeling the behavior of the system

pdit, tpt 28

pdit, tpt 29

INTERACTION DIAGRAMS

• Both sequence and collaboration diagrams are called the interaction diagrams.

• An interaction diagram shows an interaction consisting of set of objects and their relationships.

• The interaction diagrams are developed based on the objects for the purpose of sending and receiving messages.

pdit, tpt 30

SEQUENCE DIAGRAM

pdit, tpt 31

COLLABORATION DIAGRAM

pdit, tpt 32

SEQUENCE DIAGRAM

pdit, tpt 33

COLLABORATION DIAGRAM

pdit, tpt 34

ACTIVITY DIAGRAM

• An activity diagram is a special kind of state chart diagram and it is like a flow chart that shows flow from one activity to another activity.

• The activity diagram addresses the dynamic view of a system.

pdit, tpt 35

pdit, tpt 36

STATE CHART DIAGRAM

• It shows a state machine consisting of states, transition events and activities.

• State chart diagram addresses the dynamic view of a system.

• They are especially important in modeling the behavior of an interface class or collaboration and emphasize the event ordered behavior of an object.

pdit, tpt 37

pdit, tpt 38

Data flow diagram• A data flow diagram is a graphical

representation of the "flow" of data through an information system, modeling its process aspects.

pdit, tpt 39

DATA FLOW

DAIGRAM

pdit, tpt 40

EXECUTION SLIDES

pdit, tpt 41

pdit, tpt 42

pdit, tpt 43

pdit, tpt 44

pdit, tpt 45

pdit, tpt 46

pdit, tpt 47

pdit, tpt 48

pdit, tpt 49

pdit, tpt 50

pdit, tpt 51

pdit, tpt 52

pdit, tpt 53

pdit, tpt 54

pdit, tpt 55

pdit, tpt 56

pdit, tpt 57

pdit, tpt 58

pdit, tpt 59

pdit, tpt 60

pdit, tpt 61

Conclusion• 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.

• 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.

pdit, tpt 62

• Fog computing :• Fog Computing is a paradigm that extends Cloud

computing and services to the edge of the network. • Fog provides data, compute, storage, and application

services to end-users. • The distinguishing Fog characteristics are its

proximity to end-users, its dense geographical distribution, and its support for mobility.

• Services are hosted at the network edge or even end devices such as set-top-boxes or access points.

• By doing so, Fog reduces service latency, and improves QoS, resulting in superior user-experience.

• Thanks to its wide geographical distribution the Fog paradigm is well positioned for real time big data and real time analytics.

pdit, tpt 63

References• M. Armbrust et al., “A View of Cloud Computing,”

Comm. ACM, vol. 53, no. 4,2010, pp. 50–58.• 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.

• J. Skene, D.D. Lamanna, and W. Emmerich, “Precise Service Level Agreements,”Proc. 26th Int’l Conf. SoftwareEng. (ICSE 04), IEEE CS Press, 2004, pp. 179–188.

• 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.

• M.D. Dikaiakos, A. Katsifodimos, and G. Pallis, “Minersoft: Software Retrieval in Grid and Cloud Computing Infrastructures,”ACM Trans. Internet Technology.