Introduction to Cloud Computing part 3
•
2 likes•474 views
The Art of Service created a short series of 4 presentations to introduce the various cloud computing concepts. This is part 3 covering PaaS and IaaS.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Introduction to Cloud Computing part 3
Similar to Introduction to Cloud Computing part 3 (20)
More from The Art of Service Pty Ltd
More from The Art of Service Pty Ltd (9)
Recently uploaded
Recently uploaded (20)
Introduction to Cloud Computing part 3
- 1. Cloud Computing Introduction Part 3
- 3. From the Top Cloud Computing encompasses: • Four Deployment Methods • Three Service Models • Five Essential Characteristics
- 4. Deployment Models • Public Clouds • Community Clouds • Private Clouds • Hybrid Clouds
- 5. Public Clouds Advantages to Public Cloud Disadvantages to Public Cloud Computing Computing •Lack of Control •Minimal capital expenditures •Scalability within instances •No upfront risk or commitments •Lack of Investment •Highly agile in dynamically •Speed and Performance sharing resources with multiple •Reliability and Security customers •Legacy systems •Cost efficient •Pay-for what is used •Internet accessible •Maintenance
- 6. Software as a Service (SaaS) A software application is offered as a service via an Internet connection. Infrastructure Storage Application Platform Functionality Application User Interface CLOUD API
- 7. Platform as a Service (PaaS) The six key elements of Platform of a Service are: •Integrated environment •User experience •Built-in management features Infrastructure •Built-in integration Storage Platform •Support collaboration •Deep application instrumentation
- 8. Benefits of PaaS • Each platform component is a service • Supports entire application lifecycle • Utilises same IDE environment • Multi-tenancy • Pay-per-use pricing model • Decreases Total Cost of Ownership • Built-in elasticity • Supports agile software development • Supports rapid development and deployment • Rapid configuration changes
- 9. Providing the Best Experience A PaaS solution has two user bases: •Software developers using the platform to build & deploy an application; and •Users actually using the application.
- 10. Infrastructure as a Service (IaaS) IaaS offers organizations the option to outsource the equipment needed to support their business operations. Platform Application Infrastructure Functionality Storage User Interface CLOUD API
- 11. Managing IaaS as a Customer What to manage: •Unauthorised use of cloud services •Organisation change and adoption of cloud •Business value of using public clouds
- 12. Managing IaaS as a Provider What to manage: •Assimilation of cloud architectures •Internal and external usage of cloud resources •Support from public cloud resources •Recovery of infrastructure and support costs
- 13. Thank you
Editor's Notes
- Hi and Welcome to this program from The Art of Service\n\nWelcome to the first program in the Cloud Computing Certification series. This course will help you to understand the different components of cloud computing and how the services that utilize “the cloud” could be managed effectively. \n
- A useful analogy to use in understanding cloud computing is the utility service for electricity. A strong comparison was first introduced by Douglas Parkhill in 1966 which mentions many of the characteristics of modern-day cloud computing \n\nAt the start of the industrial Revolution, most manufacturing companies were creating their own energy. When power plants came, however, a ‘Grid’ was formed that delivered electricity to houses and plants. This gird interconnected the different power plants to each other and provided power redundancy. Residential and businesses were charged for what they used. Initially there was a lot of resistance. Some arguments were that it was:\n Too expensive\n Not secure enough\n Not stable / available enough\n\nBut nowadays everybody accepts the electricity delivery method as normal... The idea is that storage and processing power will be delivered in a similar fashion. There will be large organisations creating and managing the IT service where everybody else uses the output from the Internet, a “grid” of networks. IT connectivity becomes a utility, just like power.\n\nOnly when you consider disaster situations and how to minimise the damage done or how to recover quickly from them you will consider electricity as something you need to generate and manage yourself. (via diesel generators or other solutions) as you can not assume that electricity is a given in a disaster situation. \n\nMany references discuss the cloud model as a form of utility computing, referring by analogy to the electric power grid. Generating assets move in and out of the grid seamlessly and all the user knows is that the light goes on when the switch is flipped and the bill comes every month for the kilowatts consumed.\n
- Before understanding Infrastructure as a Service (IaaS), one must have a basic understanding of cloud computing concepts and how IaaS fits into the general solution. \n\nCloud computing is the culmination of several technologies that have been used in IT environments for decades. As a concept, cloud computing represents a paradigm shift on how systems are deployed. As a technology, cloud computing refers to the applications and services running on a distributed network using virtualized resources and accessed using Internet protocols and networking standards. However, cloud computing is still quite young and, therefore, still being defined.\n\nIn September 2011, the National Institute of Standards and Technology (NIST) published their NIST Definition of Cloud Computing (NIST Special Publication 800-145) after several years of discussion. The definition provided a cloud model consisting of:\n4 Deployment Methods: Private, Community, Public, and Hybrid Clouds\n3 Service Models: IaaS, PaaS, and SaaS\n5 Characteristics: on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service\n
- The NIST definition identifies four deployment models: public, community, private, and hybrid clouds.\n\nPublic clouds are designed for open use by the general public. The public cloud exists on the premises of a business, academic, government organization who owns, manages, and operates the offering. \nCommunity clouds are designed for exclusive use by a specific community of users from organizations with shared missions or concerns. One or more of the organizations may own, manage, and operate the offering or it may be provided by a third party provider or a combination of the two. The solution may exist on or off the premises.\nPrivate clouds are designed for exclusive use by a single organization comprised of multiple consumers. The offering may be owned, managed, or operated by the organization, a third party, or a combination of the two. The solution may be found on or off premise.\nHybrid clouds are a combination of public, community, and private clouds, bound together using standardized or proprietary technology for data and application portability. A hybrid cloud must be a single entity that remains unique. \n
- The prevailing question in the argument for using private clouds over public clouds focuses on the issues with public clouds. \n\nWhile clear advantages exist for using public clouds, specifically cloud solutions where the infrastructure is shared among multiple customers, they have their disadvantages too. The most prevalent disadvantage is the lack of control over the data used within the cloud solution. Highly regulated industries must be responsible for the level of access public entities have to sensitive data. While the public cloud itself may be highly security, the WAN connection between the cloud and the business is still exposed. The backups and redundancy required by regulations may be insufficient from a public cloud provider; and if provided, may be more expensive than a private cloud. Many of the issues presented below support the lack of control issue.\n\nScalability within a virtual environment can happen on three levels: vertical scaling, horizontal scaling, and instance expansion. Most providers of a public cloud will easily offer vertical and horizontal scaling. This means they can provide a larger or smaller instance based on the customer’s requirements and they can increase or decrease the number of instances required by the customer. Unfortunately, most public cloud providers will not provide “instance expansion”, the ability to add resources within an instance. Therefore if an instance is constructed with a dedicated 2 GB of memory, the customer who requires 3 GB of memory for a short time during the instance session will not have it. When “on-demand” solutions are offered, the per-hour compute cost is generally higher than when “reserving” resources. So while cloud computing is highly scalable, the practices and service offerings of the cloud provider may not. \n\nSince public cloud providers are in the business of providing cloud services, some expectation is present that the charges for using those services will be inflated somewhat to cover staff, maintenance, and growth. Generally speaking, these charges will be less than the costs of providing the same service in a traditional IT environment over a short period of time. However when looking at the long-term use of cloud resources, the cost of using public cloud resources may be higher than creating the infrastructure for a private cloud. While there is no capital expenditures in using a public cloud, the operational costs can be significantly higher than a private cloud using either purchased or leased equipment. \n\nPrivate clouds are typically onsite to the business and will not require the use of a WAN connection. Public clouds will always utilize the WAN connection. Communicating over a long distance is recognized as slow. The data transfer rate across the WAN is dependent on the capabilities of the Internet Service Provider (ISP) in the area and usually tops out at 10mbps. The speed and performance requirements of some applications may not support the use of a public cloud because of the distance and ISP limitations, specifically those applications that support and use large data files, such as video. \n\nBusinesses tend to put more automation and controls in place than the minimum business requirements require: the practice is not bad because it falls inside the concept of optimizing the service, but the practice does show an area of concern related to using public resources – reliability and security. For public clouds, the reliability and security of the cloud is shared by all customers and will not change across the cloud. The service provider may make the cloud more reliable and more secure and the benefits of such actions will be shared across all customers and reflected in the pricing of the cloud services. To keep prices lower, a cloud provider is opt to support the minimal reliability and security requirements they can for their customers. While this appropriate for most situations, some applications and businesses require a greater level of reliability and security over time. Public clouds will not support these higher requirements. As a general rule, private clouds will be more reliable and more secure than public clouds because the private cloud is catering to the organization’s maximum requirements in this area.\n\nLegacy systems are not a good fit for public cloud support. With most legacy applications, the design of the application has a high degree of integration with the hardware, middleware, and operating system. Public clouds will typically provide “generic” abstractions of an infrastructure that is attractive to the majority of potential customers. Businesses will need to re-engineer the applications to utilize these generic abstraction or custom create an abstraction to support the legacy application. Custom abstractions require control over the virtualization controls of the hypervisor and will require establishing a private cloud in most cases. \n\nUsing a public cloud is not without its benefits and, in many cases, will provide most businesses the needed services they require. Unfortunately, the use of a public cloud is not always the best choice in particular situations and a business should consider if a private cloud solution is acceptable. \n
- Software as a Service (SaaS) is a software deployment opportunity where an application is hosted into the Internet environment. Once there, the application is available to users throughout the Internet without any need for the user to install or run the application on their own computer. As a result, the user does not have to be concerned with maintaining the software, its operations, or support. SaaS is a pay as you use service, meaning that initial purchase of software and its license is not required, rather the charge is a continuous charge, usually monthly, to use the application without any contract. \n \nFor software vendors, SaaS is an attractive solution because of the promise of stronger protection of its online intellectual property and an ongoing revenue stream. They can host the application on its own web server or allow it to be handled by a third-party application service provider (ASP). As a result, the term “software-as-a-service” is sometimes diluted as it has two meanings. It can speak to the application itself and the environment hosting the environment. The second situation is also referred to as a platform and is sometimes interchanged with platform-as-a-service. To combat this problem, some have started to use the terms “SaaS” and “SaaS platform” to distinguish between the two situations. \n\nRemember add-on development platforms from the last slide. Salesforce.com is a SaaS application and Force.com is the PaaS. As soon as a developer creates an add-on for SaleForce, they could potentially repackage the entire application and market it as a different application with SaleForce as its core “engine”. These enhanced and repackaged SaleForce-based SaaS applications are typically found in a market place run by Salesforce called AppExchange. For NetSuite, the marketplace is called SuiteApp.com. This is the “SaaS platform” previously mentioned.\n\nFor most end-users, the mechanics “behind the cloud” is not important as long as they can access and use the application effectively. For business management, the mechanics may provide a list of concerns and assurances about the product being used. It is important for the business to understand the actual scope of the service provider. Are they a true SaaS provider who provides the entire application and infrastructure required to support the business or are they a “software vendor” offering an application on another service provider’s infrastructure? The answer will influence many of the terms within the service level agreement. \n\nThe answer is also important for determining the “proper” interface for the business. For the end-user, accessing the application from the user interface is all that is required. But for a business, some other processes may require a “back office” interface to allow other systems used by the business to communicate with the SaaS application. Like other service models, this interface is defined by the Cloud API. However, in a situation with a software vendor using another provider’s infrastructure, is the Cloud API provided by the software vendor, the service provider, or both.\n
- As developers and businesses look into cloud solutions with more vigor and greater attention, there are increasingly more gaps being identified. Pay-as-you-use services for software, storage, computing, and even CRM (Customer Relations Management) are having greater success as time goes on. However, these services still only represent pieces of a larger solution. Platform-as-a-service has the ability to encompass all of these services plus more. A cloud platform includes all the systems requires to manage the entire life cycle of a web application. Bungee Labs have identified six key elements such a platform. to the most inclusive Platform-as-a-Service (PaaS) offering possible today:\n\nIntegrated environment\nThe first element of a fully functional platform is the ability to develop, test, deploy, host, and maintain the application in a single environment. The places a considerable amount of burden on the developer in terms of hardware, maintenance, and configuring to ensure that application moves through its life cycle. \n \nUser experience\nThe experience the developer has using the platform is critical to the success of the PaaS service. Most developers move from one project to the next, so repeat business is a considerable factor. But from the developing perspective, having the tools and capabilities available to move the application through its life cycle is extremely important. It's like using DOS and Windows. Though DOS allowed a computer user to perform most functions required at the time, the introduction of the Windows operating system made those functions easier to perform and with a more pleasant experience.\n \nBuilt In Management Features\nDevelopers and businesses have to deal with a number of different variables throughout the life cycle of the application which requires considerable attention to those factors that can adversely impact the proper functioning of the application. Of these, scalability is a major factor, as well as reliability and security. These factors should be built into the platform without any need to develop, configure, or in any way spend any time, cost, or effort away from the application itself. \n\nBuilt In Integration\nVery few applications are developed in complete isolation. The need to connect to external sources for dynamic data, updates, even third party web services is very much a required consideration. Specifically for applications depending on real time data, the platform needs to allow direct and continuous connection to external sources.\n \nSupport Collaboration\nIn the same way applications are not developed in isolation, developers do not work in isolation. Most software development projects are a collaboration of several individuals throughout the entire life cycle of the application. This collaboration is a mixture of formal and on-demand occurrences that require the ability to communicate effectively while maintaining the security and performance of the application code.\n \nDeep Application Instrumentation\nSoftware development no longer ends upon the deployment of the application. As much as a developer or business would like to think that they have introduced a perfect application into the marketplace, this is rarely true. How the application is used, the performance, and reliability issues are all concerns that software manufacture would like to monitor. A platform-as-a-service would have a full set of instrumentation in place to handle this monitoring to effect improvements.\n
- A particular PaaS environment allows the development, testing, deployment, and management of applications using cloud resources. The benefits of a PaaS service model are:\n\nREAD SLIDE\n
- A PaaS solution has two user bases. The first set of users is the software developers using the platform to build and deploy an application – software developers. The second set of users is the people using the application – the end user. Some providers have recognized a potential third set of users who are interested in understanding how the application is performing and the data it is generating – the business manager. The provider of a platform-as-a-service offering must be concerned with all sets of user s when maintaining the environment.\n \nThe first concern with user experience is realizing the extent in which users tend to multi-task during the day. For the end-user, these can be a variety of tasks ranging from data entry, to reviewing a document, to some form of communication like instant messaging or email. The software developer can be working on building code and needing resources to understand the code better, debug the code as its written or find examples of similar code. Business managers are performing multiple queries, looking for trends and problems, and compiling data for future reports. The work each of these users perform may be contained within the platform environment or strung across several resources available to the user. Working within the platform should facilitate key multi-tasking activities for each set of users. This can be done simply by allowing the user to go outside of the platform to find the resource and use it. A interface for the user could pull those resources into the interface so that the user does not have to change windows. To enhance the user's experience, the interface could be configured to automatically pull those resources together based on what the user is currently working on.\n \nNo matter the task or the user, the core component of the user experience is the user interface. The interface should be intuitive and easy to use. It should allow the user to customize views based on their work habits, without sacrificing functionality. Once configured by the user, the interface should retain the settings for following sessions. Many interfaces provide embedded applications, like Microsoft Word or Excel, or Adobe Acrobat so that the user's system is not bogged down by running multiple applications.\n
- Infrastructure as a Service offers organizations the option to outsource the equipment needed to support their business operations. This can include storage equipment, hardware, servers, and networking components. \n\nThe organization pays the service provider for the use of the equipment, and the service provider maintains ownership of and responsibility for the equipment, meaning that the service provider houses and runs the equipment, as well as being responsible for maintaining it. Traditionally, businesses would lower capital spending by leasing equipment and they could use and manage the equipment as they desire. IaaS is not a leasing agreement in the traditional sense because they are not only outsourcing the equipment, but the management and optimization of the equipment. \n\nIn this service model, the request from the customer is for an computing infrastructure with associated storage, but the customer will provide the platform and applications. The customer is responsible for everything running on top of the infrastructure. However, remember applications require storage to function optimally. To facilitate the interchange between the customer’s applications and platforms and the service provider’s infrastructure, the cloud provider will provide a “Cloud API”. \n\nConsider two IaaS providers who are using the same types and numbers of servers, storage devices, and network components. The same customer is running the exact same configuration of applications and platforms at the similar levels of demand. Instinctively, one might assume that the performance of each environment would be the same, but this is not necessarily true. The interface, the Cloud API, between the customer and the service provider can be distinct enough that the actual performance for the customer is impacted. \n\nThe Cloud API provided by different service providers are not the same. It is the responsibility of the customer to ensure the products and services they place on the infrastructure can appropriately communicate with the Cloud API. \n
- As a customer of IaaS, most of the responsibility of managing the infrastructure is placed on the service provider; however, how the infrastructure is used is still within the management scope of the consumer. Within this context, it is important that the purposes for using a cloud infrastructure and the capabilities of the cloud infrastructure match. Looking at the fabric of the infrastructure (computing, network, and storage) the availability of the required resources should be pursued. In many cases, a cloud provider may focus on computing resources, but not storage resources or vice versa. This can cause problems over time if the need for additional storage increases. At present, very few service providers provide support all areas of the fabric.\n\nLooking at the situation honestly, it is likely that some adoption of multicloud or hybrid cloud support is taken to ensure the entire infrastructure fabric is in place. Because of the competitive relationship between commercial cloud providers, any hope of cooperation between providers to support a federated solution is improbable, though some cloud providers have started to create strategic alliances to this effect. If the customer does not or cannot want for such events to happen, the effort to federate the cloud must occur in-house. In this manner, the cloud solutions are simply an extension of the organization’s existing infrastructure. \n\nAt this point, the in-house infrastructure must be evaluated. While it is possible to maintain a traditional IT environment where some business services are provided by a cloud or resources to the business are available through a cloud, extending the infrastructure may have additional challenges in this situation. At the same time, transforming a traditional infrastructure to a cloud-based infrastructure will provide a tighter coupling in a federated solution, the organization will have to incur some change in adopting new policies and standards consistent with building a cloud. This change may require new skills and knowledge for the organization. In addition to infrastructure changes, the adoption of new designs and practices may require significant redesign of applications and business systems.\n\nThe severity of the change will be based on how deeply the organization wants to adopt cloud computing as well as whether the organization has already been using technologies and practices consistent with a cloud computing. If the organization already utilizes virtualization in some infrastructure components, but not all; they will have an easier path to adopting full virtualization than an organization which has not used virtualization at all. \n
- For our purposes, any organization establishing a cloud infrastructure is considered a service provider; whether their customer is an internal employee or external consumer. Many commercial service providers started out by adopting cloud computing as a means to optimize their internal IT organization and found they could provide the same services in the marketplace. Tactically, the adoption of cloud computing has little differentiation relative to whether the customer is internal or externally located. At the same time, the processes associated with managing an internal cloud infrastructure has minimal differences from managing a traditional infrastructure. A common viewpoint is the cloud computing is an optimization of the older infrastructure models. \n\nThroughout this course, we have addressed several concerns that are relevant to organizations wishing to adopt a private cloud. Those greatest concerns are summarized here:\nTraditional versus cloud – one of the first concerns for an organization is to determine what business processes will be supported using cloud resources and how much of the traditional infrastructure will remain. Strategically, the organization may be driving toward the full support of the cloud, but realistically the fulfillment of this may take some time. The migration from traditional support to cloud support will have to be prioritized and managed appropriately. The migration of some legacy systems may be more expensive than utilizing a net-native application with the same functionality: the deciding factor dependent on how easily the data from the old system can be migrated to the new system.\nIn-house versus market – in conjunction with the previous concern is whether the cloud infrastructure will be used for internal customers only or will also support “public” usage. The applications and business supported by the cloud may provide many of the answers in this concern because the audience is already established, but the provisioning of the cloud may open opportunities that were not practical previously. The adoption of the cloud may be driven by the pursuit of such an opportunity.\nPublic cloud support – some reasonable assumption can be made that the organization is already utilizing cloud resources from several public cloud providers. A decision to continue using these public clouds or bringing supporting internally may be required. A possible driver for using a private cloud may be present if the use of a public cloud is counterproductive or risky, but the organization likes the benefits they are obtaining from its use.\nCost recovery – managing IT requires some effort to recovery costs for the investment and operation of the infrastructure and support. The use of cloud resources does not change this financial imperative; however the cloud computing model may force a re-evaluation of the accounting, chargeback, and billing methods of the organization. Techniques and ability to more accurately measure service may provide better cost models for the financial department and service delivery.\nFederated clouds – larger corporations may have to deal with multiple private infrastructures and/or private clouds. Incorporating all the previous concerns, some effort may be required to create an enterprise-wide cloud computing solution. This is especially true if attempts in cloud computing are made at a department level, a line of business, or individual datacenters where interfaces with other parts of the organization must be considered. \n
- Well done again for completing this program, we wish you the best of luck for your next program, and every success in your furture Cloud Computing career!\n