Jonathan, Great questions (and advanced apologies for the long reply). We'd originally thought to allow multiple barclamp proposals for exactly that purpose; unfortunately, that would mean being much more consistent with search in every barclamp that we've been able to accomplish.
Decomposing the request.... Our approach for new OpenStack releases is to use the pull-from-source (PFS) feature instead of advance packages. That allows us to be more specific in what gets selected and also makes it possible to fix bugs in advance of pulls being accepted. It's also OS agnostic. If you are interested in being part of that work, please consider using PFS and joining on community calls. With the Grizzly release (on Mesa) complete, the Dell team is starting to organize our efforts on that work. If PFS make sense, then one way to consider the Grizzly -> Havana migration is to be on PFS for both. In that case, you'd be able to migrate by changing the cookbooks and relevant code. The real challenge IMHO is that our dev process is not against a production system. We will work on the cookbooks/bits/deploy for a release with the objective to having it be complete for install. To break that cycle, we needed a different orchestration model which is one of the Crowbar 2 core requirements. However, it would be possible to have the Havana PFS cookbooks understand upgrades - it's a matter of finding people who can help ensure this is working. Rob -----Original Message----- From: crowbar-bounces On Behalf Of Jonathan Brownell Sent: Friday, August 02, 2013 3:42 PM To: crowbar Subject: [Crowbar] Crowbar plan for upgrading between OpenStack versions I'm using Crowbar to manage an existing cloud with a handful of Nova Essex compute instances, and I'm interested in pulling/updating to create a new barclamp-nova with the latest Havana .deb packages to light up a new Nova Havana cluster alongside what I've already got. (My eventual goal is to migrate the existing workloads over to Nova Havana and release my original compute nodes for other purposes.) Is there any way for me to have two "nova" barclamps installed side-by-side in Crowbar for this purpose? It seems quite non-trivial to make a new barclamp with a new name (i.e. "nova-havana"), since the barclamp name is woven all throughout the cookbook and would create a lot of conflicts unless I did a perfect job. Is there a Crowbar strategy that would allow me to perform this kind of step-up upgrade from one OpenStack Nova version to the next in the same environment? Thanks, -JB _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/ _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
