SCALE 2011 Deploying OpenStack with Chef
10 likes2,152 views
The document discusses the automated deployment of OpenStack using Chef, highlighting OpenStack's mission to create a scalable open-source cloud platform and its core principles of modularity and community engagement. It details the configuration management capabilities of Chef, including recipes and roles used for managing resources on server nodes and the process of deploying OpenStack in various environments. Additionally, the document mentions the importance of community contributions and ongoing development efforts to enhance OpenStack features and deployment scenarios.
![name "webserver"
description "Systems that serve HTTP traffic"
run_list(
"role[base]",
Can include
"recipe[apache2]", other roles!
"recipe[apache2::mod_ssl]"
)
default_attributes(
"apache" => {
"listen_ports" => [ "80", "443" ]
}
)
override_attributes(
"apache" => {
"max_children" => "50"
}
)
33](https://image.slidesharecdn.com/scale2011-openstack-110227004707-phpapp01/85/SCALE-2011-Deploying-OpenStack-with-Chef-33-320.jpg)
![Recipes are just Ruby!
extra_packages = case node[:platform]
when "ubuntu","debian"
%w{
ruby1.8
ruby1.8-dev
rdoc1.8
ri1.8
libopenssl-ruby
}
end
extra_packages.each do |pkg|
package pkg do
action :install
end
end](https://image.slidesharecdn.com/scale2011-openstack-110227004707-phpapp01/85/SCALE-2011-Deploying-OpenStack-with-Chef-40-320.jpg)
![Role: nova-single-machine-install
name "nova-single-machine-install"
description "Installs everything required to run Nova on a single
machine"
run_list(
"recipe[apt]",
"recipe[nova::mysql]",
"recipe[nova::openldap]",
"recipe[nova::rabbit]",
"recipe[nova::common]",
"recipe[nova::api]",
"recipe[nova::scheduler]",
"recipe[nova::network]",
"recipe[nova::objectstore]",
"recipe[nova::compute]",
"recipe[nova::setup]",
"recipe[nova::creds]",
"recipe[nova::finalize]"
)](https://image.slidesharecdn.com/scale2011-openstack-110227004707-phpapp01/85/SCALE-2011-Deploying-OpenStack-with-Chef-53-320.jpg)
![Role: nova-multi-controller
name "nova-multi-controller"
description "Installs requirements to run the Controller node in a
Nova cluster"
run_list(
"recipe[apt]",
"recipe[nova::mysql]",
"recipe[nova::openldap]",
"recipe[nova::rabbit]",
"recipe[nova::common]",
"recipe[nova::api]",
"recipe[nova::objectstore]",
"recipe[nova::compute]",
"recipe[nova::setup]",
"recipe[nova::creds]",
"recipe[nova::finalize]"
)](https://image.slidesharecdn.com/scale2011-openstack-110227004707-phpapp01/85/SCALE-2011-Deploying-OpenStack-with-Chef-54-320.jpg)
![Role: nova-multi-compute
name "nova-multi-compute"
description "Installs requirements to run a Compute node in a Nova
cluster"
run_list(
"recipe[apt]",
"recipe[nova::network]",
"recipe[nova::compute]",
)](https://image.slidesharecdn.com/scale2011-openstack-110227004707-phpapp01/85/SCALE-2011-Deploying-OpenStack-with-Chef-55-320.jpg)
![AMIs
name "nova-ami-urls"
description "Feed in a list URLs for AMIs to download"
default_attributes(
"nova" => {
"images" =>
["http://192.168.11.7/ubuntu1010-UEC-localuser-image.tar.gz”]
}
)
$ knife role from file roles/nova-ami-urls.rb
‣ Use an existing AMI
‣ Update URL to your own](https://image.slidesharecdn.com/scale2011-openstack-110227004707-phpapp01/85/SCALE-2011-Deploying-OpenStack-with-Chef-58-320.jpg)
![Assign the Roles
$ knife node run_list add crushinator.localdomain "role[nova-ami-
urls]"
{
"run_list": [
"role[nova-ami-urls]"
]
}
$ knife node run_list add crushinator.localdomain "role[nova-single-
machine-install]"
{
"run_list": [
"role[nova-ami-urls]"
"role[nova-single-machine-install]",
]
}](https://image.slidesharecdn.com/scale2011-openstack-110227004707-phpapp01/85/SCALE-2011-Deploying-OpenStack-with-Chef-59-320.jpg)
![chef-client
mray@ubuntu1010:~$ sudo chef-client
[Fri, 25 Feb 2011 11:52:59 -0800] INFO: Starting Chef Run (Version
0.9.12)
...
[Fri, 25 Feb 2011 11:56:05 -0800] INFO: Chef Run complete in
5.911955 seconds
[Fri, 25 Feb 2011 11:56:05 -0800] INFO: cleaning the checksum cache
[Fri, 25 Feb 2011 11:56:05 -0800] INFO: Running report handlers
[Fri, 25 Feb 2011 11:56:05 -0800] INFO: Report handlers complete](https://image.slidesharecdn.com/scale2011-openstack-110227004707-phpapp01/85/SCALE-2011-Deploying-OpenStack-with-Chef-60-320.jpg)
![Knife
‣ Nova has same API as Amazon
‣ knife ec2 server create ‘role[base]’ -I ~/.ssh/my.pem -x
ubuntu -G default -i ami-a403f6xd -f m1.micro
‣ Fog reportedly supports OpenStack already
‣ Simply need to pass URL of nova-api server and
credentials
‣ http://tickets.opscode.com/browse/CHEF-1757
‣ knife openstack server create ‘role[base]’ -I ~/.ssh/my.pem
-x ubuntu -G default -i ami-a403f6xd -f m1.micro](https://image.slidesharecdn.com/scale2011-openstack-110227004707-phpapp01/85/SCALE-2011-Deploying-OpenStack-with-Chef-70-320.jpg)
SCALE 2011 Deploying OpenStack with Chef
- 1. Automated Deployment of OpenStack with Chef SCALE 9x February 25-27, 2011
- 2. Introductions Matt Ray Senior Technical Evangelist [email protected] @mattray GitHub:mattray
- 4. Founders operate at massive scale NASA
- 5. OpenStack: The Mission "To produce the ubiquitous Open Source cloud computing platform that will meet the needs of public and private cloud providers regardless of size, by being simple to implement and massively scalable."
- 6. OpenStack Founding Principles Apache 2.0 license (OSI), open development process Open design process, 2x year public Design Summits Publicly available open source code repositories Open community processes documented and transparent Commitment to drive and adopt open standards Modular design for deployment flexibility via APIs
- 7. Community with Broad Support
- 8. Software to provision virtual machines on standard hardware at massive scale OpenStack Compute creating open source software to build public and private clouds Software to reliably store billions of objects distributed across standard hardware OpenStack Object Storage
- 9. OpenStack Compute Key Features ReST-based API Asynchronous eventually consistent communication Horizontally and massively scalable Hypervisor agnostic: support for Xen ,XenServer, Hyper-V, KVM, UML and ESX is coming Hardware agnostic: standard hardware, RAID not required
- 10. User Manager Cloud Controller: Global state of system, talks to LDAP, OpenStack Object Storage, and node/storage workers through a queue ATAoE / iSCSI API: Receives HTTP requests, converts commands to/from API format, and sends requests to cloud controller Host Machines: workers that spawn instances Glance: HTTP + OpenStack Object OpenStack Compute Storage for server images
- 11. Hardware Requirements OpenStack is designed to run on industry standard hardware, with flexible configurations Compute x86 Server (Hardware Virt. recommended) Storage flexible (Local, SAN, NAS) Object Storage x86 Server (other architectures possible) Do not deploy with RAID (can use controller for cache)
- 12. Why is OpenStack important? Open eliminates vendor lock-in Working together, we all go faster Freedom to federate, or move between clouds
- 13. What is Chef?
- 14. Chef enables Infrastructure as Code Manage configuration as idempotent Resources. Put them together in Recipes. Track it like Source Code. Configure your servers.
- 15. At a High Level A library for configuration management A configuration management system A systems integration platform An API for your entire Infrastructure
- 17. Principles Idempotent Data-driven Sane defaults Hackability TMTOWTDI
- 18. Open Source and Community Apache licensed Large and active community Over 280 individual contributors (60+ corporate) Community is Important!
- 20. How does it Work?
- 21. How does it Work? Magic!
- 22. How does it Work? Magic! (no really)
- 23. Chef Client runs on your System
- 24. Chef Client runs on your System ohai!
- 25. Clients talk to the Chef Server
- 26. The Opscode Platform is a hosted Chef Server
- 27. We call each system you configure a Node
- 28. Nodes have Attributes { "kernel": { "machine": "x86_64", "name": "Darwin", Kernel info! "os": "Darwin", "version": "Darwin Kernel Version 10.4.0: Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386", }, "release": "10.4.0" Platform info! "platform_version": "10.6.4", "platform": "mac_os_x", "platform_build": "10F569", "domain": "local", "os": "darwin", "current_user": "mray", "ohai_time": 1278602661.60043, "os_version": "10.4.0", Hostname and IP! "uptime": "18 days 17 hours 49 minutes 18 seconds", "ipaddress": "10.13.37.116", "hostname": "morbo", "fqdn": "morbomorbo.local", "uptime_seconds": 1619358 }
- 29. Nodes have a Run List What Roles and Recipes to Apply in Order
- 30. Nodes have Roles
- 31. Nodes have Roles webserver, database, monitoring, etc.
- 32. Roles have a Run List What Roles and Recipes to Apply in Order
- 33. name "webserver" description "Systems that serve HTTP traffic" run_list( "role[base]", Can include "recipe[apache2]", other roles! "recipe[apache2::mod_ssl]" ) default_attributes( "apache" => { "listen_ports" => [ "80", "443" ] } ) override_attributes( "apache" => { "max_children" => "50" } ) 33
- 34. Chef manages Resources on Nodes
- 35. Resources ‣ Have a type package "apache2" do version "2.2.11-2ubuntu2.6" action :install ‣ Have a name end template "/etc/apache2/apache2.conf" do ‣ Have parameters source "apache2.conf.erb" owner "root" ‣ Take action to put the group "root" mode 0644 resource in the action :create declared state end Declare a description of the state a part of the node should be in
- 36. Resources take action through Providers
- 37. Recipes are lists of Resources
- 38. Recipes 1 package "apache2" do version "2.2.11-2ubuntu2.6" action :install end Evaluate and apply template "/etc/apache2/apache2.conf" do Resources in the order source "apache2.conf.erb" owner "root" they appear group "root" mode 0644 action :create2 end
- 39. Order Matters
- 40. Recipes are just Ruby! extra_packages = case node[:platform] when "ubuntu","debian" %w{ ruby1.8 ruby1.8-dev rdoc1.8 ri1.8 libopenssl-ruby } end extra_packages.each do |pkg| package pkg do action :install end end
- 41. Cookbooks are packages for Recipes
- 42. Cookbooks Distributable cookbooks.opscode.com Infrastructure as Code Versioned
- 43. Cookbooks Recipes Files Templates Attributes Metadata
- 44. Data bags store arbitrary data
- 45. A user data bag item... % knife data bag show users mray { "comment": "Matt Ray", "groups": "sysadmin", "ssh_keys": "ssh-rsa SUPERSEKRATS mray@morbo", "files": { ".bashrc": { "mode": "0644", "source": "dot-bashrc" }, ".emacs": { "mode": "0644", "source": "dot-emacs" } }, "id": "mray", "uid": 7004, "shell": "/usr/bin/bash" }
- 47. Command-line API utility, Knife http://www.flickr.com/photos/myklroventine/3474391066/ Copyright © 2011 Opscode, Inc - All Rights Reserved 47
- 48. Search $ knife search node 'platform:ubuntu' ‣ CLI or in Ruby search(:node, ‘platform:centos’) ‣ Nodes are searchable $ knife search role 'max_children:50' ‣ Roles are searchable search(:role, ‘max_children:50’) ‣ Recipes are $ knife search node ‘role:webserver’ searchable search(:node, ‘role:webserver’) ‣ Data bags are $ knife users ‘shell:/bin/bash’ searchable search (:users, ‘group:sysadmins’)
- 50. HOW TO: Turn Racks of Standard Hardware Into a Cloud with OpenStack
- 52. Compute (Nova) Single machine installation ‣ MySQL, RabbitMQ, OpenLDAP ‣ Nova-(api|scheduler|network|objectstore|compute) ‣ Role: nova-single-machine-install Multi-machine ‣ Role: nova-multi-controller (1) ‣ Role: nova-multi-compute (N)
- 53. Role: nova-single-machine-install name "nova-single-machine-install" description "Installs everything required to run Nova on a single machine" run_list( "recipe[apt]", "recipe[nova::mysql]", "recipe[nova::openldap]", "recipe[nova::rabbit]", "recipe[nova::common]", "recipe[nova::api]", "recipe[nova::scheduler]", "recipe[nova::network]", "recipe[nova::objectstore]", "recipe[nova::compute]", "recipe[nova::setup]", "recipe[nova::creds]", "recipe[nova::finalize]" )
- 54. Role: nova-multi-controller name "nova-multi-controller" description "Installs requirements to run the Controller node in a Nova cluster" run_list( "recipe[apt]", "recipe[nova::mysql]", "recipe[nova::openldap]", "recipe[nova::rabbit]", "recipe[nova::common]", "recipe[nova::api]", "recipe[nova::objectstore]", "recipe[nova::compute]", "recipe[nova::setup]", "recipe[nova::creds]", "recipe[nova::finalize]" )
- 55. Role: nova-multi-compute name "nova-multi-compute" description "Installs requirements to run a Compute node in a Nova cluster" run_list( "recipe[apt]", "recipe[nova::network]", "recipe[nova::compute]", )
- 56. Starting with a provisioned server ‣ Ubuntu 10.10 (preseed) ‣ openssh-server ‣ virtual-machine-host knife bootstrap crushinator.localdomain ~/.ssh/id_rsa -x mray --sudo -d ubuntu10.04-gems
- 57. Installation ‣ Cookbooks uploaded $ $ knife cookbook upload -a knife cookbook list $ rake roles ‣ Roles uploaded $ knife role list $ knife node list ‣ Nodes ready
- 58. AMIs name "nova-ami-urls" description "Feed in a list URLs for AMIs to download" default_attributes( "nova" => { "images" => ["http://192.168.11.7/ubuntu1010-UEC-localuser-image.tar.gz”] } ) $ knife role from file roles/nova-ami-urls.rb ‣ Use an existing AMI ‣ Update URL to your own
- 59. Assign the Roles $ knife node run_list add crushinator.localdomain "role[nova-ami- urls]" { "run_list": [ "role[nova-ami-urls]" ] } $ knife node run_list add crushinator.localdomain "role[nova-single- machine-install]" { "run_list": [ "role[nova-ami-urls]" "role[nova-single-machine-install]", ] }
- 60. chef-client mray@ubuntu1010:~$ sudo chef-client [Fri, 25 Feb 2011 11:52:59 -0800] INFO: Starting Chef Run (Version 0.9.12) ... [Fri, 25 Feb 2011 11:56:05 -0800] INFO: Chef Run complete in 5.911955 seconds [Fri, 25 Feb 2011 11:56:05 -0800] INFO: cleaning the checksum cache [Fri, 25 Feb 2011 11:56:05 -0800] INFO: Running report handlers [Fri, 25 Feb 2011 11:56:05 -0800] INFO: Report handlers complete
- 61. sudo su - nova nova@$ nova-manage service list h00-26-6c-f4-1e-a0 nova-scheduler enabled :-) 2011-02-25 18:30:45 h00-26-6c-f4-1e-a0 nova-network enabled :-) 2011-02-25 18:30:48 h00-26-6c-f4-1e-a0 nova-compute enabled :-) 2011-02-25 18:30:50 nova@$ euca-describe-images IMAGE! ami-90hgmwai!nova_amis/maverick-server-uec-amd64-vmlinuz- virtual.manifest.xml! admin! available! private i386!kernel! true! IMAGE! ami-h8wh0j17!nova_amis/maverick-server-uec- amd64.img.manifest.xml!admin! untarring!private i386!machine ! ami-90hgmwai! nova@$ euca-run-instances ami-h8wh0j17 -k mykey -t m1.tiny RESERVATION! r-uur39109! admin! default INSTANCE! i-00000001! ami-h8wh0j17!! ! scheduling! mykey (admin, None)! 0! ! m1.tiny! 2011-02-25 18:34:01! nknown zone!! u
- 62. sudo su - nova (page 2) nova@$ euca-describe-instances RESERVATION! r-uur39109! admin! default INSTANCE! i-00000001! ami-h8wh0j17!10.0.0.2! 10.0.0.2! running ! mykey (admin, h00-26-6c-f4-1e-a0)! 0! ! m1.tiny! 2011-02-25 18:34:01! nova! nova@$ ssh -i mykey.priv [email protected] The authenticity of host '10.0.0.2 (10.0.0.2)' can't be established. RSA key fingerprint is 91:21:ef:5d:33:17:24:cb:f6:65:dd:27:1d:1c: 50:ad. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '10.0.0.2' (RSA) to the list of known hosts.
- 63. The Moment of Truth Linux i-00000001 2.6.35-24-virtual #42-Ubuntu SMP Thu Dec 2 05:15:26 UTC 2010 x86_64 GNU/Linux Ubuntu 10.10 Welcome to Ubuntu! <SNIP> See "man sudo_root" for details. ubuntu@i-00000001:~$
- 64. How Did We Get Here?
- 65. Forked from Anso Labs’ Cookbooks Bootstrapped by Opscode Chef Solo/Vagrant installs for Developers http://github.com/ansolabs/openstack-cookbooks
- 67. What’s Next?
- 68. Nova needed enhancements Happy Path-only! KVM-only MySQL-only Flat DHCP network-only Swift and Glance integration More Roles
- 69. Dashboard Graphical interface for managing instantiation of AMIs Django application dashboard.rb recipe already exists in nova cookbook
- 70. Knife ‣ Nova has same API as Amazon ‣ knife ec2 server create ‘role[base]’ -I ~/.ssh/my.pem -x ubuntu -G default -i ami-a403f6xd -f m1.micro ‣ Fog reportedly supports OpenStack already ‣ Simply need to pass URL of nova-api server and credentials ‣ http://tickets.opscode.com/browse/CHEF-1757 ‣ knife openstack server create ‘role[base]’ -I ~/.ssh/my.pem -x ubuntu -G default -i ami-a403f6xd -f m1.micro
- 71. Object Storage (Swift) ‣ Recipes originated from Anso Labs’ repository ‣ https://github.com/ansolabs/openstack-cookbooks ‣ Included in the ‘bexar’ branch ‣ Untested so far
- 72. Image Registry (Glance) ‣ Recipes originated from Anso Labs’ repository ‣ https://github.com/ansolabs/openstack-cookbooks ‣ Included in the ‘bexar’ branch ‣ Untested so far
- 73. Scaling changes how we deploy OpenStack!
- 74. Deployment Scenarios ‣ Single machine is relatively simple ‣ Controller + Compute nodes is a known quantity for small installations ‣ Nova + Swift + Glance in large installations ‣ Services separated and HA configurations supported ‣ Documentation and Chef Roles will be the solution
- 75. Cactus, Diablo, ... Development continues... Branches for each stable release Design Summit in April Design Summit in the Fall
- 76. Get Involved! https://github.com/mattray/openstack-cookbooks/tree/bexar http://lists.openstack.org http://lists.opscode.com #chef on irc.freenode.net #openstack on irc.freenode.net [email protected] [email protected]