I shared the following with the Crowbar listserv and wanted to post it for the larger audience. If you want the latest on Crowbar then subscribe!
We’ve been getting questions and defects (thanks Matt Ray) about how we are going to allow you to update and add barclamps to Crowbar. We’re working on that exact issue right now – you can watch me on the “modules” branch of the github.
NOTE TO CROWBAR FOLLOWERS: we are moving some items around in the repo! There are “cactus” and “v1.0” tags in place so you can still build the current trees after we start the refactor.
We’ve got some big plans that I’ll outline on the list and earlier posts.
Right now, we’re working to modularize barclamps so that each one is in its own github repo. This will allow you to pull in barclamps at build time or live on site. We’re also creating import/update routines that work for live systems to make it easier to develop barclamps. Once again, that’s on the github modules branch. These will be exposed as rake barclamp:create[“foo”] and rake barclamp:install[“../foo”] type commands and I’ve committed to create some “how to make barclamps” videos.
That work is a prelude for a hard push on OpenStack Diablo before the design conference. All that work will also be done in the github but the Diablo barclamps will be in independent repos from the Crowbar framework.
If you want to get started early. 80% of a barclamp effort is around the Chef Cookbooks. Keith Hudgins with DTO did a great job writing up barclamps here: http://kb.dtosolutions.com/wiki/Deploying_the_cloudfoundry_barclamp. We’re changing some of it to make it much easier and more modular.
Pingback: Don’t fork it up. OpenStack needs community collaboration « Rob Hirschfeld's Blog
Pingback: Technical details of pending Crowbar changes « Rob Hirschfeld's Blog
Pingback: What does “enable upstream recipes” mean? Not just fishing for community goodness! « Rob Hirschfeld's Blog