0
Chef for OpenStack OverviewOpenStack Summit April 2013Matt RayOpscode
Why Chef?
Chef is Infrastructure as Codehttp://www.flickr.com/photos/louisb/4555295187/• Programmaticallyprovision and configure• Tre...
Declarative Interface to Resources• Define policy• Say what, not how• Pull not Pushhttp://www.flickr.com/photos/bixentro/25...
Ruby!extra_packages = case node[platform]when "ubuntu","debian"%w{ruby1.8ruby1.8-devrdoc1.8ri1.8libopenssl-ruby}endextra_p...
Recipes and Cookbooks• Recipes are collections ofResources• Cookbooks containrecipes, templates, files,custom resources, e...
The Chef Community• Apache License,Version 2.0• 1300+ Individual contributors• 200+ Corporate contributors• Dell, DreamHos...
http://www.flickr.com/photos/16339684@N00/2681435235/Chef and OpenStack?Thats great and all,but tell me aboutOpenStack!
Deploying OpenStack• Chef ties it all together automatically• Scaling changes how we deploy• Interchangeable components• C...
Overview & Status ofChef for OpenStack
Chef for OpenStack:Who• Arista• AT&T• Baremetal Cloud• Calxeda• Dell• DreamHost• HP• HubSpot• IBM• Intel• Internap• Mercad...
Chef for OpenStack:Why• Community for the automated deploymentand management of OpenStack• Reduce fragmentation and encour...
Chef for OpenStack:What• Chef Repository for Deploying OpenStack• Documentation for Chef for OpenStack• Cookbooks• Keyston...
Chef for OpenStack:Where• #openstack-chef on irc.freenode.net• github.com/opscode/openstack-chef-repo• github.com/opscode-...
• Chef repo for Essex/Grizzly• Operating Systems (Ubuntu 12.04)• Hypervisors (KVM, LXC)• Databases (MySQL)• Nova network F...
Chef for OpenStack:When (Tomorrow)• Grizzly sprint scheduled in 2weeks• Merging AT&T, DreamHost,HubSpot and Rackspace code...
• Build packages from source• Continuous integration• Hypervisors (Hyper-V, bare metal)• Databases (PostgreSQL)• Cinder (C...
ResourcesChef for OpenStackEcosystem
AT&T• github.com/att-cloud/• primary Folsom merge source• openstack-common• cinder (lvm, netapp, rbd)• lots of support coo...
Crowbar• Hardware provisioning and applicationmanagement platform• crowbar.github.com• Dell, SUSE, others• likely Swift co...
DreamHost• github.com/dreamhost• ceph• ceilometer• quantum
• Nicira NVP cookbook• Open vSwitch cookbook• Development in progress by Opscode• github.com/gmiranda23/nvp-cookbookNicira
Rackspace Private Cloud• www.rackspace.com/cloud/private/• github.com/rcbops/chef-cookbooks• primary Essex merge source• l...
• Cookbooks reusable outside ofOpenStack• Test Kitchen• knife-rackspace/hp• Crowbar, pxe_dust & Razor• Arista EOS cookbook...
knife openstack
knife openstack$ knife openstackAvailable openstack subcommands: (for details, knife SUB-COMMAND --help)** OPENSTACK COMMA...
knife openstack flavor list$ knife openstack flavor listID Name Virtual CPUs RAM Disk1 m1.tiny 1 512 MB 0 GB2 m1.small 1 2...
knife openstack image list$ knife openstack image listID Name4a197431-503d-4b85-b61e-84af21ca8654 cirros-imagef8ebb842-c0c...
knife openstack server create -a -f 1 -I f8ebb842-c0c0-4be3-8c4c-f72f48edec50-S local -i ~/.ssh/local.pem -x ubuntuknife o...
knife-openstack compatibility• Uses the OpenStack API• Diablo, Essex, Folsom, Grizzly• Cloudscaling• Crowbar• DreamHost• N...
knife-openstack Roadmap• docs.opscode.com/plugin_knife_openstack.html• tickets.opscode.com/browse/KNIFE/component/• floati...
Why the Cloud?Why OpenStack?
• Instant infrastructure• Unlimited capacity• Autoscaling• No commitment• Immediate replacementWhy the Cloud?
• Real Open Source• Anyone can play• Choice of features• Features achieving parity/accelerating aheadWhy OpenStack?
Know our escape planfor every infrastructureprovider
Chef for Infrastructure Portability• knife ec2• knife rackspace• knife hp• knife google• knife azure• knife cloudstack• kn...
• Vagrant• VMware• CloudStack• Eucalyptus• OpenStack• bare metal• AWS• Rackspace• HP• Google• Azure• many othersDesktop,Vi...
• Vagrant• VMware• CloudStack• Eucalyptus• OpenStack• bare metalDesktop,Virtualization, Private & Public Clouds• AWS• Rack...
The Path to Full AutomationFullInfrastructureAutomationCommonAutomation Tasks:Scripts, OSCompliance,Updates &PatchesConfig...
Continuous DeploymentWorkflowContinuous Deployment Workflow• Clear, documented workflows for different team members - sysa...
gerrit!Continuous Deployment Toolchain• A single, ubiquitous process for building and managing the entiretechnology platfo...
Chef for OpenStack TL;DL• Project, not a product• Lots of contributors with realdeployments in a vibrantecosystem• Essex w...
Questions?Matt Raymatt@opscode.comTwitter|GitHub|IRC: mattray
Chef for OpenStack: OpenStack Spring Summit 2013
Chef for OpenStack: OpenStack Spring Summit 2013
Upcoming SlideShare
Loading in...5
×

Chef for OpenStack: OpenStack Spring Summit 2013

1,360

Published on

Overview of current Chef for OpenStack ecosystem at the OpenStack Spring Summit 2013.

Published in: Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,360
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
79
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Transcript of "Chef for OpenStack: OpenStack Spring Summit 2013"

  1. 1. Chef for OpenStack OverviewOpenStack Summit April 2013Matt RayOpscode
  2. 2. Why Chef?
  3. 3. Chef is Infrastructure as Codehttp://www.flickr.com/photos/louisb/4555295187/• Programmaticallyprovision and configure• Treat like any other codebase• Reconstruct business fromcode repository, databackup, and bare metalresources.
  4. 4. Declarative Interface to Resources• Define policy• Say what, not how• Pull not Pushhttp://www.flickr.com/photos/bixentro/2591838509/
  5. 5. Ruby!extra_packages = case node[platform]when "ubuntu","debian"%w{ruby1.8ruby1.8-devrdoc1.8ri1.8libopenssl-ruby}endextra_packages.each do |pkg|package pkg doaction :installendend
  6. 6. Recipes and Cookbooks• Recipes are collections ofResources• Cookbooks containrecipes, templates, files,custom resources, etc• Code re-use andmodularity• Hundreds already onCommunity.opscode.comhttp://www.flickr.com/photos/shutterhacks/4474421855/
  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• http://community.opscode.com
  8. 8. http://www.flickr.com/photos/16339684@N00/2681435235/Chef and OpenStack?Thats great and all,but tell me aboutOpenStack!
  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• AT&T• Baremetal Cloud• Calxeda• Dell• DreamHost• HP• HubSpot• IBM• Intel• Internap• Mercado Libre• Mirantis• NTT• Nebula• Nicira• Piston Cloud• Rackspace• SUSE• TryStack.org• Voxel• ...and more
  12. 12. Chef for OpenStack:Why• Community for the automated deploymentand management of OpenStack• Reduce fragmentation and encouragecollaboration• 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 irc.freenode.net• github.com/opscode/openstack-chef-repo• github.com/opscode-cookbooks/• keystone, glance, nova, horizon,swift,quantum,cinder• github.com/opscode/knife-openstack• github.com/mattray/openstack-chef-docs• groups.google.com/group/opscode-chef-openstack• @chefopenstack
  15. 15. • 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 integrationChef for OpenStack:When (Today)
  16. 16. Chef for OpenStack:When (Tomorrow)• Grizzly sprint scheduled in 2weeks• Merging AT&T, DreamHost,HubSpot and Rackspace code• Documentation(docs.opscode.com)
  17. 17. • Build packages from source• Continuous integration• Hypervisors (Hyper-V, bare metal)• Databases (PostgreSQL)• Cinder (Ceph)• Quantum (Midokura)• Operating Systems (RHEL, Debian, SUSE)• Documentation (docs.opscode.com)• HA ConfigurationsChef for OpenStack:When (Roadmap)
  18. 18. ResourcesChef for OpenStackEcosystem
  19. 19. AT&T• github.com/att-cloud/• primary Folsom merge source• openstack-common• cinder (lvm, netapp, rbd)• lots of support cookbooks
  20. 20. Crowbar• Hardware provisioning and applicationmanagement platform• crowbar.github.com• Dell, SUSE, others• likely Swift cookbook source combinedwith Rackspaces
  21. 21. DreamHost• github.com/dreamhost• ceph• ceilometer• quantum
  22. 22. • Nicira NVP cookbook• Open vSwitch cookbook• Development in progress by Opscode• github.com/gmiranda23/nvp-cookbookNicira
  23. 23. Rackspace Private Cloud• www.rackspace.com/cloud/private/• github.com/rcbops/chef-cookbooks• primary Essex merge source• likely Red Hat source
  24. 24. • Cookbooks reusable outside ofOpenStack• Test Kitchen• knife-rackspace/hp• Crowbar, pxe_dust & Razor• Arista EOS cookbook• Berkshelf & Librarian• Spiceweasel & SputnikChef for OpenStack "Halo Effect"
  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 create -a -f 1 -I f8ebb842-c0c0-4be3-8c4c-f72f48edec50-S local -i ~/.ssh/local.pem -x ubuntuknife openstack server create
  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• docs.opscode.com/plugin_knife_openstack.html• tickets.opscode.com/browse/KNIFE/component/• floating IP address management• quantum network management
  32. 32. Why the Cloud?Why OpenStack?
  33. 33. • Instant infrastructure• Unlimited capacity• Autoscaling• No commitment• Immediate replacementWhy the Cloud?
  34. 34. • Real Open Source• Anyone can play• Choice of features• Features achieving parity/accelerating aheadWhy OpenStack?
  35. 35. Know our escape planfor every infrastructureprovider
  36. 36. Chef for Infrastructure Portability• knife ec2• knife rackspace• knife hp• knife google• knife azure• knife cloudstack• knife openstack• knife vcloud• ... and manyothers
  37. 37. • Vagrant• VMware• CloudStack• Eucalyptus• OpenStack• bare metal• AWS• Rackspace• HP• Google• Azure• many othersDesktop,Virtualization, Private & Public Clouds
  38. 38. • Vagrant• VMware• CloudStack• Eucalyptus• OpenStack• bare metalDesktop,Virtualization, Private & Public Clouds• AWS• Rackspace• HP• Google• Azure• many others
  39. 39. The Path to Full AutomationFullInfrastructureAutomationCommonAutomation Tasks:Scripts, OSCompliance,Updates &PatchesConfigurationManagementDiscovery andVisibilityApplicationManagementContinuousDeployment
  40. 40. Continuous DeploymentWorkflowContinuous Deployment Workflow• Clear, documented workflows for different team members - sysadmins,devs, QA & business stakeholders
  41. 41. gerrit!Continuous Deployment Toolchain• A single, ubiquitous process for building and managing the entiretechnology 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 realdeployments in a vibrantecosystem• 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
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×