Open Sourcing the Cloud - PuppetConf 2013

Notes de l'éditeur

1. All the discussion of mobile, cloud, big data Is Technology transforming the business. or business reqs driving technology transformation. Both.
2. CHAPTER 1: DEMAND IS CHANGING. But one thing is clear: - Expectations on IT are only increasing - Shrinking budgets (or best case flat) - 80% of IT dollars go to maintenance
3. Developers: need the physical resources (not 1 but hundreds per app) to develop, test and scale their apps access to the evolving technology on which to build them, from mobile to nosql In today's always connected competitive arena, the LOB need to drive customer engagement through an online presence, and this requires new applications and services IT is caught in the middle. Challenged w/ meeting the needs of the developer and the business External IT depts (clouds) servicing their devs better
4. First, insurmountable tasks are a job for open source. It has already delivered an open platform without which it is hard to imagine what IT would like. Open source has brought choice because of modularity of the components and robust interoperability and reconfigurability.
5. CHAPTER 2: FUNDAMENTALS ARE CHANGING. How does this become your reality? Evolution of IT. The era of specialized innovation in hardware platforms is nearing its end. True commoditization. The majority of today's innovation is now in software. 3 vectors of new IT. Compute, storage, and networking. All delivered through OSS, powered by RHEL, on standardized x86 kits. Not longer just replacing the legacy, but redefining the capability.
6. How do we organize compute-storage-network systems into a coherent architecture that can deliver on the dream of a truly agile datacenter? With OpenStack. OpenStack is a collection of projects for building an IaaS cloud. M aps well onto the architecture of deployment for s/w defined compute, storage, and networking Developed by a growing number of vendors and contributors, including Red Hat. Over 500 contributed to Grizzly. 2 months ago: —Grizzly. Red Hat #1. But it feels like day 2, we are just getting started Reminds us of another open project that succeeded beyond expectations—Linux.
7. Those are the primary components of OpenStack and the ones we will explore some more. OpenStack: Compute Nova: Core part of openstack, manages the compute tier The place where applications run The layer that when a user needs a virtual machines is responsible for allocating and delivering
8. Those are the primary components of OpenStack and the ones we will explore some more. OpenStack: Compute Nova: Core part of openstack, manages the compute tier The place where applications run The layer that when a user needs a virtual machines is responsible for allocating and delivering
9. To bootstrap an openstack cluster we first need to install RHEL (with KVM) on every Nova compute node. In the future Nova itself will be able to bootstrap the bare metal – 3-O.Today there are different tools for this – we use Foreman. Nova then provisions RHEL VMs (on behalf of user requests) – of arbitrary size in terms of mem/storage VMs are allocated ... also released . As more capacity is needed, more hardware can be provisioned into Nova nodes. This is cloud. Very dynamic infrastructure. VIDEO CUE: from RH IT – this is how we’re using puppet
10. VIDEO: from RH IT – this is how we’re using puppet. (Either Eric Brown or Jim Strong. Roughly 90 second video.
11. OpenStack: Storage Storage - 2 core storage services – SWIFT (large blobs, VMs, S3) & CINDER (storage volume as a service) GLUSTER – additive – cloud file service, multi-tenant & elastic, basis for RHS, plugs into OpenStack, optimizing it for Hadoop. Each independent of each other, and build in varying mechanisms for DR, scalability.
12. Objects, volume, files
13. OpenStack: Networking Neutron (formerly known as Quantum...) is the interface for networking services. Or “OpenStack Networking” but old habits die hard.
14. We need a dynamic network that is able to be reconfigurable as applications and data are provisioned. Traditional networking is very static This makes for an inflexible network when we are dynamically placing apps and data. Now within 1 physical system we are carving up with VMs, and we'd like each VM to be assigned to an arbitrary virtual network.
15. Neutron's job is to orchestrate the virtual network independent of physical network API (SDN) to configure; Plug-in architecture for speaking to different types of switches – s/w or physical Open vSwitch: we need logic within linux/kvm, as not all VMs are in the same virtual network OpenFlow – it is emerging as a standard for a switch API – whether virtual or physical
16. Challenge: But with a very dynamic network, how do you orchestrate actions? Need a way to interact with your infrastructure that is as dynamic as your network itself. On OpenShift, we use technology like MCollective and messaging technology like ActiveMQ to create the bridge between our operators and our infrastructure. It allows us to find and operate on servers, even when they are constantly changing. *Matt to send MCollective script.*
17. RDO – get a dist immediately into the hands of millions
18. An emerging space of distributed controllers for managing large scale environments. Most plug into neutron for OpenStack integration. Nicira NVP is a pioneer in this space, but there are others such from NTT, BSN. Open Daylight is a project to create an OSS network controller Video cue: Chris Wright
19. Video: Chris Wright
20. IT is now able to build private openstack clouds that deliver elastic services. Developers are no longer waiting on hardware services. But there still is a bit of impedance mismatch – in that developers are now getting VM containers rather than application platforms. So instead they are becoming OS and VM experts. And until the developers are as efficient as possible – it will impact the new services the business need.
21. CHAPTER 3: DEVELOPER TOOLS ARE CHANGING. Hello World example
22. Whereas what you want is this. Continuous deployment. If we could get deployment down from 2 months to 3 hours, innovation could happen faster.
23. This was the inspiration behind OpenShift Making developers ridiculous productive whether on a public or private cloud. Moving devel&deploy into a devops model where IT and developers share the same process.
24. Here’s how fast you can deploy things in OpenShift. DEMO: Create an app, create a Jenkins server, deploy it to live. Make a change, deploy it to live again. (Clayton Coleman) This is real. Video note: roughly 120 seconds
25. Over a million apps have been deployed on OpenShift. - 2,000+ apps created each day - serving 500 million hits of traffic Users have validated it.
26. Through OSS; redefining IT. Devs now have a DevOps platform where they can develop quickly and deploy in realtime. The business can now depend on the delivery of new innovation to drive customer engagement. And IT is now the enabler – delivering IaaS and PaaS together as a single platform.