Académique Documents
Professionnel Documents
Culture Documents
LOUD COMPUTING is the delivery of computing as a service rather than a product, whereby shared resources, software, and information are provided to computers and other devices as a utility over a network (typically the Internet). Although cloud computing is an emerging field of computer science, the idea has been around for a few years. It's called cloud computing because the data and applications exist on a "cloud" of Web servers. It is believed to have been invented by Joseph Carl Robnett Licklider in the 1960s. Since the sixties, cloud computing has developed along a number of lines, with Web 2.0 being the most recent evolution. However, since the internet only started to offer significant bandwidth in the nineties, cloud computing for the masses has been something of a late developer. This is a new computing model and not a new technology. Cloud Computing vendors combine virtualization (one computer hosting several virtual servers), automated provisioning (servers have software installed automatically), and Internet connectivity technologies to provide the service. These are not new technologies but a new name applied to a collection of older (but updated) technologies that are packaged, sold and delivered in a new way. In this model customers plug into the cloud to access IT resources which are priced and provided on-demand. In any corporation, responsibilities of a senior executives include making sure that all of their employees have the right hardware and software they need to do their jobs. Buying computer for everyone isn't enough; right software or software licenses(SL) need to be bought too, to give employees the tools they require. Whenever theres a new hire, more software/SL needs to be bought. It's so stressful and requires huge piles of money. CLOUD COMPUTING comes to rescue here. It provides an supreme alternative to the companys management. Instead of installing a suite of software for each computer, they could only load one application. That application would allow workers to log into a Webbased service which hosts all the programs the user would need for his or her job. Users could access cloud based applications through a web browser or a light weight desktop or mobile app while the business software and data are stored on servers at a remote location. These Remote machines owned by another company would run everything from e-mails to word processing to complex data analysis programs. At the foundation of cloud computing is the broader concept of infrastructure convergence and shared services. This type of data centre environment allows enterprises to get their applications up and running faster, with easier manageability and less maintenance, and
enables IT to more rapidly adjust IT resources (such as servers, storage, and networking) to meet fluctuating and unpredictable business demand. In a cloud computing system, there's a significant workload shift. Local computers no longer have to do all the heavy lifting when it comes to running applications. The network of computers that make up the cloud handles them instead. Thus, hardware and software demands on the user's side decrease. The only thing the user's computer needs to be able to run is the cloud computing system's interface software, which can be as simple as a Web browser, and the cloud's network takes care of the rest. Since, the clients data resides on someone elses server(s), cloud computing depends on the reputation and trust on service providers, cloud application providers strive to give the same or better service and performance than if the software programs were installed locally on enduser computers. Thus, delivered over an Internet connection, the cloud replaces the company data center or server providing the same service. Cloud Computing is simply IT services sold and delivered over the Internet and holds the potential to change the face of IT industry.
II
III
Front End
Back End
Client's computer
Interface Software
Storage Devices
Middleware
he goal of a cloud-based architecture is to provide some form of elasticity, the ability to expand and contract capacity on-demand. The implication is that at some point additional instances of an application will be needed in order for the architecture to scale and meet demand. Cloud engineering is the application of engineering disciplines to cloud computing. It brings a systematic approach to the high level concerns of commercialization, standardization, and governance in conceiving, developing, operating and maintaining cloud computing systems. It is a multidisciplinary method encompassing contributions from diverse areas such as web, systems, software, performance, information, security, platform, risk and quality engineering. The biggest challenge in cloud computing is the fact that there's no fixed standard or single architectural method. Therefore, it's best to view cloud architectures as a set of approaches, each with its own examples and capabilities.
IV
Broadly, a cloud computing system can be simply classified into two parts, Front end and Back end. They are connected to each other through a network (usually Internet). The front end is the side that the computer user, or client, sees. It includes client's computer (or computer network) and the application required to access the cloud computing system. Not all cloud computing systems have the same user interface. Services like Web-based e-mail programs leverage existing Web browsers like Internet Explorer or Firefox. Other systems have unique applications that provide network access to clients. The back end is the "cloud" section of the system. On the back end of the system are the various computers, servers and data storage systems that create the "cloud" of computing services. In theory, a cloud computing system could include practically any computer program you can imagine, from data processing to video games. Usually, each application will have its own dedicated server. A central server administers the system, monitoring traffic and client demands to ensure everything runs smoothly. It follows a set of rules called protocols and uses a special kind of software called middleware. Middleware allows networked computers to communicate with each other. Most of the time, servers don't run at full capacity. That means there's unused processing power going to waste. It's possible to fool a physical server into thinking it's actually multiple servers, each running with its own independent operating system. The technique is called server virtualization. By maximizing the output of individual servers, server virtualization reduces the need for more physical machines. If a cloud computing company has a lot of clients, there's likely to be a high demand for a lot of storage space. Some companies require hundreds of digital storage devices. Cloud computing systems need at least twice the number of storage devices it requires to keep all its clients' information stored. That's because these devices, like all computers, occasionally break down. A cloud computing system must make a copy of all its clients' information and store it on other devices. The copies enable the central server to access backup machines to retrieve data that otherwise would be unreachable. Making copies of data as a backup is called redundancy.
Cloud providers will need to consider and meet different QoS parameters of each individual consumer as negotiated in specific SLAs. To achieve this, Cloud providers can no longer continue to deploy as negotiated in specific SLAs. To achieve this, Cloud providers can no longer continue to deploy traditional system centric resource management architecture that do not provide incentives for them to share their resources and still regard all service requests to be of equal importance. Instead, market-oriented resource management is necessary to regulate the supply and demand of Cloud resources at market equilibrium, provide feedback in terms of economic incentives for both Cloud consumers and providers, and promote QoSbased resource allocation mechanisms that differentiate service requests based on their utility.
VI
VII
VIII
Cloud Service: - It consists of access manager, firewall and queue, which based on the
number and type of messages it contains determines the number of nodes to be provisioned. They host the application components that process messages. Additionally, the elastic queue can analyze environmental information, such as the overall utilization of the elastic infrastructure or resource prices. This is used to delay less critical messages by reducing the number of handling compute nodes and to prioritize the business critical functionality if the overall infrastructure utilization is high.
Cloud Storage: - Cloud storage is a model of networked online storage where data is
stored in virtualized pools of storage which are generally hosted by third
IX
parties. Hosting companies operate large data centers, and people who require their data to be hosted buy or lease storage capacity from them. The data center operators, in the background, virtualizes the resources according to the requirements of the customer and expose them as storage pools, which the customers can themselves use to store files or data objects. Physically, the resource may span across multiple servers. Cloud storage has the same characteristics as cloud computing in terms of agility, scalability, elasticity and multi-tenancy.
XI
CLOUD SERVICES
Software as a Service
Platform as a Service
Infrastructure as a Service
Fig.4.Classification of Cloud
Platform as a Service: - The size of service, budget, or staff of a corporation does not limit
IT when the platform for custom services is as readily available and broadly deployable as
XII
the web. With PaaS, one can develop new applications or services in the cloud that do not depend on a specific platform to run, and can be made widely available to users through the Internet. PaaS delivers cloud-based application development tools, in addition to services for testing, deploying, collaborating on, hosting, and maintaining applications. PaaS can be used to create multi-tenant applicationsthat is, services accessed by many users simultaneously. The open architecture of PaaS can support integration with legacy applications and interoperability with on-site systems-important considerations, because government operates in a mixed IT world. Interoperability gives you the flexibility to take advantage of cloud benefits while retaining data and applications on site as needed. Facilities Supported: Business Intelligence Application Deployment Virtual Environment Database Integration Development & Testing
Software as a Service: - SaaS makes use of a cloud computing infrastructure to deliver one
application to many users, regardless of their location, rather than the traditional model of one application per desktop. It allows activities to be managed from central locations in a one-tomany model, including architecture, pricing, partnering, and management characteristics. SaaS helps an organization with Lowers expenses associated with software acquisitions in near term. IT budget from capital expense to operational expense. Limited IT resources can deploy and maintain needed hardware and software. IT staff can be refocused from deployment and maintenance to high-priority projects. Facilities Supported: Human Resource Social network BackUp & Recovery Email and Office Productivity Document Management Sales Legal Financials Collaboration CRM
XIII
XIV
PUBLIC CLOUD: - The name public in the public cloud comes from the fact that
application is hosted on the Hosting Providers location (Vendors). Applications, storage, and other resources are made available to the general public by a service provider. Though it is hosted in shared system, each resource operates in silo and encrypted securely. Public cloud services may be free or offered on a pay-per-usage model. There are limited service providers like Microsoft, Google etc owns all Infrastructures at their Data Center and the access will be through Internet mode only. No direct connectivity proposed in Public Cloud Architecture. With Public Cloud all the resources and the services are dynamically added and removed (Scalable) based on the usage. Public cloud is more advantages for Small and Medium scale industries since we are going to pay for the resources which we are going to use and specifically the hardware and the bandwidth are going to be maintained by the hosting provider.
PRIVATE CLOUD: - Private cloud is cloud infrastructure operated solely for a single
organization, whether managed internally or by a third-party and hosted internally or externally. In this form, the cloud is deployed with in a corporate firewall and runs on
XV
premise IT infrastructure. Private cloud is more expensive compared to the public cloud since the operating and bandwidth costs are to be maintained by the organization, but this cloud is more secure than the public cloud. They have attracted criticism because users "still have to buy, build, and manage them" and thus do not benefit from less hands-on management, essentially "[lacking] the economic model that makes cloud computing such an intriguing concept". However, Private Cloud provides more benefits to the corporate by capitalizing on the Data Security and Corporate Governance and provides administrators more control over the operating environment.
XVI
COMMUNITY CLOUD: - Community cloud shares infrastructure between several organizations from a specific community with common concerns (security, compliance, jurisdiction, etc.), whether managed internally or by a third-party and hosted internally or externally. The costs are spread over fewer users than a public cloud (but more than a private cloud), so only some of the cost savings potential of cloud computing are realized. This type of cloud is specifically used for organizations that are shared such as different government organizations. In this case, non-government organizations will not have access to this cloud. The cloud could be located in-house, or on public cloud based on the needs of the organization.
XVII
he applications of cloud computing are practically limitless. With the right middleware, a cloud computing system could execute all the programs a normal computer could run. Potentially, everything from generic word processing software to customized computer programs designed for a specific company could work on a cloud computing system. But, why would anyone want to rely on another computer system to run programs and store data? Here are just a few reasons: Location and Device Independent: - Clients would be able to access their applications and data from anywhere at any time. They could access the cloud computing system using any computer linked to the Internet. Data wouldn't be confined to a hard drive on one user's computer or even a corporation's internal network. Reduces Capex: - It could bring hardware costs down. Cloud computing systems would reduce the need for advanced hardware on the client side. A corporation need not to buy the fastest computer with the most memory, because the cloud system would take care of those needs. Instead, an inexpensive computer terminal will be enough. The terminal could include a monitor, input devices like a keyboard and mouse and just enough processing power to run the middleware necessary to connect to the cloud system. You wouldn't need a large hard drive because you'd store all your information on a remote computer.
Easier Collaboration: - Corporations that rely on computers have to make sure they have the right software in place to achieve goals. Cloud computing systems give these organizations company-wide access to computer applications. The companies don't have to buy a set of software (or SL) for every employee. Instead, the company could pay a metered fee to a cloud computing company.
XVIII
Reduces Physical Costs: - Servers & digital storage devices take up space. Some companies rent physical space to store servers and databases because they don't have it available on site. Cloud computing gives these companies the option of storing data on someone else's hardware, removing the need for physical space on the front end. Easier and Cheaper Maintenance: - Corporations might save money on IT support. Streamlined hardware would, in theory, have fewer problems than a network of heterogeneous machines and operating systems. Higher Processing Power: - If the cloud computing system's back end is a grid computing system, then the client could take advantage of the entire network's processing power. Often, scientists and researchers work with calculations so complex that it would take years for individual computers to complete them. On a grid computing system, the client could send the calculation to the cloud for processing. The cloud system would tap into the processing power of all available computers on the back end, significantly speeding up the calculation. Automated Upgradation: - SaaS clients need not to worry about the upgrading softwares every the and now. Instead of user spending the money of upgrading softwares, the service provider will automatically do it.
XIX
XX
in large part to the private and public sectors' unease surrounding the external management of security-based services. It is the very nature of cloud computing-based services, private or public, that promote external management of provided services. This delivers great incentive to cloud computing service providers to prioritize building and maintaining strong management of secure services. Security issues have been categorized into sensitive data access, data segregation, privacy, bug exploitation, recovery, accountability, malicious insiders, management console security, account control, and multi-tenancy issues. Solutions to various cloud security issues vary, from cryptography, particularly public key infrastructure (PKI), to use of multiple cloud providers, standardization of APIs, and improving virtual machine support and legal support. AVAILABLE BANDWIDTH: - As all the data needs to be downloaded or uploaded on third party servers, the user needs to have very fast internet connection to avoid delays.
XXI
XXII
loud computing is revolutionizing the way your business will work in the next several years. Although its still an evolving paradigm, cloud computing is an infrastructure which can not only help streamline processes across all departments, but also increase customer satisfaction and loyalty and increase revenue and profit margins. So, what does this mean to the future of information technology? How will the role of IT, and the roles within IT, change as a result of the changing landscape of the technology it administers? What new applications--and resulting markets--are enabled by the "big rethink"? Software packaging will be application focused, not server focused: For some time now, the focus of system deployment has been the server, not the application. In the highly customized world of IT systems, development before virtualization and the cloud, servers were acquired, software was installed upon the servers in very specific ways, and the entire package was managed and monitored largely from the perspective of the server (e.g. what processes are running, how much CPU is being used, etc.). As OS functionality begins to get wrapped into application containers, or moved onto the hardware circuitry itself, the packaging begins to be defined in terms of application architecture, with monitoring happening from the perspective of software services and interfaces rather than the server itself. These packages can then be moved around within data centers, or even among them, and the focus of management will remain on the application. That's not to say that no one will be watching the hardware. Infrastructure operations will always be a key function within data centers. However, outside of the data center operations team, it will matter less and less. Enterprise and Solutions architectures will align better with Cloud Offerings: The cloud may not stifle differentiation in software systems. As end users select SaaS, applications to run core pieces of their business, meet integration and operations needs from the cloud and generally move from systems providers to service providers, the need to reduce customization will be strong. This is both to reduce costs and strengthen system survivability in the face of constant feature changes on the underlying application system. The organization, however, is an artifact of a time when applications were tightly coupled to the hardware on which they were deployed. In such a static deployment model, expertise was needed to customize these technologies in pursuit of meeting specific service-level goals. When you decouple software deployment from underlying hardware, it begins to allow for a re-evaluation of these operational roles. Today, most companies are already in a transition in this respect, with increasing reliance on roles like "virtualization administrator" and "operations specialist" to fulfill changing needs.
XXIII
The changing landscape of software development platforms will result in new philosophies of software architecture, deployment, and operations: As the cloud computing evolve, in future, two things will happen. First, agility will become king in large-scale systems development for classes of applications ranging from web applications to data processing to core business systems. From the service provider's perspective, agility will come in terms of frequency in which they can release features and fixes. Agility from the perspective of the enterprise developer will come through the ways in which they can rapidly iterate over the write-build-test cycle. Agility from the perspective of the entrepreneur, in that data center services are now a credit card away. Second, project management whether for commercial offerings or for custom enterprise applications, will experience rapid changes. Agile programming and project management methods make a ton of sense in the cloud, as do service-oriented approaches to software and systems architecture. Project managers wondering what cloud computing will do to their day-to-day jobs should consider what happens if development can outpace a Gant chart. The need for tactical systems administrators will be reduced: In future, the tactical system administrator is going to be largely (though probably not entirely) go away because of Automation. Most of the tasks such an admin does day to day are highly automatable: provisioning, failure recovery, scaling, infrastructure management and so on. These administrators are among the last "clerks" in business, and a result of the unfortunate fact that IT has been excellent at automating everything in business--except IT. However administration will still be required for "Private Cloud Operations Center", a concept similar to the network operations centers that exist in many Fortune 500 companies today. There, the administrator would monitor overall performance of applications running in the cloud (on both internal and external resources), as well as monitoring the performance of the cloud providers themselves. IT Jobs are going to experience radical changes: In future, as more and more businesses shift towards cloud computing, there individual requirement for IT and hardware professionals will reduce and instead, the demand for professionals in Cloud vendors will increase.
CONCLUSIONS
fter studying the topic carefully and deeply and going through the report, I have come to the conclusion that Cloud Computing, may not be too
XXIV
successful right now. But it has a bright future and would be regarded as one of the most path breaking concept of all time. As the bandwidth offered by Internet Service Providers (ISPs) will increase with advancement of technology, more and more people and businesses will shift towards cloud computing. The technology would be specially beneficial for government use, since it will terminate the lengthy government procedures of tendering and bidding. The concept will improve efficiency and will be provide boost to mobile computing. Already Google, Microsoft, Apple etc, the big technology companies are fighting it hard for the lucrative pie in the market of cloud computing. Once the security and legal concerns are done away with, cloud computing is going to explode.
APPENDIX
XXV
1. CSPs: - Cloud Service Providers 2. ISPs: - Internet Service Providers 3. SL: - Software License 4. SaaS: - Software as a Service 5. PaaS: - Platform as a Service 6. IaaS: - Infrastructure as a Service 7. CDN: - Content Delivery Network 8. CRM: - Customer Relationship management 9. QOS: - Quality of Service 10. SLA: - Service Level Agreement
XXVI