Openstack• Cloud management software• Over 80 countries• Over 100 companies• Over 7000 developpers• Cloud OS mainly for IaaS• Amazone EC2/S3/EBS/VPC compatible• OpenStack Mission“To produce the ubiquitous open source cloud computing platform that will meetthe needs of public and private cloud providers regardless of size, by being simpleto implement and massively scalable.”
Openstack History• 2005 Rackspace development start• 2010.3 Rackspace make cloud software to open source• 2010.5 NASA Nebula opensource• 2010.6 Rackspace, NASA established OpenStack• 2010.10 Austin release• 2011.2 Bexar Release• 2011.4 Cactus Release• 2011.9 Diable Release• 2012.4 Essex release• 2012.9 Folsom• 2013.4 Grizzly Release• 2013.10(?) Havana• Release Naming• https://wiki.openstack.org/wiki/ReleaseNaming
Openstack Component• Swift - Object Storage• Glance - catalog and repository for virtual disk images• Nova - provides virtual servers upon demand• Horizon - provides a modular web-based user interface for all theOpenStack services• Keystone - provides authentication and authorization for all the OpenStackservices• Quantum - provides "network connectivity as a service" between interfacedevices managed by other OpenStack services (most likely Nova)• Cinder - provides persistent block storage to guest VMs
Chef• Chef is a systems and cloud infrastructure automation framework thatmakes it easy to deploy servers and applications to any physical, virtual, orcloud location, no matter the size of the infrastructure.http://docs.opscode.com/chef_overview.htmlChef relies on abstract definitions(known as cookbooks and recipes)Cookbooks and receipes are writtenin Ruby
Chef Cookbooks• Cookbooks are used to tell Chef how each nodein your organization should be configured.
Puppet• Puppet is IT automation software that helps system administratorsmanage infrastructure throughout its lifecycle, from provisioning andconfiguration to patch management and compliance
DevOps• DevOps (a portmanteau of development and operations) is asoftware development method that stresses communication,collaboration and integration between software developers andinformation technology (IT) professionals. DevOps is a responseto the interdependence of software development and IT operations.It aims to help an organization rapidly produce software productsand servicesWikipedia: http://en.wikipedia.org/wiki/DevOps
Crowbar Overview• What is a Crowbar• Crowbar is a platform for server provisioning and deployment from bare metal.• Crowbar was originally developed by the Dell CloudEdge Solutions Team asan OpenStack installer.• Features• Server discovery• Firmware upgrades• Operating system installation via PXE Boot• Application development via ChefPlease Find Dell Crowbar at GitHub
Crowbar Overview• Current ReleaseThe release currently under development is Pebbles, which will be the base of our nextOpenstack Grizzly and Cloudera Hadoop solutions. It is based on the Crowbar 1.xcodebase.Crowbar 2.0Latest releaseDetail to be shown later
• Barclamp is the description of a component that can bedeployed on the target node. It generally consists of:o Rails components (i.e. models, controllers, views, etc.)o Contents component (Chef components cookbooks, data bags etc.)o Executables (e.g. a CLI interface)o Meta-data describing the barclamp and its dependencieso Documentationo TestsBarclamps
Crowbar 21. simplify our use of Chef and eliminate Crowbar requirements in our Opscode Chefrecipes.A.reduce the initial effort required to leverage CrowbarB.opens Crowbar to a broader audience (see Upstreaming)What does “enable upstream recipes” mean? Not just fishing forcommunity goodness!http://robhirschfeld.com/2012/07/05/upstreaming/
Crowbar 22. provide heterogeneous / multiple operating system deployments. This enables:A.multiple versions of the same OS running for upgradesB.different operating systems operating simultaneously (and deal withheterogeneous packaging issues)C.accommodation of no-agent systems like locked systems (e.g.: virtualization hosts)and switches (aka external entities)D.UEFI booting in Sledgehammer3. strengthen networking abstractionsA.allow networking configurations to be created dynamically (so that users are notlocked into choices made before Crowbar deployment)B.better manage connected operationsC.enable pull-from-source deployments that are ahead of (or forked from) availablepackages.
Crowbar 24.improvements in Crowbar’s core database and state machine to enableA.larger scale concernsB.controlled production migrations and upgrades5. other important itemsA.make documentation more coupled to current features and easier to maintainB.upgrade to Rails 3 to simplify code base, security and performanceC.deepen automated test coverage and capabilities