Hello, I started working on a proof of concept to see if we could wrap the upstream stackforge cookbooks[1] in the existing barclamps.
The stackforge cookbooks support the grizzly openstack branch. There are several advantages to using them: the style of the cookbooks is clearer and more orthogonal (e.g. platform-specific things are set in the attributes file), they have good chefspec test coverage and a growing community. I have a first working version up in a new branch in our SUSE-Cloud keystone-barclamp repository[2]. Some pieces aren't there yet, like password management and SSL support, but it works successfully with the other openstack barclamps in the release/pebbles/master branch. The code is pretty simple, it basically just maps some of the existing attributes from crowbar-names to stackforge-names. Basically all of it is in the default recipe[3]. I haven't changed any existing attribute names; changing those could reduce the size of the default recipe. So like I said, this is just a working proof of concept which we'd like to get some feedback on from the wider crowbar community to see if this would be a worthwhile path to follow. Thank you, Ionuț [1] https://launchpad.net/openstack-chef [2] https://github.com/SUSE-Cloud/barclamp-keystone/tree/stackforge-wrap [3] https://github.com/SUSE-Cloud/barclamp-keystone/blob/stackforge-wrap/chef/cookbooks/keystone/recipes/default.rb _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
