Automation now has two V3 scenarios related to configurations or execution environments. As an alternative to trying to spec something in Automation for this, we may want to look for opportunities for linking to Configuration Management resources. Configuration Mgmt scenarios are currently more focused on things like SCM and product lifecycles, but I think representing the configurations associated with automation executions makes sense as well. All three automation resources (plans, requests, results) could have links to configuration resources. Thoughts? A good fit, or too much of a stretch?
http://open-services.net/wiki/configuration-management/Configuration-Management-Scenarios http://open-services.net/wiki/configuration-management/Configuration-Management-Terminology Regards, Mike Michael Fiedler IBM Rational Software [email protected] 919-254-4170 "Oslc-Automation" <[email protected]> wrote on 03/06/2013 07:39:33 AM: > Martin P Pain <[email protected]> > Sent by: "Oslc-Automation" <[email protected]> > > 03/06/2013 07:39 AM > > To > > [email protected], > > cc > > Subject > > [Oslc-Automation] New automation scenario: Temporary deployment > scenarios (tear-down and multiple use) > > Hello all, > > I have created a new automation spec v3 scenario for discussion: > Temporary deployment scenarios (tear-down and multiple use). > > This is to address the issue of tearing down resources that were > deployed through the deploy domain of the automation spec, and also > managing multiple clients using the same automation result (as that > has an effect on when it is torn down). > > Stephen Rowles and I have thought about some of the ways this could > be achieved in the spec - the details are on the wiki. > > Regards, > Martin Pain > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with > number 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU > _______________________________________________ > Oslc-Automation mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
