HistoryViewLinks to this page 2013 May 14 | 09:55 pm

Time: 11:00AM Eastern US (contact MichaelFiedler if you’d like to participate)

Agenda

Minutes

Attending: Michael Fiedler, Martin Pain, Paul McMahan, Heather Fraser-Dube, David Liu, Subhajit Bhuiya, Umberto Caselli, Deepa Doraswamy, Vaibhav Srivastava, Jing Qian, Rohit Shetty, Scarlett Li

  • No new V2 issues
  • Implementation updates
    • Vaibhav reported interest from a systems integrator in India in creating OSLC Automation integrations with IBM Rational Quality Manager and will keep the workgroup updated
  • Automation V3 scenarios
    • Paul McMahan provided a walkthrough of the AutomationPlan ExecutionEnvironment scenarios
      • Proposal to define a relationship from an Automation Plan to an Execution Environment resource
      • one scenario is centered around an Automation Plan author (example: test architect) defining the required environments to execute in
      • second scenario centered around an Automation Plan author using existing external environments (e.g. cloud resources) and incorporating them in to the design of an Automation Plan
      • third scenario is execution oriented - creating Automation Requests for a particular Execution Environment and running the automation in/against/on it
      • Discussion items:
        • Scenarios, as written, are test centric. But could apply to other domains. Example: builds of native code requiring specific build engines or environments
        • How to plan Parameters not satisfy the scenario? In the most basic sense the do. Parameters, as instances of OSLC Properties, could be used for anything. But, it is useful to have more narrow definitions of resources and resource types. Helps consumers.
        • Touch points with the Temporary deployment scenarios discussed. Execution time and possible resource linking intersections.
        • Umberto mentioned the automation product he works on has a similar concept - variable table representing parameters and runtime environments
      • Follow up: Additional discussion when some other workgroup members unable to attend can participate.
    • Vaibhav Srivastava provided a re-cap of the Automation agent/worker scenarios.
      • Basic walkthrough of the interactions between a worker and the provider.
      • Umberto mentioned that his automation product has similar interactions between the provider and workers
      • Follow up: Vaibhav & team will update the scenarios for V3 and further discussion
  • Future topics
    • Orchestration
    • Automation templates
    • Further discussion on Execution Environments and Agent scenarios
    • Re-visit Temporary deployment scenarios
  • Next meeting: May 9th (cancelled) and May 16th