The minutes from this week's meeting are on the wiki:
http://open-services.net/wiki/automation/AutomationMeetings20131024/
* Last week's minutes accepted
* Trial implementers - we will need 2 before finalisation. Lyo can be one.
Can just be non-released prototypes. The more, and the more coverage, the
better. Very few hard requirements.
* Umberto not present to comment on templates
* TODO: Normalise current version to "v2.1", not "v3" or "postv2".
* MP would like to see orchestration write-up in primer
* Actions 2.0
* ITOpsToDev looks more about linking than state transitioning.
* Auto reqs - "would be ideal to" reuse existing interaction patterns
that clients already know. (reuse language)
* Auto scenario requires unattended execution - make it a SHOULD for
providers to provide an implementation that can be driven unattended.
* Use case: multi-select 100 bugs/tickets/ etc & transition all of
them
* TODO: Ask CM to review & confirm they are comfortable with the reqs &
specs as at the moment. Especially the complexity added by the
extensibility, etc, values.
* TODO: Answer last red Q.
* Resource shape tables in there by tomorrow. Equiv desc currently in
desc.
* Added "when linked to by action:action predicate" to MUST contain
"action:request" MUST. MP happy with this solution. TODO: Remove red
question.
* Constraint requiring zero-parameter option. MP proposes "SHOULD" in
"parameters" core section (not in profiles). No objections.
* JA proposes renaming action:action to action:availableAction.
* MP: executableAction?
* MP voted for action:action. As chair, wins.
* Raise it as a review point when we review the spec.
* How does a consumer know if it can execute an actions
* TODO: MP to think through how some key examples would work - both
identifying actions that can be used, and how they know they can't execute
other ones.
* Delegated dialog
* How does the client find it?
* TODO: Flesh out how delegated UIs play in here. - Umberto's imput
is important, as Tivoli uses them a lot. Umberto & Martin to both propose
how they would see it.
* New work - John
* Some products have approached me about new near-term work that seems
closely related to Automation, but distinct from what's in scope for 2.1
* Centered around availability:
* Exposing availability state (which for them is a complex
multi-property set of information, not a simple string or URI)
* Exposing availability groups of various flavors
* Actions to change the state - mainly start/stop, of various
kinds. Their actions are typically long-running so they're interested in
re-using the Automation/Actions work we've been incubating with CM.
* This seems like natural follow-on work to 2.1. It's not clear that
it's worthwhile creating a separate WG for this, given the public plans to
move to OASIS and the actions overlap.
* JA proposing making separate workflow in Automation WG. Decision for
chairs how much coordination of what type they want.
* Logistically, it might be easier to have separate Automation
meetings to incubate this post-2.1 work in parallel with 2.1 ... largely
disjoint set of participants.
* Paul: Consult with Steve Speicher, from something done in CM
(experimental resources) - not sure if that is a pattern that worked out
well.
* JA: Steve has seen this, since I knew he was traveling this week;
he actually suggested running it under Automation independently.
##Actions resulting from this meeting##
Person | Action | Due
------------- | ------------- | -------------
Martin | Normalise current version to "v2.1", not "v3" or "postv2". | 31st
Oct
Martin | Ask CM to review & confirm they are comfortable with the reqs &
specs as at the moment. Especially the complexity added by the
extensibility, etc, values. | 31st Oct
Martin | Update Actions 2.0 scenarios page as described above | 31st Oct
John | Update core Actions 2.0 proposal page as described above | 31st
Oct
Martin (and John?) | Think through profile identification - i.e. consumers
determining if they can execute an action | 31st Oct
Umberto & Martin | Flesh out how delegated UIs play in here. | 31st Oct
Umberto & Martin | Discuss availability work | 31st Oct
Kind regards,
Martin Pain
Software Developer - Green Hat
Rational Test Virtualization Server, Rational Test Control Panel
Open Services for Lifecycle Collaboration - Automation WG joint chair
E-mail: martinpain at uk.ibm.com
Find me on: and within IBM on:
IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20131025/eb379472/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 518 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20131025/eb379472/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1208 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20131025/eb379472/attachment-0001.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 360 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20131025/eb379472/attachment.gif>