History   View   Links to this page 2013 October 3 | 12:09 pm

index / Automation Meetings / This page

Time: 11:00AM Eastern US (Currently 4pm UTC)

Agenda

Actions from last meeting

Person Action Due
Martin Flesh out/document how Actions could be used to implement teardown, and more generic approach (the core-proposal) - might delegate parts to John This meeting
Umberto Update draft V.next spec with Template changes. Flag “This is new for 2.1” at beginning of new section. ?
Martin Report on his team’s desired timescale for convergence & finalisation. This week
Martin Integrate terminology proposal into primer. This week

Actions carried over/not yet due:

Person Action Due
John Ask Steve S or Sam P to write up applying Actions to Cm. (Perhaps once Martin’s generic write-up done).
Charles Write up how existing spec can be used for orchestration scenarios Feed back 10th Oct
Michael Inform new chairs about updates needed on new spec draft: contributors and licence changes. 10th Oct
Michael Follow up on discussions about how to highlight spec changes from v2 10th Oct
Michael Read Martin’s document, and check it makes sense to those not involved in the offline discussion 3rd Oct

Minutes

Attended: Martin Pain, Steve, Umberto, John A, Charles R

  • No problems raised for last week’s minutes
  • Generic Actions
    • Steve S to look at Actions draft and provide feedback - next week
    • Steve S: why not just POST
    • MP answered….
    • SS: Pulling things that HTTP already exposes? Methods available
    • SS: Feels like a lot of handling 5% cases.
    • MP: Domains suing Actions can tie the flexibility down to a minute.
    • SS: Motivation for requirements? “Transitioning” the state of a resource - might make it clearer that more is happening than in a PUT.
    • Actions depend on the current state - rather than ranges of properties which may not adequately advertise the transitions that are available. It advertises the state transitions that are available form the current state.
    • CM (state transitions) only ever expose currently-valid transitions.
    • Automation will only expose currently-valid transitions on results, but also wants to advertise on the plan what transitions will be available on the result. Auto results want to avoid the need for the resources being transitioned to have their own RDF resources.
    • CR: On AutoResults, if the result is NOT the resource that is being torn down, it might be reasonable for the action to remain on the result after teardown has occurred.
    • The “context” requirement
    • CR: Do we need to document anything about Auto Results as the deployed result vs not?
    • MP: Perhaps document the problems that could occur if they are the same. I primer?
  • CR: The “problem” in the definition of Automation, where creation of the request implies execution of it. Do we want to fix that in future? JA: Templates fix that problem
  • Generic Actions:
    • Need scenarios/use cases.
    • Link to/copy CM ones?
    • Include teardown
  • Teardown
    • MP write up how actions are applied to Teardown
  • Template scenarios:
    • Umberto to update draft spec for next week
  • Actions from last week
    • MP happy with target finalisation for end of year
    • Need to plan right-to-left schedule
  • Remove versioning from primer.
  • Talk through rest of Actions document next week.

Actions resulting from this meeting

Person Action Due
Michael Read Martin’s document, and check it makes sense to those not involved in the offline discussion 3rd Oct
Umberto Update draft V.next spec with Template changes. Flag “This is new for 2.1” at beginning of new section. 10th Oct
Steve S Feed back on Actions. Discuss with CM workgroup. Feed back 10th Oct
Charles Write up how existing spec can be used for orchestration scenarios Feed back 10th Oct
Michael Inform new chairs about updates needed on new spec draft: contributors and licence changes. 10th Oct
Michael Follow up on discussions about how to highlight spec changes from v2 10th Oct
Martin Write up how Actions apply to Teardown 10th Oct
Martin Add scenarios/use cases to Actions page 10th Oct
Martin Remove versioning from primer 17th Oct
Martin & Umberto Plan schedule/deadlines required for getting v2.1 into finalisation by the end of the year 17th Oct