All, We've been making a lot of progress on Deployments and deployment states (proposed, committed, active) as reflected by different snapshots.
In earlier designed, we'd captured something similar in the Attrib values (proposed vs actual). Differences between these values are reflected as the Attrib state. It looks like these two approaches are in conflict and we'll need to start resolving them over the next few days. I do not expect this to be a sweeping change. Basically, I'm proposing that general Attrib.state will be a reflection to the state of the snapshot that it is connected with. For example, a snapshot that is the Deploy's proposed snapshot should have attribs that are also in state proposed. This would be true for committed and active as well. We have a few Attribs (HasNode specifically) that will still have their own state definition. I also expect that we'll drop the "requested" component of the attribs since that information is also redundant with the active/commited/proposed state. This will be clearer as we incorporate inbound state from the jig. Rob ______________________________ Rob Hirschfeld Distinguished Cloud Solution Architect Dell | Cloud Edge, Data Center Solutions blog robhirschfeld.com, twitter @zehicle Please note, I am based in the CENTRAL (-6) time zone
_______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
