The Automation meetings alternate times each meeting to accomodate the global team.

Agenda

* Reoccurring agenda items:

• Recap of previous meeting AutomationMeetings20111110

• • Report to workgroup on artifact discussion (Automation Request/Result vs single AutomationJob? )
  • DavidBrauneis, CharlesRankin, LucasPanjer and MichaelFiedler met to discuss
  • Summary
    • Some existing implementations represent the concepts with 1 artifact, some with 2
    • 2 artifacts provides the most flexibility
    • implementations with only 1 artifact internally can represent the information in that artifact as 2 separate OSLC artifacts, the request and result.
    • keep the request as simple as possible. Minimal info to request an automation:
      • state
      • desired state (for cancel)
      • input parameters required for automation execution
      • link to result (when it becomes available)
      • link to automation plan
      • requester
      • time requested
      • possibly "how requested" (manual, scheduled, programmatically)
    • originally, discussed this being transient. Now recommended persistent. Implementation may expose info available in 1..n places as 2 OSLC artifacts.
• Discuss Agent/Worker sub-scenario.
  • Proposal to limit scenario to optional agent registration
  • Value of a limited scenario
• If there is time, discuss result contributions. See ResourceDefinitions.
• Plans for moving from scenario development to spec development
• Previous Action Items:
  • NA
• Next meetings:
  • Discuss meeting time
  • 1 December

Minutes