First, we’ll have our Crowbar demo rack showcasing LIVE MULTI-NODE DIABLO DEPLOYMENTS and some IMPORTANT FEATURE AND COMMUNITY ADDITIONS. No spoilers here – you’ll have to come by. Of course, it’s in the git hub too, but we’ve put a bow on it.
Second, there’s a DEPLOYMENT BLUE PRINT discussion about getting better interlocks between OpenStack development and deployment. We really need to reduce the pain and lag between adding great features and using those features.
Next, we’ve got a limited audience CONCEPT SNEAK PEEK for something from our labs that we think is very interesting and we’d like to get input about. Unfortunately, we’re very limited with space & time for this whisper session so you’ll need to contact OpenStack@Dell.com to request an invitation.
Finally, at the Conference, you can see OUR TEAM IN ACTION:
Thurs 11:30 – Dell Keynote by John Igoe
Thurs 3:30 – Private Cloud Panel w/ Rob Hirschfeld
We are doing the work in the open on the Crowbar Github so you have access to the very latest capabilities and it also means that the head the Crowbar may be unstable while we add capabilities. We feel like this is an important trade off because it allows us to keep up with the rapid pace of development in OpenStack (and other projects). This is the motivation for the recent modularization work and will continue to be a feature driver for Crowbar enhancements because it allows Crowbar users to easily bring in updated bits.
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.
We’ve been so busy working on getting RHEL support ready to drop into the Crowbar repos that I have not had time to post about what’s coming next for Crowbar. The RHEL addition has required a substantial amount of work to accommodate different packaging models and capabilities. This change moves Crowbar closer to being able allow nodes’ operating systems (the allocated TFTP Boot Image) to be unique per node.
I will post more forward looking details soon but wanted to prime the pump and invite suggestions from our community.
OpenStack Diablo Barclamps. Expect to see individual barclamps for various components like Keystone, Dashboard, Glace, Nova, Swift, etc)
Barclamp versioning / connected imports. This feature will enable Crowbar to pull in the latest components for barclamps from remote repositories. I consider this a critical feature for Crowbar’s core DevOps/CloudOps capabilities and to support more community development for barclamps.
We are also working on some UI enhancements
Merging together the barclamps/proposals/active views into a single view
Enabling bulk actions for nodes (description, BIOS types, and allocate)
Allowing users to set node names and showing the names throughout the UI
More clarity on state of proposal application process (stretch goal)
I am planning to post more about our design ideas as work begins.
If you want to help with Diablo barclamps, these will be worked in the open and we’d be happy to collaborate. We’re also open to suggestion for what’s next.