ASSIGNMENT

Q1. What is cloud computing? ANS. Cloud computing is the use of computing resources (hardware and software) that
are delivered as a service over a network (typically the Internet). The name comes from the use of a cloud-shaped symbol as an abstraction for the complex infrastructure it contains in system diagrams. Cloud computing entrusts remote services with a user's data, software and computation. As a metaphor for the Internet, "the cloud" is a familiar clich, but when combined with "computing," the meaning gets bigger and fuzzier. Some analysts and vendors define cloud computing narrowly as an updated version of utility computing. ARCHITECTURE OF CLOUD COMPUTING Cloud architecture is the systems architecture of the software systems involved in the delivery of cloud computing, e.g., hardware, software, as 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 is very similar to the UNIX philosophy of having multiple programs 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 are used to 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.

a) The Intercloud
The Intercloud is an interconnected global "cloud of clouds and an extension of the Internet "network of networks" on which it is based. The term was first used in the context of cloud computing in 2007 when Kevin Kelly opined that "eventually we'll have the intercloud, the cloud of clouds". It became popular in early 2009 and has also been used to describe the datacenter of the future. The Intercloud scenario is based on the key concept that each single cloud does not have infinite physical resources or ubiquitous geographic footprint. If a cloud saturates the computational and storage resources of its infrastructure, or is requested to use resources in a geography where it has no footprint, it would still be able satisfy such requests for service allocations sent from its clients. The Intercloud scenario would address such situations where each cloud would use the computational, storage, or any kind of resource of the infrastructures of other clouds. This is a precise analogy to how the Internet works, in that a service provider, to which an endpoint is attached, will access or deliver traffic from/to source/destination addresses outside of its service area by using Internet routing protocols with other service providers with whom it has a prearranged exchange or peering relationship. It is also analogous to the way mobile operators implement roaming and inter-carrier interoperability. Such forms of cloud

exchange, peering, or roaming may introduce new business opportunities among cloud providers if they manage to go beyond the theoretical framework.

b) Cloud engineering 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 systems, software, web, performance, information, security, platform, risk, and quality engineering. Cloud engineering is a field of engineering that focuses on cloud services, such as "software as a service", "platform as a service", and "infrastructure as a service". It is a multidisciplinary method encompassing contributions from diverse areas such as systems engineering, software engineering, web engineering, performance engineering, information engineering, security engineering, platform engineering, service engineering, risk engineering, and quality engineering. The nature of commodity-like capabilities delivered by cloud services and the inherent challenges in this business model drive the need for cloud engineering as the process of "designing the systems necessary to leverage the power and economics of cloud resources to solve business problems."

TYPES OF CLOUD ENGINEERING

a) PUBLIC CLOUD:
Public cloud or external cloud describes cloud computing in the traditional mainstream sense, whereby resources are dynamically provisioned on a finegrained, 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. The name public in the public cloud comes from the fact that application is hosted on the Hosting Providers location (Vendors). Though it is hosted in shared system, each resource operates in silo and encrypted securely. 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. Some of the examples of Public Cloud in market are Amazon Web Services, Microsoft Azure and Google Apps. 1. Infrastructure as a Service (IaaS) In this most basic cloud service model, cloud providers offer computers, as physical or more often as virtual machines, and other resources. The virtual machines are run

as guests by a hypervisor, such as Xen or KVM. Management of pools of hypervisors by the cloud operational support system leads to the ability to scale to support a large number of virtual machines. IaaS refers not to a machine that does all the work, but simply to a facility given to businesses that offers users the leverage of extra storage space in servers and data centers. 2. Platform as a service (PaaS) In this model, the consumer creates the software using tools and/or libraries from the provider. The consumer also controls software deployment and configuration settings. The provider provides the networks, servers, storage and other services. PaaS offerings facilitate the deployment of applications without the cost and complexity of buying and managing the underlying hardware and software and provisioning hosting capabilities. PaaS offerings may also include facilities for application design, application development, testing and deployment as well as services such as team collaboration, web service integration and marshalling, database integration, security, scalability, storage, persistence, state management, application versioning, application instrumentation and developer community facilitation. These services are generally provisioned as an integrated solution over the web 3. Software as a service (SaaS) In this model, cloud providers install and operate application software in the cloud and cloud users access the software from cloud clients. The cloud users do not manage the cloud infrastructure and platform on which the application is running. This eliminates the need to install and run the application on the cloud user's own computers simplifying maintenance and support. What makes a cloud application different from other applications is its elasticity. This can be achieved by cloning tasks onto multiple virtual machines at run-time to meet the changing work demand. [47] Load balancers distribute the work over the set of virtual machines. This process is inconspicuous to the cloud user who sees only a single access point. To accommodate a large number of cloud users, cloud applications can be multitenant, that is, any machine serves more than one cloud user organization. It is common to refer to special types of cloud based application software with a similar naming convention: desktop as a service, business process as a service, test environment as a service, communication as a service. The pricing model for SaaS applications is typically a monthly or yearly flat fee per user, so price is scalable and adjustable if users are added or removed at any point. 4) Data as a service (DaaS) Data as a service, or DaaS, is a cousin of software as a service. Like all members of the "as a Service" (aaS) family, DaaS is based on the concept that the product, data in this case, can be provided on demand to the user regardless of geographic or organizational separation of provider and consumer. Additionally, the emergence of service-oriented architecture (SOA) has rendered the actual platform on which the data resides also irrelevant. This development has enabled the recent emergence of the relatively new concept of DaaS.

Data provided as a service was at first primarily used in web mashups, but now is being increasingly employed both commercially and, less commonly, within organizations such as the UN 5) Storage as a service (STaaS) is a business model in which a large service provider rents space in their storage infrastructure on a subscription basis. The economy of scale in the service provider's infrastructure allows them to provide storage much more cost effectively than most individuals or corporations can provide their own storage, when total cost of ownership is considered. Storage as a Service is often used to solve offsite backup challenges

b) PRIVATE CLOUD In this form, the cloud is deployed with in a corporate firewall and runs on 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. 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.

c) HYBRID CLOUD Hybrid Cloud are increasingly being used by corporations where there is a need to maintain some of their applications on their internal infrastructure (because of regulatory compliance or sensitivity of data), but also need the scalability and cost benefits of the public cloud. Cloud bursting is the term normally used for this type of environment where internal applications are deployed on private cloud for normal usage while internet applications are deployed on the public cloud to handle variable loads.

d) COMMUNITY CLOUD 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. CHALLENGES OF CLOUD COMPUTING Challenge 1: Safeguarding data security Potential adopters are concerned about the security of data outside the corporate firewall. A related issue has to do with offshore data housing, which can pose

problems of legislative compliance when data crosses borders. In the short term, most companies can avoid these issues by using domestic cloud facilities. The cloud carries some new risks, howevernotably, People hack brands or hack applications regardless of what the infrastructure is underneath. Because a cloud provider hosts multiple clients, each can be affected by actions taken against any one of them, as in distributed denial-of-service attacksserver requests that inundate a provider from widely distributed computers. This is what happened, for example, in the wake of the WikiLeaks activities: when attacks came into the provider hosting WikiLeaks, all other clients were affected as well. However, some of these risks are mitigated to a degree by new security applications such as encrypted file systems and data-loss prevention software. Cloud providers also have the ability to invest in more sophisticated security hardware and software, such as using analytics to examine unusual behavior across vast numbers of virtual servers. Beyond this, a providers scale enables effective responses to large-scale server attacks through high levels of redundancy. Concerned enterprises can also mitigate risk by employing hybrid cloudsa situation in which most servers are in the cloud, but key data is hosted internally and by improving data governance.

Challenge 2: Managing the contractual relationship Cloud computing contracts are a mix of outsourcing, software and leasing. Some observers have argued that contracting for cloud is simpler than traditional approaches to IT sourcing because only one contract is required instead of multiple agreements for software, hardware and systems integration. In reality, however, few software, platform or infrastructure providers meet all of a clients functional requirements, so contracting for cloud services typically involves ecosystems of providers that must be integrated to provide complete solutions. Cloud contracts generally focus on service-level agreement (SLA) guarantees, but the network of interactions within the overall ecosystem increases the complexity of SLAs. Software-as-a-service providers, for example, often share a single platform for all users, and so they cannot provide each client with a differentiated SLA. At present, relatively low compensation is offered by providers for breaches of SLAs, but competition should improve this situation, as should the development of cloud standards. Challenge 3: Dealing with lock-in Exit strategies and lock-in risks are key concerns for companies looking to exploit cloud computing. There is always a switching cost for any company receiving external services. However, cloud providers have a significant additional incentive to attempt to exploit lock-in. If computing were to become a very liquid commodity, and if switching to a lower-cost provider were too easy, margins would rapidly become razor thin. When contracting for a cloud service, executives should be aware of two forms of lock-in. The first form, technology lock-in, concerns the cost of moving a business service from one cloud platform to another. Once a company is on a particular

platform, it is often more cost-effective to purchase additional services compatible with existing onesthus increasing lock-in. A second form, institutional lock-in, occurs when technologies become embedded within organizational routines and users work practices. Particularly for users of software-as-a-service, such institutionalism can have a serious impact on the ability to switch cloud providers-which increases the severity of lock-in. Providers are likely to focus on increasing lock-in as competition reduces margins. Competitors, however, will focus on reducing switching costs for dominant players. Specialist services and service integrators can help meet these challenges. Challenge 4: Managing the cloud Although many dramatic predictions are being made about the impact of cloud computingamong them, the claim that traditional IT departments will become obsoletecloud impacts are likely to be more gradual and less linear. Nevertheless, the cloud does carry with it significant disruption to business as usual, leading to two particular management challenges. First, once introduced into the enterprise, cloud services can be easily updated or changed by business users without the direct involvement of the IT department. And it is in the providers interests to develop functionality that expands usage and spreads it across the organization. So maintaining overall, strategic control of services can be difficult. This independence of the business when it comes to IT services also means that IT must work harder to gain the ongoing attention of the C-suite and to extend its strategic role. Second, organizations are still slow in developing management capabilities and principles for operating with cloud services. Such strategies should focus on the multiple contracts needed for a cloud ecosystem. Effective supervision of usage, SLAs, performance, robustness and business dependency is vital. Monitoring the external providers services must be done, but internal cloud monitoring should also be introduced. Support provided by cloud providers can be variable, and organizations should develop their own support services, either internally or with third parties

APPLICATIONS OF CLOUD COMPUTING

Cloud computing evolved from the knowledge and experience of managed services, Internet services, application service providers, etc. Its technology is the result of a paradigm shift and is improving business computing because: (1) it is modular, compartmentalizing software applications and associated hardware and infrastructure; (2) it is uniform, utilizing the same resources that customers share. A business using cloud computing can avoid large outlays of capital expense as well as perpetual maintenance costs, thereby aligning cash flow with total system cost. Data centers are known to be very inefficient and clustering and virtualizing their servers has met with only limited success. Over time, there will be a logical segue to scalable computing based on/in the cloud. The future of computing is going to consist of the combination of service orientation, service management, and cloud computing. Some of the reasons for this are: Hardware costs would decrease because cloud computing systems would reduce the need for advanced, expensive hardware on the client side. It would no longer be necessary or desirable to buy the fastest computer with the most memory or largest hard drive. Rather, all a customer would need to buy is an inexpensive computer terminal, a monitor, input components such as a keyboard and mouse, and only enough processing power to run the middleware necessary to connect to the cloud system. Clients could access their applications and data from anywhere at any time using a computer linked to the Internet. Data would be stored offsite rather than take up space on a hard drive on a users computer or a corporations internal network.

 Since cloud computing is a pay as you go system, companies would not have to buy software or software licenses for each employee. Instead, the company would pay a metered fee based on usage, much the way open source software (as opposed to proprietary software) works. For the most part, cloud computing infrastructures are built from open source components because the cloud providers are hesitant to make large investments without knowing the payoff. Cloud computing customers would no longer have to worry about physical space in which to store servers and other storage hardware. They can store data on a thirdpartys system, thus removing the need for physical space on the front end. Since cloud computing offers tried and true hardware, operating systems, and applications, customers could save money on IT support (for obvious reasons, this is not a concept that IT support personnel in general buy into). If the cloud computing systems back end is a grid computing system, customers could take advantage of the entire networks processing power. For instance, scientists and researchers who work with extremely complicated calculations could send the calculations to the cloud for processing. The cloud system would utilize the processing power of all available computers on the back end and significantly speed up the calculations. Cloud computing provides a way to outsource non-critical applications to organizations better suited to run them, allowing IT to focus on critical applications. Cloud providers are more efficient at IT operations, using fewer man-hours for standard tasks. By buying hardware in large volume, cloud providers get better pricing. INDUSTRIES USING CLOUD COMPUTING Small and medium businesses Start up companies Government Financial Sector Telecommunication Companies Education Sector