Cloud Computing Fundamentals and its applications

CC

1. Cloud Computing By: Ritesh Malaiya

2. Evolution of Cloud Computing Cloud computing is a natural evolution of the widespread adoption of  virtualization ,  service-oriented architecture ,  autonomic  (self-managing characteristics of distributed computing resources), and utility computing The underlying concept of cloud computing dates back to the 1960s, when  John McCarthy  opined that "computation may someday be organized as a  public utility ." Around 2006,  Amazon  played a key role in the development of cloud computing by modernizing their  data centers , which, like most  computer networks , were using as little as 10% of their capacity at any one time, just to leave room for occasional spikes. In early 2008, efforts were focused on providing QoS guarantees (as required by real-time interactive applications) to cloud-based infrastructures, in the framework of the IRMOS European Commission-funded project.

3. Layers in Cloud Computing Client A  cloud client  consists of  computer hardware  and/or  computer software  that relies on cloud computing for application delivery and that is in essence useless without it. Examples include some computers, phones and other devices,  operating systems , and  browsers Application Cloud application services or " Software as a Service  (SaaS)" deliver software as a service over the Internet, eliminating the need to install and run the application on the customer's own computers and simplifying maintenance and support. Platform Cloud platform services, also known as  Platform as a service  (PaaS), deliver a  computing platform  and/or  solution stack  as a service, often consuming cloud infrastructure and sustaining cloud applications. It facilitates deployment of applications without the cost and complexity of buying and managing the underlying hardware and software layers.

4. Layers in Cloud Computing Infrastructure Cloud infrastructure services, also known as "infrastructure as a service" (IaaS), deliver computer infrastructure – typically a  platform virtualization  environment – as a service, along with raw (block) storage and networking. Rather than purchasing servers, software, data-center space or network equipment, clients instead buy those resources as a fully outsourced service. Suppliers typically bill such services on a utility computing basis; the amount of resources consumed (and therefore the cost) will typically reflect the level of activity. [35] Server The servers layer consists of  computer hardware  and/or  computer software  products that are specifically designed for the delivery of cloud services, including multi-core processors, cloud-specific operating systems and combined offerings.

5. Flavors of Cloud Computing Cloud Computing SAAS - Service As A Service PAAS - Platform As A Service IAAS   - Infrastructure As A Service IAAS   - Identity As A Service CAAS - Compliance-as-a-Service SecAAS - Security As A Service   

6. Cloud Computing Why is this required? Role of Virtualization (Native Hypervisor) Evolution from Clusters Comparison with Grid Computing, Distributed Computing, Ubiquitous Computing

7. SaaS Architecture Maturity Model Level 0 (Chaos); Every time you add a new customer, you add a new instance of the software. Level 1 (Managed Chaos): Every customer runs on the same version of the software and any customizations are done via configuration. Level 2 (Multi-Tenant, Highrise): You've got all customers running on a single version of the software, and they're all running essentially on one "instance". Level 3 (Multi-Tenant, Build-Out): This is when you've got multi-tenant, single version of the software model. But, you can scale-out (add buildings at will). Level 4 (Utopia): This is like Level 3, except you've figured out an efficient way to run different versions of the software on different "instances". According to a  Gartner Group  estimate, SaaS sales in 2010 reached $10B, and are projected to increase to $12.1B by end of 2011 www.cnergyis.com/ESSV3 is an example of SAAS.

8. Platform As A Service Platform as a service  ( PaaS ) is the delivery of a  computing platform  and  solution stack  as a service. An outgrowth of the SaaS application delivery model. Types of PAAS: Add-on development facilities These facilities allow customization of existing  software-as-a-service  (SaaS) applications. Often these require PaaS developers and their users to purchase subscriptions to the co-resident SaaS application. Stand alone development environments Stand-alone PaaS environments do not include technical, licensing or financial dependencies on specific SaaS applications or web services, and are intended to provide a generalized development environment. Application delivery-only environments Some PaaS offerings lack development, debugging and test capabilities, and provide only hosting-level services such as security and on-demand scalability. Microsoft AZURE is an example of PAAS

9. IAAS  Typically a  platform virtualization  environment  Provides raw (block) storage and networking Apache Hadoop is an example of IAAS It enables applications to work with thousands of nodes and  petabytes  of data. Hadoop was inspired by  Google 's  MapReduce  and  Google File System  (GFS) papers. Prominent Users Yahoo! On February 19, 2008,  Yahoo! Inc.  launched what it claimed was the world's largest Hadoop production application. The Yahoo! Search Webmap is a Hadoop application that runs on more than 10,000  core   Linux   cluster  and produces data that is now used in every Yahoo! Web search query. On June 10, 2009, Yahoo! made available the source code to the version of Hadoop it runs in production. Yahoo! contributes back all work it does on Hadoop to the open-source community Facebook In the year 2010  Facebook  claimed that they have the largest Hadoop cluster in the world with 21 PB  of storage. On July 27, 2011 they announced the data has grown to 30 PB . 1 PB = 1000TeraByte

10. Federation  Federation differs from peering, which requires a prior agreement between parties before a server-to-server (S2S) link can be established Technically speaking, federation is the ability for two XMPP servers in different domains to exchange XML stanzas Permissive federation Server accepts a connection from a peer network server without verifying its identity using DNS lookups or certificate checking. Verified federation Default service policy on the open XMPP since the release of the open-source jabberd 1.2 server Encrypted federation Peer should supports Transport Layer Security (TLS) Trusted federation. Here, a server accepts a connection from a peer only under the stipulation that the peer supports TLS and the peer can present a digital certificate issued by a root certification authority (CA) that is trusted by the authenticating server.

11. Federation  A notable research project being conducted by Microsoft, called the  Geneva Framework , focuses on issues involved in cloud federation. Multiple providers to interact seamlessly with others. Enables developers to incorporate various authentication models that will work with any corporate identity system, including Active Directory, LDAPv3-based directories Internet Engineering Task Force (IETF) standard Extensible Messaging and Presence Protocol (XMPP) and interdomain federation using the Jabber Extensible Communications Platform (Jabber XCP) Potential Users: The U.S. Marines Corps, The Defense Information Systems Agency (DISA), The U.S. Joint Forces Command (USJFCOM), and the National Weather Service.

12. XMPP (also called Jabber) SOAP (Simple Object Access Protocol) and a few other assorted HTTP-based protocols, are all one-way information exchanges XMPP’s profile has been steadily gaining since its inception as the protocol behind the open source instant messenger (IM) server jabberd in 1998. XMPP is a good fit for cloud computing because it allows for easy two way communication Eliminates the need for polling Rich publish - subscribe (pub-sub) functionality built in.

13. Presence in the Cloud Presence is an enabling technology for peer-to-peer interaction Implementation of presence follows the software design pattern known as publish-and-subscribe (pub-sub) Digital identity refers to the traits, attributes, and preferences on which one may receive personalized services Consists of : identity, location, and presence Identity-as-a-Service (IaaS)

14. Security Issues in Cloud Computing Security Architecture Design 1. Authentication 2. Authorization 3. Verifiability 4. Confidentiality 5. Integrity 6. Accountability 7. Privacy

15. Homomorphic Encryption Partially homomorphic cryptosystems Unpadded RSA If the  RSA  public key is modulus  m  and exponent  e , then the encryption of a message  x  is given by . The homomorphic property is then ElGamal In the  ElGamal cryptosystem , in a group  G , if the public key is  ( G , q , g , h ) , where  h  =  g x , and  x  is the secret key, then the encryption of a message  m  is , for some . The homomorphic property is then Full homomorphic cryptosystems  A cryptosystem which supports both addition and multiplication is known as fully homomorphic encryption (FHE) and is far more powerful. Craig Gentry using  lattice-based cryptography  showed the first fully homomorphic encryption scheme as announced by IBM on June 25, 2009 N. Smart and F. Vercauteren. Fully homomorphic encryption with relatively small key and ciphertext sizes. In Public Key Cryptography (PKC'10), volume 6056 of LNCS, pages 420{443. Springer, 2010.

16. Garbled Circuits (GC) By Andy Yao in 1986 for Secure multiparty computation Bob creates a "garbled circuit", and sends the circuit to Alice.  Alice evaluates the circuit with her inputs and returns the result to Bob.  The result of the circuit evaluation with Alice's inputs is the output of the function Alice and Bob wish to compute. 

17. Secure and Practical Outsourcing of Linear Programming in Cloud Computing In this framework, the process on cloud server can be represented by algorithm ProofGen and the process on customer can be organized into three algorithms (KeyGen, ProbEnc, ResultDec). These four algorithms are summarized below and will be instantiated later. • KeyGen(1k) → {K}. This is a randomized key generation algorithm which takes a system security parameter k, and returns a secret key K that is used later by customer to encrypt the target LP problem. • ProbEnc(K,) → {K}. This algorithm encrypts the input tuple into K with the secret key K. According to problem transformation, the encrypted input K has the same form as , and thus defines the problem to be solved in the cloud. • ProofGen(K) → {(y, 􀀀)}. This algorithm augments a generic solver that solves the problem K to produce both the output y and a proof 􀀀. The output y later decrypts to x, and 􀀀 is used later by the customer to verify the correctness of y or x.  • ResultDec(K,, y, 􀀀) → {x,⊥}. This algorithm may choose to verify either y or x via the proof 􀀀. In any case, a correct output x is produced by decrypting y using the secret K. The algorithm outputs ⊥ when the validation fails, indicating the cloud server was not performing the computation faithfully.

18. Twin Clouds: An Architecture for Secure Cloud Computing The security-critical operations are performed by the Trusted Cloud in a Setup Phase High loads of queries can be processed on-demand by the Commodity Cloud. The Trusted Cloud is used mostly in the Setup Phase to encrypt the outsourced data and programs using Yao's garbled circuits which requires only symmetric cryptographic operations and only a constant amount of memory in the Query Phase, the computations on the encrypted data are performed in parallel by the fast but untrusted Commodity Cloud, and finally veried by the Trusted Cloud.

19. Practical Problems of Cloud faced by Developers Mount points for logs to be written. Mount points for resources to be read. Tracing the server which received the request. Deployment configuration required. Change Management.