Victor Lowther (victor.lowt...@gmail.com) wrote:
> As of the latest set of pushes to development release, Crowbar 2.0 is now
> able to deploy an admin node that can then boot other nodes into
> Sledgehammer. Unlike the last time CB2.0 was able to do this, the Crowbar
> framework is performing all the work needed to bootstrap itself into
> usefulness without manual intervention. With the current codebase, you
> should be able to:
>
> - Build a Crowbar ISO using the usual ./dev build --os ubuntu-12.04
> method.
> - Boot a VM (or real machine, if you have one to spare) to the generated
> ISO, and let it install
> - Once the admin node is installed, log in as crowbar/crowbar, sudo -i
> to root, and run /opt/dell/bin/install-crowbar your.admin.fqdn
> - Watch the script output with screen -r
> - Once screen terminates, log in to the Crowbar webui at
> http://192.168.124.10:3000 with crowbar/crowbar
> - Poke around all the new UI bits and see all the new shininess
> - Boot other nodes into sledgehammer and then watch them drop to a login
> prompt instead of doing something useful
>
> While that does not sound like much on the surface
Actually, it sounds like a lot to me, bearing in mind the deep
structural overhaul. Congrats on getting to this milestone!
> Design difference between CB 1.x and CB 2.0:
[snipped]
THANK YOU for writing these key changes up. This should be
tremendously useful - both as a memory refresher for myself, and also
for colleagues who haven't yet been made aware of recent CB 2.0
design.
This info is too valuable to be allowed an undignified passive burial
in the mailing list archives. Please can we find a new home for it
where it can be expanded, refined etc.? I'm not sure the dev guide is
entirely the right place, because it's important that normal users are
also able to learn the high-level architecture. So maybe in the user
guide?
> - Node-role bindings (called noderoles for short -- please suggest a
> better name for this!)
Assignments? That's about the best I've managed so far ...
http://thesaurus.com/browse/assignment
> 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.
> - 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.
Sounds great!
_______________________________________________
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/
