Running SAP on SUSE Cloud 2.0

Editor's Notes

• #5: Prior to cloud computing more and more conversations between IT and the Line of Business started to look this way. Walk through the conversation. So developers and the Line of Business moved to the cloud.
• #6: Now let's take a step back and discuss some of the basics of cloud computing. Cloud computing can take place outside your company or inside your firewall. In general, the options are: Public Cloud Computing. The cloud infrastructure is owned, managed, and operated by a cloud service provider and runs on its premises. Resources are typically delivered on-demand through a public portal. Private Cloud Computing. The infrastructure is owned managed and operated by an organization for its own use. Ownership, location and operation can be outsourced to a third party, but the overall responsibility for definition of services and acquisition of physical resources remains with the enterprise. And then there is hybrid cloud computing, which allows a user to access public and private cloud resources from a single management environment. This provides more flexibility to organizations that have a wide range of workloads and a highly dynamic environment. Also, there are three distinct types of IT services that enterprises both deliver and use today, through public, private and hybrid cloud computing models: The first is Software-as-a-Service or SaaS. SaaS enables users to access an application, but have little to no control over the delivery of the application. An example of SaaS is Google Mail or SalesForce.com. The second is Platform-as-a-Service or PaaS. PaaS enables users to deploy onto the cloud infrastructure applications they have created or acquired through a framework of programming languages, libraries, services, and tools supported by the provider. The user has control over the deployed applications and possibly configuration settings for the application-hosting environment, but not the underlying infrastructure. An example of a public PaaS is Windows Azure or CloudFoundry. An example of a private PaaS is the Windows Azure Platform Appliance. The service model that is most widely viewed as “a cloud” is Infrastructure-as-a-service or IaaS. An IaaS cloud enables a user to dynamically provision computing, storage, networks, and other fundamental computing resources where the user does not manage or control the underlying infrastructure. The most common use case is the provisioning of a virtual server by a user, who then adds an OS and application to run on the virtual server. <number>
• #7: Other organizations are also beginning to see the benefits of private cloud. Over time more and more enterprises are making a private cloud implementation in their data center a priority. Forrester, recently provided an update to this study and it showed that the number had grown to 46%.
• #8: However, by deploying a private cloud you can also meet the needs of the business, while lowering costs. But, you can achieve this without losing control of your data, or opening your enterprise up to security risks. As with all technology innovation, Private Cloud lowers costs. Through automation and orchestration Private Cloud promises to provide improved server utilization rates. Automation when combined with the self-service features of cloud computing that enable private cloud users to provision and configure servers themselves will allow your IT department to become more efficient and free-up staff for other higher value activities even as you scale out your cloud environment. But, the real benefit of the private cloud is to be able to respond to the needs of the business more rapidly using your enterprise's infrastructure, security measures, and compliance protocols.
• #9: Let's go one level deeper into the technical differences in the various types of clouds. If you look a full application stack, you start at the bottom with the physical infrastructure – servers, the network, and storage. Since we are focused on virtualized infrastructure, the hypervisor is really part of the lowest level of service delivery. Looking at the left, this is what an IaaS provider such as Amazon delivers to the customer. Everything above the hypervisor including the VM and the OS is specified and operated by the customer. Looking at PaaS, the service provider picks up responsibility for the VM, OS and middleware, leaving the customer to focus on just the data and applications. Note that the applications are developed for the specific PaaS environment that the service provider uses. Going one step further, in a SaaS model, the service provider is responsible for deploying and maintaining the entire stack – The customer just adds users.
• #10: Contrasting this with the private cloud, let's start at the right hand side of the slide with SaaS. This is the development model for most businesses today – IT is responsible for deploying, managing and maintaining everything. The LOB just provides users. In other words, IT is a SaaS provider today. The drivers that we discussed around cloud are really discussions of how IT moves toward IaaS and PaaS by establishing user interfaces that enable the LOB to take more control over the entire solution. In effect, the role of IT becomes identical with the role of an external cloud provider. The corollary of all this is that the Line of Business needs to be prepared to take ownership of the tasks outlined here for either IaaS or PaaS.
• #11: SUSE Cloud is our OpenStack distribution and uses Crowbar as part of the install framework to help simplify the installation and ongoing management of your private cloud environment. SUSE Cloud delivers on the promise of a private cloud by allowing you to deploy a secure, compliant fully supported cloud environment within your firewalls. By using SUSE Cloud IT and the business can work more closely together. They can react quickly to changing business demands and reduce costs by automating the creation of virtual servers and deploying workloads on them. Utlimately, SUSE Cloud will allow you to be the cloud service provider of choice for your enterprise.
• #12: This is why. OpenStack has the greatest industry support and most vibrant community among open source cloud software projects. The most recent release, Grizzly, had contributions from 517 developers from 180 companies. In the long-run the vibrancy of the community will lead to more rapid innovation than competing projects and even proprietary solutions When we were formulating our private cloud strategy we went and spoke with our customers and they wanted to know what was our OpenStack solution. So, customer demand is really driving our participation in OpenStack Finally, the formation of the OpenStack Foundation helps to ensure: The long-term viability of the project and that the project's development goals benefit the industry and not one vendor – unlike CloudStack and Eucalyptus Our developers find this to be the most professional community because most contributors come from vendors and are committed to solving user issues.
• #13: SUSE is an original platinum member of the OpenStack foundation. As such, we provide legal, engineering, and ongoing financial support to the foundation. Alan Clark, who also sits on the board of the Linux Foundation, is the Chairman of the OpenStack Foundation's board. His experience working on behalf of SUSE within other Open Source communities proved invaluable during the formation of the foundation. His colleagues recognized this and voted him as chairman. SUSE has focused its technical contributions to date on making sure OpenStack is enterprise ready. Security and hardening of the code. Easing deployments and ongoing maintenance Ensuring multi-hypervisor support by upgrading OpenStack support for Xen and working with MSFT to ensure full support for Hyper-V. We will continue to provide code and feature contributions in future releases. Ultimately all of this is to ensure that we have the most enterprise ready OpenStack distribution
• #14: But, why do you need a distribution? Enterprises don't download the Linux Kernel from kernel.org and deploy. What you see in Orange is OpenStack. It is like Kernel.org To make OpenStack usable you also need other items. You need servers. OpenStack needs to run on an OS and a hypervisor or two. You need a messaging service and a database. And you need all of these items and support for all of these items integrated together. And you also need an install framework to ease the initial set-up and ongoing use of the cloud. And then you have other management tools that need to integrate seamlessly into your private cloud environment and be fully supported. Piecing all of this together yourself and getting it deployed can be costly and time consuming.
• #18: When building a private cloud, many organizations start with solutions that fit their existing Virtualization standards. More and more organizations are finding that mulitple hypervisors exist in different departments or divisions, which over time they would like to include in their private cloud strategy. The hypervisors used today, will evolve, there will be new technologies that emerge, and a private cloud strategy that takes this innovation and evolution into account will best serve the IT organization. As private clouds begin to share workloads with public clouds to form a hybrid clould, support for mulitple hypervisors will create flexibility and choice.
• #19: Goal: Comprehensive solution for managing the whole lifecycle of Operating Systems and core applications anywhere in the Datacenter or Private or Public Cloud Build with Studio, run in any cloud, including a SUSE private cloud offering, manage and orchestrate with SUSE Manager SUSE Manager engine with API to the Linux Systems Management Engine SUSE Manager UI extends into Portal for your IT organization Workflow engine
• #20: SUSE Studio is a tool that provides a wizard style interface that helps developers create a custom image built on SUSE Linux Enterprise Server. Using Studio, IT or line of business developers configure the operating system and add application-specific packages and middleware. They can build an image that is ready to run on SUSE Cloud or public clouds such as Amazon EC2. Then, deploy the image to those environments with a single click. This new workload is then stored in the image repository. From there, the user can use SUSE Cloud to set up a new server and deploy the image onto the cloud. By storing images in a single repository, it's easy to share images, modify them for different uses, or deploy them through automated tools in response to demand spikes.
• #21: SUSE Manager is the ideal solution for managing large numbers of virtual servers running in a cloud environment. It helps enterprises easily update all of their Linux workloads. This ensures the performance and security of the workload and aids compliance with both corporate and external regulations. Using SUSE Manager, you can easily update and monitor all of their Linux workloads, ensuring a continued, harmonious cloud. SUSE Cloud, combined with SUSE Studio and SUSE Manager, provides an enterprise ready, stable cloud environment for any organization.
• #22: SUSE Cloud is an Infrastructure-as-a Service private cloud solution for the enterprise. Combined with SUSE's tools SUSE Cloud enables the implementation of an automated cloud-centric life management. That simplifies the overall life cycle management. Build: Developer creates new: Application Middleware library Uses automated tool to: Specify dependencies, Create packages with meta-data Adds package to repository Image creation: Developer creates OS image containing: Application, Middleware, OS, Management instrumentation Uses automated tool to: Resolve dependencies, Add needed packages ,Configure/create image in required format(s) Specify needed virtual resources Adds image to test image repository Cloud Enabled QA - QA Team can spin up a virtual environment including 10s or 100s of VM - Once testing is complete images are placed in public repositories for deployment Deployment and management - LOB or IT can select and deploy images as needed through a self-service interface - Images will automatically register with the management tool for monitoring and ongoing Maintenance.
• #23: In addition to the APIs and repositories that improve the cloud workflow that we already discussed, the service centric cloud need a new set of APIs to locate, configure and connect to services. In addition to the repositories that hold deployable images, the predefined services will exist in the cloud. As SUSE continues to develop our private cloud offerings we will do so with a focus on ensuring smooth delivery of IT services to the Line of Business.
• #25: The Compute Nodes are the pool of machines on which the instances are running. These machines need to be equipped with a sufficient number of CPUs and enough RAM to start several instances. The Controller Node effectively distributes instances within the pool of Compute Nodes and provides the necessary network resources. The OpenStack service Compute (Nova) runs on the Compute Nodes and provides means for setting up, starting, and stopping virtual machines.
• #26: The Compute Nodes are the pool of machines on which the instances are running. These machines need to be equipped with a sufficient number of CPUs and enough RAM to start several instances. The Controller Node effectively distributes instances within the pool of Compute Nodes and provides the necessary network resources. The OpenStack service Compute (Nova) runs on the Compute Nodes and provides means for setting up, starting, and stopping virtual machines.
• #27: Demo of UI etc...