Chef For OpenStack Overview


Published on

Published in: Technology, Self Improvement
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Chef For OpenStack Overview

  1. 1. Chef for OpenStack OverviewOpenStack Summit April 2013Matt RayOpscode
  2. 2. Why Chef?
  3. 3. Chef is Infrastructure as Code • Programmatically provision and configure • Treat like any other code base • Reconstruct business from code repository, data backup, and bare metal resources.
  4. 4. Declarative Interface to Resources• Define policy• Say what, not how• Pull not Push
  5. 5. Ruby!extra_packages = case node[platform] when "ubuntu","debian" %w{ ruby1.8 ruby1.8-dev rdoc1.8 ri1.8 libopenssl-ruby } endextra_packages.each do |pkg| package pkg do action :install endend
  6. 6. Recipes and Cookbooks• Recipes are collections of Resources• Cookbooks contain recipes, templates, files, custom resources, etc• Code re-use and modularity• Hundreds already on
  7. 7. The Chef Community• Apache License, Version 2.0• 1300+ Individual contributors• 200+ Corporate contributors • Dell, DreamHost, HP, Rackspace, VMware, SUSE and many more• 900+ cookbooks•
  8. 8. Chef and OpenStack?Thats great and all, but tell me about OpenStack!
  9. 9. Deploying OpenStack• Chef ties it all together automatically• Scaling changes how we deploy• Interchangeable components• Configurations shared, supported & documented• Licensing makes it available to everyone
  10. 10. Overview & Status ofChef for OpenStack
  11. 11. Chef for OpenStack: Who• Arista • Mercado Libre• AT&T • Mirantis• Baremetal Cloud • NTT• Calxeda • Nebula• Dell • Nicira• DreamHost • Piston Cloud• HP • Rackspace• HubSpot • SUSE• IBM •• Intel • Voxel• Internap • ...and more
  12. 12. Chef for OpenStack: Why• Community for the automated deployment and management of OpenStack• Reduce fragmentation and encourage collaboration• Deploying OpenStack is not "secret sauce"• Project not a product• Apache 2 license
  13. 13. Chef for OpenStack: What• Chef Repository for Deploying OpenStack• Documentation for Chef for OpenStack• Cookbooks • Keystone • Glance • Nova • Horizon • Swift • Quantum • Cinder• knife-openstack
  14. 14. Chef for OpenStack: Where• #openstack-chef on•• • keystone, glance, nova, horizon, swift,quantum,cinder••• openstack• @chefopenstack
  15. 15. Chef for OpenStack: When (Today)• Chef repo for Essex/Grizzly• Operating Systems (Ubuntu 12.04)• Hypervisors (KVM, LXC)• Databases (MySQL)• Nova network FlatDHCP HA & VLAN• Quantum Nicira plugin available• Test Kitchen integration
  16. 16. Chef for OpenStack: When (Tomorrow)• Grizzly sprint scheduled in 2 weeks• Merging AT&T, DreamHost, HubSpot and Rackspace code• Documentation (
  17. 17. Chef for OpenStack: When (Roadmap)• Build packages from source• Continuous integration• Hypervisors (Hyper-V, bare metal)• Databases (PostgreSQL)• Cinder (Ceph)• Quantum (Midokura)• Operating Systems (RHEL, Debian, SUSE)• Documentation (• HA Configurations
  18. 18. Chef for OpenStack Resources Ecosystem
  19. 19. AT&T•• primary Folsom merge source• openstack-common• cinder (lvm, netapp, rbd)• lots of support cookbooks
  20. 20. Crowbar• Hardware provisioning and application management platform•• Dell, SUSE, others• likely Swift cookbook source combined with Rackspaces
  21. 21. DreamHost•• ceph• ceilometer• quantum
  22. 22. Nicira• Nicira NVP cookbook• Open vSwitch cookbook• Development in progress by Opscode•
  23. 23. Rackspace Private Cloud••• primary Essex merge source• likely Red Hat source
  24. 24. Chef for OpenStack "Halo Effect"• Cookbooks reusable outside of OpenStack• Test Kitchen• knife-rackspace/hp• Crowbar, pxe_dust & Razor• Arista EOS cookbook• Berkshelf & Librarian• Spiceweasel & Sputnik
  25. 25. knife openstack
  26. 26. knife openstack$ knife openstackAvailable openstack subcommands: (for details, knife SUB-COMMAND --help)** OPENSTACK COMMANDS **knife openstack flavor list (options)knife openstack group list (options)knife openstack image list (options)knife openstack server create (options)knife openstack server delete SERVER [SERVER] (options)knife openstack server list (options)
  27. 27. knife openstack flavor list$ knife openstack flavor listID Name Virtual CPUs RAM Disk1 m1.tiny 1 512 MB 0 GB2 m1.small 1 2048 MB 10 GB3 m1.medium 2 4096 MB 10 GB4 m1.large 4 8192 MB 10 GB5 m1.xlarge 8 16384 MB 10 GB
  28. 28. knife openstack image list$ knife openstack image listID Name4a197431-503d-4b85-b61e-84af21ca8654 cirros-imagef8ebb842-c0c0-4be3-8c4c-f72f48edec50 precise-image
  29. 29. knife openstack server createknife openstack server create -a -f 1 -I f8ebb842-c0c0-4be3-8c4c-f72f48edec50 -S local -i ~/.ssh/local.pem -x ubuntu
  30. 30. knife-openstack compatibility• Uses the OpenStack API• Diablo, Essex, Folsom, Grizzly• Cloudscaling• Crowbar• DreamHost• Nebula• Piston• Rackspace Private Cloud
  31. 31. knife-openstack Roadmap••• floating IP address management• quantum network management
  32. 32. Why the Cloud?Why OpenStack?
  33. 33. Why the Cloud?• Instant infrastructure• Unlimited capacity• Autoscaling• No commitment• Immediate replacement
  34. 34. Why OpenStack?• Real Open Source• Anyone can play• Choice of features• Features achieving parity/ accelerating ahead
  35. 35. Know our escape planfor every infrastructure provider
  36. 36. Chef for Infrastructure Portability• knife ec2 • knife cloudstack• knife rackspace • knife openstack• knife hp • knife vcloud• knife google • ... and many• knife azure others
  37. 37. Desktop, Virtualization, Private & Public Clouds• Vagrant • AWS• VMware • Rackspace• CloudStack • HP• Eucalyptus • Google• OpenStack • Azure• bare metal • many others
  38. 38. Desktop, Virtualization, Private & Public Clouds• Vagrant • AWS• VMware • Rackspace• CloudStack • HP• Eucalyptus • Google• OpenStack • Azure• bare metal • many others
  39. 39. The Path to Full Automation Full Continuous Infrastructure Application Deployment Automation Configuration Common ManagementDiscovery and Management Automation Tasks: Visibility Scripts, OS Compliance, Updates & Patches
  40. 40. Continuous Deployment Workflow Continuous Deployment Workflow• Clear, documented workflows for different team members - sysadmins, devs, QA & business stakeholders
  41. 41. Continuous Deployment Toolchain gerrit!• A single, ubiquitous process for building and managing the entire technology platform• Standardized tooling• Jenkins and Chef working together• OpenStack for your private and public clouds
  42. 42. Chef for OpenStack TL;DL• Project, not a product• Lots of contributors with real deployments in a vibrant ecosystem• Essex works, Grizzly soon• Features driven by demand• Documentation with examples• Do real work with OpenStack
  43. 43. Questions?Matt Raymatt@opscode.comTwitter|GitHub|IRC: mattray