Hi everyone, Here's a link to the video of our design meeting:
http://youtu.be/bCLLfgLIGJQ and the notes: http://crowbar.sync.in/community-design-meeting-2014-03-05 This week: * Basic Updates - what we're up to. * Features and impact of move to Rails 4 * Docker Container management through a possible Container Jig * New Crowbar Attribs access via API * Building Discovery/Sledgehammer * Hinting for different workload Hardware/VM/Container types *Container vs VM vs Hardware Support:* *Repurposing Hinting:* When you create a node, it doesn't get any roles bound by default Then you can allocate an admin address will bind the network admin roles to it. Then add an API call to add default roles. Gives you a chance to change their configuration before the node gets marked alived and commited then kicks off discovery Goal is to remove the magic in the framework, and just expose the hooks to drive the API. *Multi-OS support -* is in. once attrib API was in place, then provisioner OS attribute could be set. Then you can change the role template, default target globally, deployment role... etc. then it kickstarts or preseeds. *Changing the hostname of the node:* Usability: we can already add CNAMEs (crowbar aliases) in DNS, but there are a lot of points in the framework where post-allocation hostname changing, and it has not been audited. -- Judd Maltin T: 917-882-1270 F: 501-694-7809 what could possibly go wrong?
_______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
