Posted by mattray on November 2, 2012
Getting back into the swing of semi-regular updates. Last week was the Chef Developer Summit, lots of great conversations and quite a few people interested in OpenStack. This week was catching up mostly, trying to clean up a few Essex leftovers before moving to Folsom.
- I bumped to Essex versions to 2012.1.0 to sync to the OpenStack versioning per feedback at the OpenStack Summit. I tagged everything for Essex and merged to master.
- Added an ‘lxc’ role to enable using LXC. Just an attribute and it just worked, so awesome.
- Added placeholder cookbooks for quantum, cinder and ceilometer. These have the suffix “-cookbook” in my GitHub, there was some discussion about wanting to rename the cookbook repos for the other 5 projects, anyone feel strongly?
- Updated all the Community cookbook dependencies and retested (apt, erlang, database, ntp, apache2, database, mysql, rabbitmq, openssh)
- Released a new version of pxe_dust which enforces assigning the PXE-booted NIC as eth0.
- Trying to coordinate Chef support for the bare-metal provisioning tool Razor, ping me if you’re interested.
- Canceled the NYC Chef for OpenStack Hack Day and NYC Chef Meetup.
- Preparing for the Opscode/DreamHost webinar “Automating OpenStack and Ceph at DreamHost with Private Chef“.
Next week I’ll be in Chicago presenting at the CME Group Technology Conference, ping me if you’re in Chicago and want to catch up. My OpenStack goals are to merge in the outstanding pull requests and resync with the latest Folsom work from rcbops, hopefully merging in some more branches.
Posted in chef, community, openstack, opschef | Tagged: chef, openstack, opschef | Leave a Comment »
Posted by mattray on October 23, 2012
I have primarily been focused on documentation lately and the http://github.com/mattray/openstack-chef-docs is the repository. Since there is so much interaction between the various components, prerequisites and cookbooks, I felt a unified document format would best serve our needs. The various markdown readmes and documentation is slowly migrating to this single repository so it can be kept updated in a single location and link to the various components.
The docs are in Restructured Text and use Sphinx, which is compatible with the http://docs.openstack.org source docs. The license matches the OpenStack documentation’s Apache V2 and Creative Commons Attribution ShareAlike 3.0 License. Opscode has standardized on this format for our own documentation and in the near future it will be merged upstream with official Opscode documentation.
The evolving document is currently broken into these 6 components:
* Architecture – overview of the architecture for Chef for OpenStack.
* Prerequisites – the hardware, network and operating system requirements.
* Installation – how to install Chef for Openstack.
* Example Deployment – example configuration of a small test lab.
* Knife-OpenStack – using the OpenStack plugin for Knife for provisioning and managing instances.
* Additional Resources – additional useful information and links related to Chef for OpenStack.
The docs are just getting started, lots of placeholders but I’m active writing. Please feel free to send corrections and additional details to help fill things out. There will be a permanent URL for the docs online soon, here is a temporary link:
Posted in chef, community, openstack, opschef | Tagged: chef, docs, openstack, opschef | Leave a Comment »
Posted by mattray on October 23, 2012
I’ve decided to start cross-posting my status emails for the Chef for OpenStack project to help spread the word. The Chef for OpenStack mailing list is here, please join: http://groups.google.com/group/opscode-chef-openstack
I apologize for the lack of updates, but I come bearing lots of news. For a quick summary of the state of Chef for OpenStack, check out this deck from my presentation at the OpenStack Summit:
Speaking of the OpenStack Summit, it was quite productive despite not getting to attend enough sessions due to meetings and booth duty. Monday there was a session on “Upstreaming Chef Cookbooks”, which was essentially a meetup of folks working on Chef for OpenStack. We compared notes and there is quite a lot of work being done in the various branches maintained outside the Opscode one, I’m looking forward to merging as much of the work as possible. Tuesday I gave my general Chef for OpenStack presentation linked above and we had a “DevOps Panel” later that day where there was an engaging discussion on the various issues facing deployers of OpenStack. I’ll link up videos as they become available.
Some short-term takeaways from the Summit where that there is a tremendous amount of development effort I was unaware of and the pace is about to pick up substantially. DreamHost and AT&T have a number of patches to be merged and work has already started on Folsom by several folks. The general consensus was to move the focus to Folsom now that it’s out, the cookbooks have been tagged and the repos have all been merged back to master. The ‘essex’ branches are working and have been pushed to the Community site for direct download and are still available of course if you want to continue development.
There were so many great discussions and ideas shared, I’m really looking forward to the work ahead. I’ll try to post more frequently, so the level of engagement will continue to get better.
Posted in chef, community, openstack, opschef, opscode | Tagged: chef, openstack, opschef | Leave a Comment »
Posted by mattray on November 17, 2010
I was fortunate enough to be at the OpenStack Design Summit last week in San Antonio, TX and one of the ideas that came up that I found really intriguing was the concept of a single-box easy install for OpenStack Compute (maybe Object Storage could fit on the same machine, not sure yet). To help facilitate this, we started up an OpenStack-Chef mailing list where we’ll be discussing automating installation of OpenStack Compute as well as deploying to a running Compute instance.
Hopefully we’ll free up some time to work on it soon, but while I was there I started putting together some rough specs for a machine we could use for testing and eventually using with Chef training to replace using EC2. We figured we needed enough horsepower to run 20 or so instances on the server, and shoot for around $1000 on the price. Here’s what I found on NewEgg.
So really it comes down to about $730 plus whatever storage option you go with. SSD is still expensive but might be worthwhile, but $165 for 1.1TB RAID5 isn’t too shabby and might make running Object Storage a potential option. Prices keep dropping of course, so this is probably close to being out of date already.
Posted in chef, geekery, openstack | Tagged: chef, openstack, opschef | 2 Comments »