32. 32
Be sure to stop by the IBM booth to see some demos and get your rockin‟
OpenStack t-shirt while they last.
Thank you !
Editor's Notes
IBM is committed to accelerating the success of the OpenStack foundation because interoperability in the Cloud is critical for flexible cloud deployments and ultimately customer success. As a member of the new Board of Directors, our goal is to help progress the platform, sustain a vibrant ecosystem, and position OpenStack as the IaaS platform of choice for cloud consumers and providers. IBM made a commitment in March 2013that ALL of our cloud offerings would be based on OpenStack), including our private clousofferindsto our public cloud offerings (currently Softlayer), our optimized Pure Systems offerings (PureApp and PureFlex, etc) :which would be transitioned over time to be hosted on OpenStack.Out private and public cloud portfolios including Softlayer and IBM Cloud Manager are already incorporating these standards.
Cloud Foundry PaaSAn application runs in a DEA. The Cloud Controller orchestrates the routing and lifecycle of all DEAs in the pool. Routers manage application traffic. Health Manager reports mismatched application states to the CC. A servicegateway provides an interface for services (native or external). A messaging bus manages all system communication. Apps are accessed directly through the router while web and CLI clients access Cloud Controller via RESTful services.
Stock photos for IBMhttps://www-304.ibm.com/connections/wikis/home?lang=en-us#!/wiki/Wc2b28dd4ba19_4a82_a6c1_8aaee8ffc00a/page/Photography
Here we introduce some of the BOSH vocbulary as we will be using it in the course of the presentation.Stemcells: In a cloud platform, VMs are usually cloned from a template. A stemcell is a VM template containing a standard Ubuntu distribution. A BOSH agent is also embedded in the template so that BOSH can take control of VMs cloned from the stemcell.Jobs: A job is a collection of software which serves a particular purpose (e.g. MySQL or the Cloud Controller). At deployment time, each job will be install on its own stemcell VM.Releases: A release contains a number of jobs which can be deployed into the target environment. A deployment can consist of more than one release and not every job in a release must be deployed.Deployment Manifest: A deployment manifest is the set of instructions BOSH uses to create a deployment. It is written using the YAML format. The manifest file contains the following sections:NameReleasesCompilationUpdateNetworksResource PoolsJobsPropertiesSample WordPress Manifest FileSample Cloud Foundry Manifest File
Now delving more into technical details - we first need to have an OpenStack environment implmented and configured accroding to some of the requirements from Cloud Foundry, for example static ips and persistent disks, as well as the VMs should have connectivity to the internet. We also need to create some custom flavors for Cloud Foundry jobs, as well as the default scheduler for OpenStack needs to be set up so that it distributes VMs across different nodes in a random order.
Stock photos for IBMhttps://www-304.ibm.com/connections/wikis/home?lang=en-us#!/wiki/Wc2b28dd4ba19_4a82_a6c1_8aaee8ffc00a/page/Photography
The original OpenStack configuration supported generic high performance IaaS, PaaS, and SaaS workloads, but was not optimized for Cloud FoundryThe CloudFirst Factory was a cutting edge lab intended to incubate next generation cloud innovation on a clean slate provided by OpenStack (and other open source technologies) for the next release of SmartCloud Enterprise, IBM’s incumbent IaaS.The PaaS (a Cloud Operating Environment) effort competed with IaaS (SDE), SaaS (solution APIs), and other emerging cloud workloads such as Big Data and Analytics on OpenStack.[Diagram here]So while powerful, the CFF was not able to be tailored explicitly for Cloud Foundry (due to the other workloads and tenants on the cluster). This led to some particular bottlenecks and problems.
Messaging was a single point of failure, and since we were using Qpid on Red Hat, this was a less tested configuration than RabbitMQ on Ubuntu. In particular, a memory leak with Qpid on Folsom that were solved in Grizzly overloaded our head node often. [1] As an innovation lab, and since we were quite new to running OpenStack, we started simple and therefore did not use HA as our primary driver. The quickest time to value was a single Controller node and many Compute nodes. Therefore any issues on the head node (network, memory) directly affected the entire cluster.Also since we were responding to milestones to show innovation quickly, we did not enable complex storage configuration. No shared storage (that would support live migrations) and all of our Cinder storage was on a single node.The single Controller node architecture also had implications for network design, as all traffic flowed through the head nodeAt first everything was a bare metal process. In the lab, this wasn’t as much a cost implication, but it, along with resiliency and better distribution of resources gave us key lessons[1] http://www.zdnet.com/openstacks-top-operating-system-ubuntu-linux-7000027360/
So, based on those lessons on running Cloud Foundry in the Cloud First Factory, we derived some key areas for improvement.These fed into the architecture we selected for OpenStack on SoftLayer.Hardware and network selection Bare metal and virtual machine mix Networking components and designComponent distribution
Mitigated with Clustered NATS
Key Point:
9:00 - Getting from enterprise ready to enterprise bliss - why OpenStack and IBM is a match made in Cloud heavenAs a founding sponsor of the OpenStack Foundation, IBM's approach to OpenStack is simple - deliver high value contributions to OpenStack to make it THE best in class IaaS open source offering and then build IBM offerings on this foundation to deliver exception enterprise value to our clients. In this kickoff presentation for the IBM Track, Todd Moore, Director of Open Technologies and Partnerships, provides the answer to one of the most frequently asked questions - how is IBM adopting OpenStack across IBM Cloud Offerings? This presentation details the imperative of an Open Cloud Architecture to ensure interoperability and to avoid vendor lock in and sets the context for the IBM track sessions which provide a deeper dive on some of the IBM offerings shipping with OpenStack today including SmartCloud Orchestrator and SoftLayer.9:50 - IBM and OpenStack: Enabling Enterprise Cloud Solutions NowWhether you're just looking to get started with building your first OpenStack cloud infrastructure, or needing to expand your current project with additional capabilities - IBM has many ways to support you on your journey to a more open cloud environment. Need compute and/or storage hardware? This session will provide you with an overview of the portfolio of physical infrastructure options that IBM can deliver with OpenStack today (including the latest on Power8 and XIV Storage). Leverage existing IT infrastructure? IBM has the right mix of cloud solutions to help you make the most of your OpenStack journey . What's next, now? This session will discuss and demonstrate advanced scheduling, automation, and file serving capabilities that you can use with OpenStack today. 11:00 - Taking OpenStack beyond Infrastructure with IBM SmartCloud OrchestratorYou're using OpenStack as the infrastructure to build out your cloud environment. What a great choice !! Here are a few questions we think you should be considering:How are you connecting the services in your OpenStack cloud to your existing IT Management Systems like Monitoring, Backup, Patch?Are you providing a self service catalog for non-IT users to request services?Are you integrating with development tools for full lifecycle management of Heat Orchestration Templates?Can you deliver OpenStack through public, private, hybrid and expert systems? Come see how IBM SmartCloud Orchestrator can help you automate cloud deployed business processes, connecting your OpenStack environment to your Enterprise IT Management services.11:50 - IBM, SoftLayer and OpenStack - present and futureGet a detailed overview on why SoftLayer is the best global platform to build high-performance, highly-scalable OpenStack clouds, along with the latest advancements from IBM to improve the OpenStack experience in 2014. In this session you will learn how SoftLayer's commitment to bare-metal infrastructure can be leveraged to rapidly deploy OpenStack environments in near real-time with advanced capabilities like floating IPs, private and public networks across multiple regions or as an extension of existing, on-premises OpenStack installation. Additional topics include:- SoftLayer native capabilities through OpenStack APIs- How SoftLayer automation capabilities can save valuable time during the installation and setup phases- How open source projects can make it even easier to install and operate OpenStack on SoftLayerOther sponsored tracksRed Hat - full day Monday and TuesdayHP - Monday afternoonDell - Tuesday afternoonNetapp - Wed morning ( concurrent to IBM track )Intel - Wed afternoonVMware - Wed afternoon
Tempest: Integrated OpenStack TestingAn Overview of Cloud Auditing Support for OpenStackHosting hybrid (bare-metal + virtualized) applications on OpenStack Enhancing High Availability in Context of OpenStackTraining your cluster to take care of itself and let you eat dinner in Optimizing OpenStack for large scale Cloud Foundry deployments Turning the Heat up on DevOps: Providing a web-based editing experience around Heat templatesLinux Containers - NextGen Virtualization for CloudA practical approach to deploying a highly available and optimally performing OpenStack.Federated Identity & Federated Service Provider Support for OpenStack Clouds (joint IBM, and Rackspace)Network Policy Abstractions in Neutron (joint IBM, Cisco and Midokura)Hybrid Cloud with OpenStack: Bridging Two Worlds