Chef for OpenStack December 2012
6 likes1,386 views
The document discusses Chef, an automation platform for managing infrastructure through code, particularly in the context of deploying OpenStack. It highlights Chef's capabilities for provisioning, configuring, and maintaining applications, as well as the collaborative community around Chef for OpenStack. The presentation also emphasizes the resources, tools, and roadmap for integrating Chef with OpenStack to simplify deployments and enhance infrastructure management.
![knife openstack
$ knife openstack
Available openstack subcommands: (for details, knife SUB-
COMMAND --help)
** OPENSTACK COMMANDS **
knife openstack flavor list (options)
knife openstack image list (options)
knife openstack server create (options)
knife openstack server delete SERVER [SERVER] (options)
knife openstack server list (options)](https://image.slidesharecdn.com/20121206-openstackaustin-121207094213-phpapp01/85/Chef-for-OpenStack-December-2012-17-320.jpg)
Chef for OpenStack December 2012
- 1. Chef for OpenStack Austin OpenStack Meetup December 6, 2012 Matt Ray Senior Technical Evangelist Opscode
- 2. What is Chef? Chef is an automation platform for developers & systems engineers to continuously define, build, and manage infrastructure. CHEF USES: “ Recipes and Cookbooks that describe Infrastructure as Code. Chef enables people to easily build & manage complex & dynamic applications at massive scale ” • New model for describing infrastructure that promotes reuse • Programmatically provision and configure • Reconstruct business from code repository, data backup, and bare metal resources
- 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. How Can Chef Help? Blueprint Your Infrastructure Build Anything… And Manage It Simply • Compute • Provision compute resources in • Introduce continuous incremental the Data Center and the Cloud change or total change. • Application • Storage • Infrastructure • Automatically reconfigure everything • Security • Application Stacks • Re-provision for disaster • Network • Big Data recovery • Configuration Standards • HPC • Fail-over to bare metal • Linux, Windows, OSX, Unixes • Monitor for compliance • Cloud migrations become trivial Using 1,000’s of man-days of prior art! Discoverable and Searchable Infrastructure
- 5. The Chef Community • Apache License, Version 2.0 • 1000+ Individual contributors • 180+ Corporate contributors • Dell, HP, Rackspace, Calxeda, VMware, SUSE, and many more • 700+ cookbooks • Plugins for every cloud • http://community.opscode.com 5
- 6. What's Out There? Chef for OpenStack Resources
- 7. 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
- 8. Chef for OpenStack: What • Chef Repository for Deploying OpenStack • Documentation for Chef for OpenStack • Cookbooks • Keystone • Glance • Nova • Horizon • Swift • Quantum • Cinder • Knife OpenStack
- 9. Chef for OpenStack: Where • groups.google.com/group/opscode-chef- openstack • #openstack-chef on irc.freenode.net • github.com/opscode/openstack-chef-repo • github.com/mattray/openstack-chef-docs • github.com/opscode-cookbooks/ • keystone, glance, nova, horizon, swift,quantum,cinder • github.com/opscode/knife-openstack
- 10. Chef for OpenStack: Who
- 11. Chef for OpenStack: Today • Chef repo for Essex • Operating Systems (Ubuntu 12.04) • Hypervisors (KVM, LXC) • Databases (MySQL) • FlatDHCP networking with floating IPs • Test Kitchen
- 12. Rackspace Private Cloud: Alamo • Parallel fork of current cookbooks • github.com/rcbops/chef-cookbooks • www.rackspace.com/cloud/private/
- 13. Chef for OpenStack: When • Folsom is under active development • Rackspace, AT&T, DreamHost have active branches • Quantum (Nicira, OVS) • Cinder • Hyper-V • Red Hat
- 14. Chef for OpenStack: How github.com/mattray/openstack-chef-docs moving to github.com/opscode/chef-docs
- 15. 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
- 16. knife openstack
- 17. knife openstack $ knife openstack Available openstack subcommands: (for details, knife SUB- COMMAND --help) ** OPENSTACK COMMANDS ** knife openstack flavor list (options) knife openstack image list (options) knife openstack server create (options) knife openstack server delete SERVER [SERVER] (options) knife openstack server list (options)
- 18. knife openstack flavor list $ knife openstack flavor list ID Name Virtual CPUs RAM Disk 1 m1.tiny 1 512 MB 0 GB 2 m1.small 1 2048 MB 10 GB 3 m1.medium 2 4096 MB 10 GB 4 m1.large 4 8192 MB 10 GB 5 m1.xlarge 8 16384 MB 10 GB
- 19. knife openstack image list $ knife openstack image list ID Name 4a197431-503d-4b85-b61e-84af21ca8654 cirros-image f8ebb842-c0c0-4be3-8c4c-f72f48edec50 precise-image
- 20. knife openstack server create knife openstack server create -a -f 1 -I f8ebb842-c0c0-4be3-8c4c-f72f48edec50 -S local -i ~/.ssh/local.pem -x ubuntu
- 23. Chef for Infrastructure Portability • knife openstack • Piston, Nebula, Crowbar, TryStack • knife hp • knife rackspace • knife ec2 • ... and many others
- 24. Chef for OpenStack Roadmap • Documentation (docs.opscode.com) • Hypervisors (Hyper-V) • Databases (PostgreSQL) • Operating Systems (RHEL, Debian, SUSE) • HA Configurations • Quantum (pluggable) • Cinder (pluggable) • Community Events (Boston January 22)
- 25. Chef for OpenStack Ecosystem • Cookbooks reusable outside of OpenStack • Test Kitchen • Librarian • Spiceweasel • pxe_dust • knife-rackspace/hp/dreamhost • Sputnik Cloud Launcher • Crowbar
- 26. Chef for OpenStack TL;DL • Opscode.com/openstack • Project, not a product • Lots of contributors with real deployments • Essex works, Folsom merging • Features driven by demand (show up for what you want) • Documentation with examples
- 27. AT&T