[OSLC-Configuration] [Oslc-Automation] New automation scenario: Temporary deployment scenarios (tear-down and multiple use)

[David N Brauneis]

Mike,

I was kind of debating a very similar thought to yours as I was thinking 
about this... It seems like we are going to end up redefining a lot of 
similar concepts in the Automation specification that already exist in the 
Configuration Management area. I certainly think it needs to be explored 
in a little more detail before we just decide to create something in the 
Automation area.

Should we synchronize with someone in the Configuration Management 
workgroup?

Regards,
David
____________________________________________________________________
David Brauneis
STSM, Rational Software CTO Office, Advanced Technology & New Product 
Incubation
email: brauneis at us.ibm.com | phone: 720-395-5659 | mobile: 919-656-0874



From:   Michael F Fiedler/Durham/IBM at IBMUS
To:     oslc-automation at open-services.net, 
oslc-configuration at open-services.net, 
Date:   03/08/2013 11:05 AM
Subject:        Re: [Oslc-Automation] New automation scenario: Temporary 
deployment scenarios (tear-down and multiple use)
Sent by:        "Oslc-Automation" 
<oslc-automation-bounces at open-services.net>



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
fiedler at us.ibm.com
919-254-4170

"Oslc-Automation" <oslc-automation-bounces at open-services.net> wrote on 
03/06/2013 07:39:33 AM:

> Martin P Pain <martinpain at uk.ibm.com> 
> Sent by: "Oslc-Automation" <oslc-automation-bounces at open-services.net>
> 
> 03/06/2013 07:39 AM
> 
> To
> 
> oslc-automation at open-services.net, 
> 
> 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
> Oslc-Automation at open-services.net
> 
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
_______________________________________________
Oslc-Automation mailing list
Oslc-Automation at open-services.net
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-configuration_open-services.net/attachments/20130308/f7465b00/attachment-0003.html>