Time: 11:00AM Eastern US

Agenda

• Main agenda items:
  • Specification issues
    • Automation Specification Version 2.0 Issues
      • After-finalization #4: OPEN - The OSLC Automation terms “Plans”, “Requests” and “Results” are not always suitable for display to all users, as they would not be aware of their OSLC meanings. There is no guidance on what wording to use when presenting these to users. The separate sub-domains might have different terminology that is appropriate.
        • 22 Aug 2013 - Proposal for Automation terminology guidance
        • 29 Aug 2013 - Preference for inclusion in existing document - Primer or V2 Spec
  • Implementation updates
    • Open forum for implementers to provide updates
    • Summarize any new implementation reports
  • Review 29 August minutes
  • Automation V3
    • Automation Scenarios V3 status - Topics TBD based on attendance. Possibilities include:
      • Scenario issues
        • Temporary deployment scenarios
          • Current proposal
          • See minutes from previous meeting for additions. TODO: Get this documented with examples
        • Orchestration Scenarios.
          
          • Agreed to shelve in 29 August meeting
          • TODO: Document how an some orchestration scenarios can be achieved with existing artifacts + current teardown and template scenarios + Update scenarios page
        • Automation Template Scenarios. Discuss scheduling scenarios around this.
        • Automation Agent/Worker Scenarios. Out - TODO: update scenarios page
  • Workgroup business
    • TODO: V3 draft specification
    • Workgroup ownership
    • Next meeting: 19 September at 11AM Eastern US

Minutes

Attending: Michael Fiedler, John Arwe, Steve Speicher, Martin Pain

• Specification issues
  • Documentation of terminology - add to primer and point to it from the sub-domain section of the specification
    • accepting this proposal - http://open-services.net/wiki/automation/Proposal-for-Automation-terminology-guidance/
• Implementation updates
  • Jenkins/Hudson as automation provider and/or consumer. Activity is starting now and feedback is welcome.
• Specification version
  • Proposed that the next revisions will be Automation V2.1. Currently no dependency on Core V3, but Actions may need to be discussed once there is some clarity on the approach. We will call it V.next for now.
• Drafting of new specification version
  • Automation Template Scenarios. Umberto Caselli will update the scenario page with the specific approach to take
  • Automation Plan Execution Environment. Approach is documented on the scenario page and ready to incorporate.
  • Temporary deployment scenarios. Martin Pain will own documenting specific proposed changes. There are some on-going discussions around Actions which Martin and John Arwe will bring to the workgroup.
• Workgroup business
  • For the remainder of V.next Umberto Caselli and Martin Pain will chair the workgroup. Michael Fiedler will create the initial draft and transition it once it is ready for others to add/update content.