Chef for OpenStack Grizzly Roadmap

OpenStack Summit April 2013

Matt RayOpscode

On the last day of the Spring 2013 Summit we gathered to plan the roadmap for the Chef for OpenStack community.

Who was there

• AT&T

• Dell

• DreamHost

• HubSpot

• KT

• Midokura

• Opscode

• Rackspace

• SUSE

There had been several days of conversations, these companies were all represented in the meeting. Missing: eNovance, HP, IBM, KIO, Mirantis

Where

• #openstack-chef on irc.freenode.net

• groups.google.com/group/opscode-chef-openstack

• github.com/mattray/openstack-chef-docs

• @chefopenstack

The resources we're using

Licensing

• Apache 2

• Opscode CLA/CCLA required

• http://wiki.opscode.com/display/chef/How+to+Contribute

• http://wiki.opscode.com/display/chef/Approved+Contributors

Attendees were all covered already

Where on GitHub

• http://github.com/osops

• chef-repo/

• berkshelf, not git submodules

• cookbooks all end in "-cookbook"

• ie. "nova-cookbook"

• "operations" cookbooks outside scope

• ie. logging, monitoring, provisioning

Move to community GitHub repo, not Opscode's. Opscode will upstream from this repo.

Cookbooks

• cinder

• glance

• horizon

• keystone

• nova

• quantum

• swift

• ceilometer & heat eventually

The core OpenStack services

Goal of incorporating into OpenStack

• Get on StackForge

• will provide CI

• which everyone will probably slave

• Gerrit for code reviews

• we'll sort out reviewers once we start

• Testing with TestKitchen initially

• Grenade? Kong? SmokeStack?

We want to go into "mainline" OpenStack

• support alternative package sources

• source-built coming ("VanillaStack")

• packaging recipes before configuration

• ie. "nova/recipes/nova-compute-packages"

Packages

Use distro packages were applicable, but not everyone wants to use them. Build from source will come in eventually.

Chef Style Guide

• Chef 11 target release

• partial search

• partial templates

• Full-stack Chef-client compatible

• Ruby 1.9.x

• Upstream community cookbooks

• Foodcritic as much as possible

Table stakes

Chef Style Guide

• openstack-common instead of osops-utils

• Attribute injection

• attributes may short-circuit search

• few, if any, attributes in roles

• environment-driven attributes

• Chef Solo not actively supported

• platform logic in attributes files

Already using these patterns

• May release "2013.1.0"

• Chef repo for Grizzly

• Operating Systems (Ubuntu 12.04)

• Databases (MySQL)

• Hypervisors (KVM, LXC)

• Nova network FlatDHCP HA & VLAN

Initial osops release

Opscode employee Matt Ray and Chris McClimans are getting together after ChefConf to work on cleaning up Grizzly. Sources will be AT&T, Dell, HubSpot and Rackspace primarily.

• Operating Systems (RHEL, SUSE)

• Databases (Postgres)

• Hypervisors (Xen, bare metal)

• Cinder (Ceph, LVM, NetApp)

• Quantum (Bridge, Midokura, Nicira, OVS)

• Folsom backport

• HA Configurations may be stretch goal because of differing implementations

Grizzly Roadmap

SUSE: SLES, OpenSUSE, PostgresKT: XenHubSpot: bare metalDreamHost: CephAT&T: LVMRackspace: Bridge, NetApp, OVS, RHELOpscode: NiciraMidokura: Folsom, MidoNetAT&T, SUSE, Rackspace different HA setups

knife-openstack v0.7.0

$ 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)

Currently supported features.

knife-openstack compatibility

• Uses the OpenStack API

• Diablo, Essex, Folsom, Grizzly

• Cloudscaling

• Crowbar

• DreamHost

• Nebula

• Piston

• Rackspace Private Cloud

Continue to test for compatibility, will build out CI testing for Opscode-supported knife plugins.

knife-openstack Roadmap

• github.com/opscode/knife-openstack

• docs.opscode.com/plugin_knife_openstack.html

• tickets.opscode.com/browse/KNIFE/component/

• Continues to be managed by Opscode

• Test against multiple OpenStack deployments for compatibility

• next major release v0.8.0 (May)

• floating IP address management

• network assignment on server creates

More features will undoubtedly show up

• Submit talk "Chef for OpenStack Fall 2013 Overview & Status"

• Review this deck

• Report progress

• Submit for developer track session as well

• See you in Hong Kong!

Fall 2013 OpenStack Summit

We'll see what actually happens in November.