On Sat, Sep 7, 2013 at 6:56 PM, Victor Lowther <victor.lowt...@gmail.com>wrote:
[ snippity ] > Next Steps for Crowbar 2.0 (in rough dependency order): > > - Make framework side of the Network barclamp operate properly, > instead of working in rigged demo mode. > Right now, the Crowbar framework side of things is just smart enough > to allocate an IP to the admin node to exercise the network recipe and > bootstrap the rest of the admin node roles. It needs to be able to track > IP address allocations in a generic fashion, and it needs to be able to > support other networks besides the admin network. > > As of the latest set of not-yet-merged pull requests, the network barclamp is able to create the admin network and and allocate the IP for the admin node out of it for real. Along the way it dynamically creates the required Chef and Crowbar roles, and allows allocation of the IP to be deferred until just before Chef needs to bind it to the node. > > - Flesh out node discovery. > We can boot nodes into Sledgehammer, but we need to wire in more > functionality to allow node discovery and configuration to take place. > - Come up with a reasonable OS installation story, and implement it. > - De-cruft the Crowbar-specific Chef cookbooks. > While the current Chef cookbooks work with minimal changes, a > side-effect of how the Crowbar framework manages configuration data via the > node-role graph is that it is very easy for most of our core cookbooks to > operate in an entirely attribute-driven fashion. Refactoring them and > stripping out the CB 1.x specific cruft would be a good way to learn the > framework. > > Questions? Comments? Flames? Pull requests? I am at your service. > > > >
_______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
