index / Automation Meetings / This page

Time: 11:00AM Eastern US (Currently 3pm UTC, 5pm CET)

Agenda

Chair: Martin

• Issues
  • Automation Specification Version 2.0 Issues
    • bug in Auto 2.0 parameterDefinition example - not on issues page.
  • Automation Specification Version 2.1 Issues
    • 1 new - missing futureAction predicate in vocabulary changes appendix.
  • Automation Specification 2.1 Feedback
• Main agenda items:
  • Review 12 June minutes
  • Review 26 June minutes
  • Workgroup end-of-life/transition plan
    • Receiving reviews, then finalization, for Automation 2.1 & Actions. Then in maintenance mode for 2.1.
    • Finishing Availability spec.
      • As this is taking longer than anticipated, we could move this to OASIS.
  • Automation 2.1 & Actions
    • Action metadata at resource type/shape level (Scroll down for initial email).
  • “Availability”
    • Discuss: Make AvailabilityCondition as own type or part of AvailabilityResource?
    • Discuss: compoundState - replace with/ additionally introduce consistentState with type boolean (need to ask Jürgen)?
    • Discuss: rto, mttr, mttf - use integer instead of ems:Measure (much more simple)? Remove completely?
    • Discuss: SLA not required for scenarios. Is it obvious that it will be required by most implementors of the spec? Or remove it?
    • Question/ Discuss: Make Redundandy{Group, Member} subclass of Availability{Group, Resource}. I’m not sure, what is the best solution?
    • Question: Did I get it right to not use http://open-services.net/ns/availability and instead use http://open-services.net/ns/auto, because I would need to request for this URL at OSLC Core?
    • Question: Not sure about consequences of memberOf vs. member (direction of linkage between a group and it’s members.
    • Question: How to express in the spec that a service provider should define it’s own property values but possibly define a small set of values, that are enforced (like online/ offline and starting/ stopping for currentState).
  • Workgroup business
    • Next meeting?
  • AOB

Actions from previous meetings

None

Minutes

Attendance

Martin Pain, John Arwe, Juergen Holtz, Tim Friessinger

Resolutions passed

• Approved minutes of meeting on 2014-06-12.
• Approved minutes of meeting on 2014-06-26.
• 2.0 make the changes described in http://open-services.net/pipermail/oslc-automation_open-services.net/2014-May/000756.html and update 2.0 issues page
• 2.1 issue 1: add term to change list + vocab document, using revised definition
• 2.1: legitimize oslc_auto:futureAction’s use in resource shape by adding example of it

Minutes

• bug in Auto 2.0 parameterDefinition example

  • proposed: make the changes described in http://open-services.net/pipermail/oslc-automation_open-services.net/2014-May/000756.html
  • resolved: no objections
  • action: johnarwe to make changes and document on 2.0 issues page
  • 2014-07-17 changes done, awaiting WG review to close issue 15. Note that 2 additional issues were found and fixed, see 15’s text for details. Also rolled the change up into 2.1 issue 2, in same awaiting WG review state. Note that n-1 of the 2.0 post-finalization issues are also in “awaiting WG review” state. Also fixed on 2.0 samples page; tried to fix the PI escaping there as well, but saving re-escaped them so I sent email to the webmaster.

• missing futureAction predicate in vocabulary changes appendix (2.1 issue 1)

  • proposed: add term to change list + vocab document

  • resolved: no objections

  • discussion of how to revise term’s definition given email feedback.

  • proposed: remove “the type of resource” sentence, which makes the revised version:

    A predicate that links to an action that is not currently executable on this resource, but may be executable in the future and/or on other resources. For example, in OSLC Automation this is expected to link from an oslc_auto:AutomationPlan to an oslc:Action resource with zero bindings (as it is not executable), with the meaning that the executable form of the action may be available on oslc_auto:AutomationResult resources generated by that Automation Plan.

  • resolved: no objections
  • action: johnarwe to make changes
  • 2014-07-17 changes done, awaiting WG review to close Auto 2.1 conv issue 2. More details there.

• Automation Specification 2.1 Feedback

  • continue discussion on-list

• Review 12 June minutes

  • action: martin to ensure the resolved small text update to Actions 2.0 was done
  • minutes approved unanimously

• Review 26 June minutes

  • martin: remove one resolution incorrectly carried over from earlier

• Workgroup end-of-life/transition plan

  • Juergen: our priorities have changed, not clear when we’ll resume work internally on this. unfamiliar with OASIS. where would temporary pause cause the least harm?
  • Martin: little to no practical difference
  • Juergen: not ready to make a decision today. continue discussion next call.

• Automation 2.1 & Actions

  • http://open-services.net/pipermail/oslc-automation_open-services.net/2014-July/000781.html
  • oslc_auto:futureAction’s use in resource shape … agreement to legitimize the usage in the spec text as another known usage. I.e. as an example, no normative changes required.
  • action: johnarwe to add to 2.1 spec and then wg can review afterward
  • 2014-07-17 changes done, awaiting WG review to close Auto 2.1 conv issue 3 and Actions 2.0 conv issue 1. Changes were updates to Auto 2.1’s existing section and Actions 2.0 - add future actions section

• “Availability” Discuss: compoundState - replace with/ additionally introduce consistentState with type boolean (need to ask Jürgen)?

  • discussion; Martin wants true/false somewhere.
  • Juergen: dislike “consistent” state; could have boolean for desired=actual, that’s the important case.
  • Juergen: intend to express details of what’s going on
  • Tim: I will propose couple of properties on the mailing list.

• next meeting

  • Martin unavailable all of next week. +2 weeks?
  • Tim: vacation until Aug 2. No point in discussing availability until then.