Enterprise Ready OpenStack, Wiekus Beukes, Oracle

Editor's Notes

• #3: This is a Title Slide with Picture slide ideal for including a picture with a brief title, subtitle and presenter information. To customize this slide with your own picture: Right-click the slide area and choose Format Background from the pop-up menu. From the Fill menu, click Picture and texture fill. Under Insert from: click File. Locate your new picture and click Insert. To copy the Customized Background from Another Presentation on PC Click New Slide from the Home tab's Slides group and select Reuse Slides. Click Browse in the Reuse Slides panel and select Browse Files. Double-click the PowerPoint presentation that contains the background you wish to copy. Check Keep Source Formatting and click the slide that contains the background you want. Click the left-hand slide preview to which you wish to apply the new master layout. Apply New Layout (Important): Right-click any selected slide, point to Layout, and click the slide containing the desired layout from the layout gallery. Delete any unwanted slides or duplicates. To copy the Customized Background from Another Presentation on Mac Click New Slide from the Home tab's Slides group and select Insert Slides from Other Presentation… Navigate to the PowerPoint presentation file that contains the background you wish to copy. Double-click or press Insert. This prompts the Slide Finder dialogue box. Make sure Keep design of original slides is unchecked and click the slide(s) that contains the background you want. Hold Shift key to select multiple slides. Click the left-hand slide preview to which you wish to apply the new master layout. Apply New Layout (Important): Click Layout from the Home tab's Slides group, and click the slide containing the desired layout from the layout gallery. Delete any unwanted slides or duplicates.
• #4: This is a Safe Harbor Front slide, one of two Safe Harbor Statement slides included in this template. One of the Safe Harbor slides must be used if your presentation covers material affected by Oracle’s Revenue Recognition Policy To learn more about this policy, e-mail: [email protected] For internal communication, Safe Harbor Statements are not required. However, there is an applicable disclaimer (Exhibit E) that should be used, found in the Oracle Revenue Recognition Policy for Future Product Communications. Copy and paste this link into a web browser, to find out more information.   http://my.oracle.com/site/fin/gfo/GlobalProcesses/cnt452504.pdf For all external communications such as press release, roadmaps, PowerPoint presentations, Safe Harbor Statements are required. You can refer to the link mentioned above to find out additional information/disclaimers required depending on your audience.
• #6: Forrester interviewed OpenStack end users and 10 OpenStack ecosystem vendors to discuss the best practices and common pitfalls faced when adopting OpenStack. Direct adopter competency takes four to six months. You’ve likely heard stories about eBay, CERN, Comcast, and PayPal adopting OpenStack directly to completely avoid vendor lock-in. Their stories didn’t happen overnight. It took months for them to develop a center of competence and select the right team to support their efforts. Once enterprises train members of the team, some find it hard to retain them, given the high demand for trained OpenStack engineers. For many enterprises, the challenges ahead seem too daunting without a vendor distribution and/or services to accelerate their journey. Building a low-cost environment for your systems of engagement apps. Some view OpenStack as a cost-effective cloud platform in a larger cost-conscious technology build-out. Many OpenStack-focused enterprises on a minimal budget seek to develop a net-new scalable environment to host future use cases. These enterprises anticipate exponential growth with no clean ties to increased revenue. Making the conscious decision at the forefront of this movement to minimize technology dependencies and use open technology is central to many OpenStack build-outs. For many, this exists at the front of a larger DevOps movement built on the philosophy of speed, automation, and open source tools
• #7: We are looking at the Operational Challenges while recognizing that there are technical issues as well such as Networking (Neutron/SDN) for large scale deployment, Security requires due diligence, etc It's not shrink-wrapped software it's made up of several different modules that all need to be configured and learn to talk together.“ Keeping up with releases and updates is difficult for most enterprises. In theory, running small monthly upgrades and larger six-month upgrades makes a lot of sense. With development organizations moving toward continuous delivery for internal apps, they’re constantly fixing bugs and frequently releasing updates. This high-velocity cadence implies that a frequent update cycle for OpenStack is in everyone’s best interest. In reality, most I&O professionals aren’t quite ready for this switch. As such, OpenStack users typically stay six months behind releases and worry about their long-term ability to keep on course with the rapid releases. DevOps efforts are helping, but most adherents are not yet able to digest the full impact of continuous delivery Direct adopter competency takes four to six months. You’ve likely heard stories about eBay, CERN, Comcast, and PayPal adopting OpenStack directly to completely avoid vendor lock-in. Their stories didn’t happen overnight. It took months for them to develop a center of competence and select the right team to support their efforts. Once enterprises train members of the team, some find it hard to retain them, given the high demand for trained OpenStack engineers. For many enterprises, the challenges ahead seem too daunting without a vendor distribution and/or services to accelerate their journey.
• #11: Talk about simplifying the deployment.
• #12: We are using Docker as a virtualization technology for our continuous delivery/deployment pipelines. Every time we build, we want to run build scripts in their own Docker containers, perfectly isolated from other builds in other projects. There are three main reasons. ## Image Repository Docker enables image sharing through its public repository at hub.docker.com. This means that after I prepare a working environment for my application, I make an image out of it and push it to the hub. That’s it. From now on, we will use my custom Docker image with pre-installed tools and packages, in every build (merge, release, deploy, etc.) Moreover, if and when I want to add something else to the image, it’s easy to do. I just start a container from the image and install Ruby into it. Then, I push a new version of the image to the Hub. On the next build, we will pull a new image from the Hub and will use it. ## Versioning Every change to a Docker image has its own version (hash) and it’s possible to track changes. It is also possible to roll back to any particular change. With this feature, we are able to control their build configurations with much better precision. ## Application-Centric Docker, unlike LXC or Vagrant or EC2 instances, for example, is application-centric. This means that when we start a container — we start an application. With other virtualization technologies, when you get a virtual machine — you get a fully functional Unix environment, where you can login through SSH and do whatever you want. Docker makes things simpler. It doesn’t give you SSH access to container, but runs an application inside and shows you its output. This is exactly what we need. We need to run an automated build (for example Maven or Rake), see its output and get its exit code. If the code is not zero, we fail the build and report to the user. Maven starts immediately. We don’t worry about the internals of the container. We just start an application inside it. This is what application-centric is about.
• #13: green = provided by kolla blue = provided by open source software other than Kolla Workflow: Dev pushes a change to gerrit. The changes is reviewed gerrit merges with git repo cd pipeline produces packages cd produces docker images based on the packages cd pipeline pushes image to private docker registry cd pipeline kicks off an image update on nodes ansible uses compose on each node to update the compose env and use the compose yml to launch an update update = Ansible calls compose pull and up on each container under management
• #18: Building OpenStack Cloud is not shrink-wrapped software it's made up of several different modules that all need to be configured and learn to talk together - Updates in the distribution releases Impact on all other plug-ins and software tools , middleware, database, applications, management each with its own product life cycle – difficult to synchronize update to the Cloud Solution Business Models Evolving, community version, enterprise version or hardened version Free trial but very limited time
• #21: For Application Provider: Mechanism to publish applications and services, including deployment rules and requirements, suggested configuration, output parameters and billing rules. Track billing and usage information. For user Find and self-provision Enterprise applications and services, integrate them into their environment, and track usage information and costs.
• #23: Enterprise customers widely use MySQL Cluster for HA and are requesting its support for OpenStack HA for enterprise usage scenarios where these advantages are needed:Real-time performance, Write scaling with auto-sharding, 99.999% availability Online scaling and schema operations, SQL and NoSQL APIs InnoDB, storage engine for MySQL Galera, is hard coded in several modules in OpenStack. Oracle is working on providing support of MySQL A/A cluster, that uses NDB storage engine for HA, and contributing upstream the Docker container images for it All API requests from the OpenStack services go through HA Proxy. data is stored in pairs of storage servers for HA. Load balancing between the servers is done via HA Proxy. - scaling for performance is easily achieved by online addition of the data nodes