Cloud computing

Dominion Draft

The version here is a snapshot taken 2009-08-22. The § lists the variances from the English lede in sofar as ai-integration.biz is viewed as a cloud-computing package.

• It is not metered, users provide their own resources and use my software with hosting bought on the open market although third parties may provide metered hosting and service based on it.
• Infrastructure sharing is limited to that needed for base internet technology such as IPV6 and DNS but this extends to higher levels too as needed to realize such initiatives as semantic web.
• It is service based but most are expected to get and use the software either on their own or using third party software service providers obtained via our public job shop market although I also provide service personally.

English Lede

Some of the vendors providing Cloud computing services

Cloud computing is a style of computing in which dynamically scalable and often virtualized resources are provided as a service over the Internet. Users need not have knowledge of, expertise in, or control over the technology infrastructure in the "cloud" that supports them.

Gartner defines five attributes of Cloud Computing:

• It is service-based.
• It is scalable and elastic. I.e., it is able to add and remove infrastructure as needed.
• It uses shared infrastructure to build economies of scale.
• It is metered and users pay according to usage.
• Most importantly, of course, it uses Internet technologies.

The concept generally incorporates combinations of the following:

• infrastructure as a service (IaaS)
• platform as a service (PaaS)
• software as a service (SaaS)
• Other recent (ca. 2007–09) technologies that rely on the Internet to satisfy the computing needs of users. Cloud computing services often provide common business applications online that are accessed from a web browser, while the software and data are stored on the servers.

The term cloud is used as a metaphor for the Internet, based on how the Internet is depicted in computer network diagrams and is an abstraction for the complex infrastructure it conceals.

The first academic use of this term appears to be by Prof. Ramnath K. Chellappa (currently at Goizueta Business School, Emory University) who originally defined it as a computing paradigm where the boundaries of computing will be determined by economic rationale rather than technical limits.

Brief

Comparisons

Cloud computing can be confused with:
1) grid computing - "a form of distributed computing whereby a 'super and virtual computer' is composed of a cluster of networked, loosely coupled computers, acting in concert to perform very large tasks".
2) utility computing - the "packaging of computing resources, such as computation and storage, as a metered service similar to a traditional public utility such as electricity" and
3) autonomic computing - "computer systems capable of self-management".

Indeed, many cloud computing deployments as of 2009Template:DMCA depend on grids, have autonomic characteristics, and bill like utilities—but cloud computing tends to expand what is provided by grids and utilities. Some successful cloud architectures have little or no centralized infrastructure or billing systems whatsoever, including peer-to-peer networks such as BitTorrent and Skype, and volunteer computing such as SETI@home.

Furthermore, many analysts are keen to stress the evolutionary, incremental pathway between grid technology and cloud computing, tracing roots back to Application Service Providers (ASPs) in the 1990s and the parallels to SaaS, often referred to as applications on the cloud. Some are of the persuasion that the true difference between these terms is marketing and branding; that the technology evolution was incremental and the marketing evolution discrete.

Characteristics

Cloud computing customers do not generally own the physical infrastructure serving as host to the software platform in question. Instead, they avoid capital expenditure by renting usage from a third-party provider. They consume resources as a service and pay only for resources that they use. Many cloud-computing offerings employ the utility computing model, which is analogous to how traditional utility services (such as electricity) are consumed, while others bill on a subscription basis. Sharing "perishable and intangible" computing power among multiple tenants can improve utilization rates, as servers are not unnecessarily left idle (which can reduce costs significantly while increasing the speed of application development). A side effect of this approach is that overall computer usage rises dramatically, as customers do not have to engineer for peak load limits. Additionally, "increased high-speed bandwidth" makes it possible to receive the same response times from centralized infrastructure at other sites.

Economics

Diagram showing economics of cloud computing versus traditional IT, including capital expenditure (CapEx) and operational expenditure (OpEx)

Cloud computing users can avoid capital expenditure (CapEx) on hardware, software, and services when they pay a provider only for what they use. Consumption is usually billed on a utility (e.g. resources consumed, like electricity) or subscription (e.g. time based, like a newspaper) basis with little or no upfront cost. A few cloud providers are now beginning to offer the service for a flat monthly fee as opposed to on a utility billing basis. Other benefits of this time sharing style approach are low barriers to entry, shared infrastructure and costs, low management overhead, and immediate access to a broad range of applications. Users can generally terminate the contract at any time (thereby avoiding return on investment risk and uncertainty) and the services are often covered by service level agreements (SLAs) with financial penalties.

According to Nicholas Carr, the strategic importance of information technology is diminishing as it becomes standardized and less expensive. He argues that the cloud computing paradigm shift is similar to the displacement of electricity generators by electricity grids early in the 20th century.

Although companies might be able to save on upfront capital expenditures, they might not save much and might actually pay more for operating expenses. In situations where the capital expense would be relatively small, or where the organization has more flexibility in their capital budget than their operating budget, the cloud model might not make great fiscal sense. Other factors impacting the scale of any potential cost savings include the efficiency of a company’s data center as compared to the cloud vendor’s, the company’s existing operating costs, the level of adoption of cloud computing, and the type of functionality being hosted in the cloud.

Companies

Dell, Vmware, 3PAR, Sun Microsystems, Rackspace US,ThinkGrid, Star UK, IBM, Amazon, Google, BMC, Microsoft, salesforce.com and Yahoo are some of the major cloud computing service providers. Cloud services are also being adopted by individual users through large enterprises including Vmware, 3PAR, General Electric, and Procter & Gamble.

Architecture

The majority of cloud computing infrastructure, as of 2009Template:DMCA, consists of reliable services delivered through data centers and built on servers with different levels of virtualization technologies. The services are accessible anywhere that provides access to networking infrastructure. Clouds often appear as single points of access for all consumers' computing needs. Commercial offerings are generally expected to meet quality of service (QoS) requirements of customers and typically offer SLAs. Open standards are critical to the growth of cloud computing, and open source software has provided the foundation for many cloud computing implementations.

History

The Cloud is a term that borrows from telephony. Up to the 1990s, data circuits (including those that carried Internet traffic) were hard-wired between destinations. Subsequently, long-haul telephone companies began offering Virtual Private Network (VPN) service for data communications. Telephone companies were able to offer VPN based services with the same guaranteed bandwidth as fixed circuits at a lower cost because they could switch traffic to balance utilization as they saw fit, thus utilizing their overall network bandwidth more effectively. As a result of this arrangement, it was impossible to determine in advance precisely which paths the traffic would be routed over. The term "telecom cloud" was used to describe this type of networking, and cloud computing is conceptually somewhat similar.

Cloud computing relies heavily on virtual machines (VMs), which are spawned on demand to meet user needs. A common depiction in network diagrams is a cloud outline.

The underlying concept of cloud computing dates back to 1960, when John McCarthy opined that "computation may someday be organized as a public utility"; indeed it shares characteristics with service bureaus that date back to the 1960s. The term cloud had already come into commercial use in the early 1990s to refer to large Asynchronous Transfer Mode (ATM) networks. Ill-fated startup General Magic launched a short-lived cloud computing product in 1995 in partnership with several telecommunications company partners such as AT&T, just before the consumer-oriented Internet became popular. By the turn of the 21st century, the term "cloud computing" began to appear more widely, although most of the focus at that time was limited to SaaS.

In 1999, Salesforce.com was established by Marc Benioff, Parker Harris, and their associates. They applied many technologies developed by companies such as Google and Yahoo! to business applications. They also provided the concept of "On demand" and SaaS with their real business and successful customers. The key for SaaS is that it is customizable by customers with limited technical support required. Business users have enthusiastically welcomed the resulting flexibility and speed.

In the early 2000s, Microsoft extended the concept of SaaS through the development of web services. IBM detailed these concepts in 2001 in the Autonomic Computing Manifesto, which described advanced automation techniques such as self-monitoring, self-healing, self-configuring, and self-optimizing in the management of complex IT systems with heterogeneous storage, servers, applications, networks, security mechanisms, and other system elements that can be virtualized across an enterprise.

Amazon played a key role in the development of cloud computing by modernizing their data centers after the dot-com bubble and, having found that the new cloud architecture resulted in significant internal efficiency improvements, providing access to their systems through Amazon Web Services in 2005 on a utility computing basis.

In 2007, Google, IBM, and a number of universities embarked on a large scale cloud computing research project, around the time the term started, it was a hot topic. By mid-2008, cloud computing gained popularity in the mainstream press, and numerous related events took place.

In August 2008, Gartner Research observed that "organizations are switching from company-owned hardware and software assets to per-use service-based models" and that the "projected shift to cloud computing will result in dramatic growth in IT products in some areas and in significant reductions in other areas."

In 2009, Cloud Computing Solutions by Google, Amazon, Microsoft, and IBM are the most popular among users with Sun and Ubuntu following them in the Cloud.

Criticism and Disadvantages of Cloud Computing

Because cloud computing does not allow users to physically possess the storage of their data (the exception being the possibility that data can be backed up to a user-owned storage device, such as a USB flash drive or hard disk) it does leave responsibility of data storage and control in the hands of the provider.

Cloud computing has been criticized for limiting the freedom of users and making them dependent on the cloud computing provider, and some critics have alleged that it is only possible to use applications or services that the provider is willing to offer. Writing in the The London Times, Jonathan Weber compares cloud computing to centralized systems of the 1950s and 60s, by which users connected through "dumb" terminals to mainframe computers. Typically, users had no freedom to install new applications and needed approval from administrators to achieve certain tasks. Overall, it limited both freedom and creativity. The Times article argues that cloud computing is a regression to that time.

One of the important issues in cloud computing that needs to be addressed is that once you upload your data to a cloud computing service provider, you lose control over your data, and if the computing service provider is experiencing problems, you may not be able to access your data at all. Also, in most of the cases, at least this is true for free services, there is no one on the provider's side to assist you with a problem (if you are having one).

Similarly, Richard Stallman, founder of the Free Software Foundation, believes that cloud computing endangers liberties because users sacrifice their privacy and personal data to a third party. He stated that cloud computing is "simply a trap aimed at forcing more people to buy into locked, proprietary systems that would cost them more and more over time."

Further to Stallman's observation, it would be a challenge for hosting/deploying intranet and access restricted (for Govt., defense, institutional, etc) sites and their maintenance. Commercial sites using tools such as web analytics may not be able to capture right data for their business planning etc.

Political issues

The Cloud spans many borders and "may be the ultimate form of globalization." As such, it becomes subject to complex geopolitical issues, and providers are pressed to satisfy myriad regulatory environments in order to deliver service to a global market. This dates back to the early days of the Internet, when libertarian thinkers felt that "cyberspace was a distinct place calling for laws and legal institutions of its own".

Despite efforts (such as US-EU Safe Harbor) to harmonize the legal environment, as of 2009Template:DMCA, providers such as Amazon Web Services cater to major markets (typically the United States and the European Union) by deploying local infrastructure and allowing customers to select "availability zones." Nonetheless, concerns persist about security and privacy from individual through governmental levels (e.g., the USA PATRIOT Act, the use of national security letters, and the Electronic Communications Privacy Act's Stored Communications Act.

Legal issues

In March 2007, Dell applied to trademark the term "cloud computing" (Template:US trademark) in the United States. The "Notice of Allowance" the company received in July 2008 was canceled in August, resulting in a formal rejection of the trademark application less than a week later.

In September 2008, the United States Patent and Trademark Office (USPTO) issued a "Notice of Allowance" to CGactive LLC (Template:US trademark) for "CloudOS". As defined under this notice, a cloud operating system is a generic operating system that "manage[s] the relationship between software inside the computer and on the Web", such as Microsoft Azure.

In November 2007, the Free Software Foundation released the Affero General Public License, a version of GPLv3 intended to close a perceived legal loophole associated with Free software designed to be run over a network, particularly SaaS. An application service provider is required to release any changes they make to Affero GPL open source code.Template:Fact

Risk mitigation

Corporations or end-users wishing to avoid not being able to access their data—or even losing it—are typically advised to research vendors' policies on data security before using their services. One technology analyst and consulting firm, Gartner, lists several security issues that one should discuss with cloud-computing vendors:

• Privileged user access—Who has specialized access to data and about the hiring and management of such administrators?
• Regulatory compliance—Is the vendor willing to undergo external audits and/or security certifications?
• Data location—Does the provider allow for any control over the location of data?
• Data segregation—Is encryption available at all stages, and were these encryption schemes designed and tested by experienced professionals?
• Recovery—What happens to data in the case of a disaster, and does the vendor offer complete restoration, and, if so, how long does that process take?
• Investigative Support—Does the vendor have the ability to investigate any inappropriate or illegal activity?
• Long-term viability—What happens to data if the company goes out of business, and is data returned and in what format?
• Data availability—Can the vendor move your data onto a different environment should the existing environment become compromised or unavailable?

In practice, one can best determine data-recovery capabilities by experiment; for example, by asking to get back old data, seeing how long it takes, and verifying that the checksums match the original data. Determining data security can be more difficult, but one approach is to encrypt the data yourself. If you encrypt data using a trusted algorithm, then, regardless of the service provider's security and encryption policies, the data will only be accessible with the decryption keys. This leads, however, to the problem of managing private keys in a pay-on-demand computing infrastructure.

Key characteristics

• Agility improves with users able to rapidly and inexpensively re-provision technological infrastructure resources. The cost of overall computing is unchanged, however, and the providers will merely absorb up-front costs and spread costs over a longer period..
• Cost is claimed to be greatly reduced and capital expenditure is converted to operational expenditure. This ostensibly lowers barriers to entry, as infrastructure is typically provided by a third-party and does not need to be purchased for one-time or infrequent intensive computing tasks. Pricing on a utility computing basis is fine-grained with usage-based options and fewer IT skills are required for implementation (in-house). Some would argue that given the low cost of computing resources, that the IT burden merely shifts the cost from in-house to outsourced providers. Furthermore, any cost reduction benefit must be weighed against a corresponding loss of control, access and security risks.
• Device and location independence enable users to access systems using a web browser regardless of their location or what device they are using (e.g., PC, mobile). As infrastructure is off-site (typically provided by a third-party) and accessed via the Internet, users can connect from anywhere.
• Multi-tenancy enables sharing of resources and costs across a large pool of users thus allowing for:
  • Centralization of infrastructure in locations with lower costs (such as real estate, electricity, etc.)
  • Peak-load capacity increases (users need not engineer for highest possible load-levels)
  • Utilization and efficiency improvements for systems that are often only 10–20% utilized.
• Reliability improves through the use of multiple redundant sites, which makes cloud computing suitable for business continuity and disaster recovery. Nonetheless, many major cloud computing services have suffered outages, and IT and business managers can at times do little when they are affected.
• Scalability via dynamic ("on-demand") provisioning of resources on a fine-grained, self-service basis near real-time, without users having to engineer for peak loads. Performance is monitored, and consistent and loosely-coupled architectures are constructed using web services as the system interface.
• Security typically improves due to centralization of data, increased security-focused resources, etc., but concerns can persist about loss of control over certain sensitive data. Security is often as good as or better than under traditional systems, in part because providers are able to devote resources to solving security issues that many customers cannot afford. Providers typically log accesses, but accessing the audit logs themselves can be difficult or impossible. Ownership, control and access to data controlled by "cloud" providers may be made more difficult,just as it is sometimes difficult to gain access to "live" support with current utilities. Under the cloud paradigm, management of sensitive data is placed in the hands of cloud providers and third parties. Currently, many developers are implementing OAuth (open protocol for secure API authorization), as it allows more granularity of data controls across cloud applications. OAuth is an open protocol, initiated by Blain Cook and Chris Messina, to allow secure API authorization in a standard method for desktop, mobile, and web applications.
• Sustainability comes about through improved resource utilization, more efficient systems, and carbon neutrality. Nonetheless, computers and associated infrastructure are major consumers of energy. A given (server-based) computing task will use X amount of energy whether it is on-site, or off.

Components

Six layers components of cloud computing

Client

A cloud client consists of computer hardware and/or computer software which relies on cloud computing for application delivery, or which is specifically designed for delivery of cloud services and which, in either case, is essentially useless without it. For example:

• Mobile (Android, iPhone, Windows Mobile)

• Thin client (CherryPal, Zonbu, gOS-based systems)

• Thick client / Web browser (Microsoft Internet Explorer, Mozilla Firefox)

Service

A cloud service includes "products, services and solutions that are delivered and consumed in real-time over the Internet". For example, Web Services ("software system[s] designed to support interoperable machine-to-machine interaction over a network") which may be accessed by other cloud computing components, software, e.g., Software plus services, or end users directly. Specific examples include:

• Identity (OAuth, OpenID)
• Integration (Amazon Simple Queue Service)
• Payments (Amazon Flexible Payments Service, Google Checkout, PayPal)
• Mapping (Google Maps, Yahoo! Maps, MapQuest)
• Search (Alexa, Google Custom Search, Yahoo! BOSS)
• Video Games (OnLive, Gaikai)
• Live chat (LivePerson)
• Symplified Inc. is a privately owned American company based in Boulder, CO. Symplified was founded by the same management team that created Securant, which pioneered the market for Web access management software and was acquired for $140M by RSA Security. The company first incorporated in 2006.
• Others (Amazon Mechanical Turk)

Application

A cloud application leverages the Cloud in software architecture, often eliminating the need to install and run the application on the customer's own computer, thus alleviating the burden of software maintenance, ongoing operation, and support. For example:

• Peer-to-peer / volunteer computing (Bittorrent, BOINC Projects, Skype)
• Web application (Twitter)
• Software as a service (Google Apps, SAP and Salesforce)
• Software plus services (Microsoft Online Services)

Platform

A cloud platform, such as Platform as a service, the delivery of a computing platform, and/or solution stack as a service, facilitates deployment of applications without the cost and complexity of buying and managing the underlying hardware and software layers. For example:

• Code Based Web Application Frameworks
  • Java Google Web Toolkit (Google App Engine)
  • Python Django (Google App Engine)
  • Ruby on Rails (Heroku)
  • .NET (Azure Services Platform)
• Non-Code Based Web Application Framework
  • WorkXpress
  • Wolf Frameworks
• Cloud Computing Application & Web Hosting (Rackspace Cloud)
• Proprietary (Force.com)

Infrastructure

Cloud infrastructure, such as Infrastructure as a service, is the delivery of computer infrastructure, typically a platform virtualization environment, as a service. For example:

• Full virtualization (GoGrid, Skytap, iland)
• Grid computing (Sun Cloud)
• Hosted desktop (ThinkGrid)
• Management (RightScale)
• Compute (Amazon Elastic Compute Cloud, Savvis, TerreMark)
• Platform (Force.com)
• Storage (Amazon S3, Nirvanix, Rackspace, Savvis, TerreMark)

Architecture

Cloud computing sample architecture

Cloud architecture, the systems architecture of the software systems involved in the delivery of cloud computing, comprises hardware and software designed by a cloud architect who typically works for a cloud integrator. It typically involves multiple cloud components communicating with each other over application programming interfaces, usually web services.

This closely resembles the Unix philosophy of having multiple programs each doing one thing well and working together over universal interfaces. Complexity is controlled and the resulting systems are more manageable than their monolithic counterparts.

Cloud architecture extends to the client, where web browsers and/or software applications access cloud applications.

Cloud storage architecture is loosely coupled, where metadata operations are centralized enabling the data nodes to scale into the hundreds, each independently delivering data to applications or users.

Types

Cloud computing types

Public cloud

Public cloud or external cloud describes cloud computing in the traditional mainstream sense, whereby resources are dynamically provisioned on a fine-grained, self-service basis over the Internet, via web applications/web services, from an off-site third-party provider who shares resources and bills on a fine-grained utility computing basis.

Hybrid cloud

A hybrid cloud environment consisting of multiple internal and/or external providers "will be typical for most enterprises".

Private cloud

Private cloud and internal cloud are neologisms that some vendors have recently used to describe offerings that emulate cloud computing on private networks. These (typically virtualisation automation) products claim to "deliver some benefits of cloud computing without the pitfalls", capitalising on data security, corporate governance, and reliability concerns. They have been criticized on the basis that users "still have to buy, build, and manage them" and as such do not benefit from lower up-front capital costs and less hands-on management, essentially "[lacking] the economic model that makes cloud computing such an intriguing concept".

While an analyst predicted in 2008 that private cloud networks would be the future of corporate IT, there is some uncertainty whether they are a reality even within the same firm. Analysts also claim that within five years a "huge percentage" of small and medium enterprises will get most of their computing resources from external cloud computing providers as they "will not have economies of scale to make it worth staying in the IT business" or be able to afford private clouds.. Analysts have reported on Platform's view that private clouds are a stepping stone to external clouds, particularly for the financial services, and that future datacenters will look like internal clouds.

The term has also been used in the logical rather than physical sense, for example in reference to platform as a service offerings, though such offerings including Microsoft's Azure Services Platform are not available for on-premises deployment.

Roles

Provider

A cloud computing provider or cloud computing service provider owns and operates live cloud computing systems to deliver service to third parties. Usually this requires significant resources and expertise in building and managing next-generation data centers. Some organisations realise a subset of the benefits of cloud computing by becoming "internal" cloud providers and servicing themselves, although they do not benefit from the same economies of scale and still have to engineer for peak loads. The barrier to entry is also significantly higher with capital expenditure required and billing and management creates some overhead. Nonetheless, significant operational efficiency and agility advantages can be realised, even by small organisations, and server consolidation and virtualization rollouts are already well underway. Amazon.com was the first such provider, modernising its data centers which, like most computer networks, were using as little as 10% of its capacity at any one time just to leave room for occasional spikes. This allowed small, fast-moving groups to add new features faster and easier, and they went on to open it up to outsiders as Amazon Web Services in 2002 on a utility computing basis.

The companies listed in the Components section are providers.

User

A user is a consumer of cloud computing. The privacy of users in cloud computing has become of increasing concern. The rights of users is also an issue, which is being addressed via a community effort to create a bill of rights. The Franklin Street statement was drafted with an eye towards protecting users' freedoms.

Vendor

Some vendors sell or give products and services that facilitate the delivery, adoption and use of cloud computing. For example:

• Computer hardware (Dell, HP, IBM, and Sun Microsystems)
  • Storage (3PAR, EMC, Hitachi Data Systems, IBM, Mezeo, NetApp, ParaScale, and Sun Microsystems)
  • Infrastructure (Cisco Systems, Juniper Networks, and Brocade Communications)
• Computer software (3tera, Eucalyptus, g-Eclipse, and Hadoop)
  • Operating systems (Solaris, AIX, Linux including Novell, Red Hat, and Ubuntu)
  • Platform virtualization (Citrix, IBM, Linux KVM, Microsoft, Sun xVM, VMware, and Xen)

Standards

Cloud standards, a number of existing, typically lightweight, open standards, have facilitated the growth of cloud computing, including:

• Application
  • Communications (HTTP, XMPP)
  • Security (OAuth, OpenID, SSL/TLS)
  • Syndication (Atom)
• Client
  • Browsers (AJAX)
  • Offline (HTML 5)
• Implementations
  • Virtualization (OVF)
• Platform
  • Solution stacks (LAMP)
• Service
  • Data (XML, JSON)
  • Web Services (REST)
• Storage

See also

• Cloud Computing Manifesto
• Cloud networking

External links

• Luis M. Vaquero et al., A Break in the Clouds: Toward a Cloud Definition, ACM SIGCOMM Computer Communication Review, Volume 39, Issue 1 (January 2009), Pages 50–55, ISSN:0146-4833
• Jones, M. Tim, Cloud Computing with Linux from IBM DeveloperWorks (2008-09-10).
• Template:Cite paper
• Social Directory of SaaS Cloud Computing Companies
• What is Cloud Computing ? - Web 2.0 expo - A video where Tim O’Reilly, Dan Farber, Matt Mullenweg and others answer this question.