All, The notes have been moved to https://github.com/crowbar/crowbar/wiki/Sprint-2013-05-24 for collaborative editing. I've uploaded the recording from today's design review: http://youtu.be/1PtqheBTN1s
The updated DB schema w/ a reference example is here: https://github.com/cloudedge/barclamp-crowbar/blob/master/doc/devguide/model/crowbar_model.png I'd encourage a discussion on the list (please limit to one card per thread!). NEW CONCEPT NOTE! In review of these notes with Victor, he made a very interesting suggestion to have deployments ABOVE barclamps. This would mean that users would have a logical deployment group (e.g.: test, dev, prod) that includes all the barclamps they are using. Since ROLES are the really container, you'd choose the roles that you wanted to include in a deployment and Crowbar would use the dependency graph to include all the needed barclamps to implement that role. For example, if you choose the Nova Compute role then it would add the Nova Controller, Keystone, SQL, Message Bus, Network...etc roles. Hmmm... that would also mean that the node available in a deployment would be added to the Crowbar Role. I'm really excited about this suggestion. I think it makes coding/using Crowbar simpler and natural. Rob ______________________________ Rob Hirschfeld Distinguished Cloud Solution Architect Dell | Cloud Edge, Data Center Solutions cell +1 512 909-7219 blog robhirschfeld.com, twitter @zehicle Please note, I am based in the CENTRAL (-6) time zone
_______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
