I've shared a document with you called "OCCI-WG Conference Call 2009-04-22":
http://docs.google.com/Doc?id=ddqm27m2_291zwgn28ht&invite=501063204

It's not an attachment -- it's stored online at Google Docs. To open this document, just click the link above.
---

Thanks to everyone who as able to make it for a good (1hr) call today.

I have prepared some notes covering most of the topics that were raised which are temporarily in a Google doc so you can add your own notes before we migrate to the wiki.

Generally we are very happy with the progress made over a very short period and the most important result of the discussion was a timeline leading up to OGF26 at the end of next month (by which time we will have an implementable draft).

Sam


OCCI-WG Conference Call 2009-04-22
OCCI-WG Conference Call 2009-04-22

Note: Future conference calls to be held at 08h00 PDT / 17h00 CEST (see meeting planner)

  1. Schedule
    1. OGF 26
      1. First draft of the API to be delivered along with a presentation (ideally directly from the wiki so as to familiarise potential participants)
      2. Two slots requested - one for presentation (marketing moreso than technical - with slides) and one for discussion/feedback
    2. OGF 27
      1. Final specification in "static" format
    3. Future
      1. Ongoing enhancement by way of registries (following concsensus on the mailing list) and extension development (e.g. firewall management)
  2. Progress
    1. Charter
      1. Done and approved.
    2. Use Cases
      1. Please take a look at the use case pages and update it if necessary
      2. IL to mail requesting more use cases - better to get input now than later
    3. Infrastructure
      1. Wiki, web site, logo, etc. done by committee offline
    4. API Design
      1. Good progress made already - this will be the basis of the implementable draft
  3. Agreements
    1. States
      1. We have the essential states that we need now
      2. Add states as we need them via registries
      3. This approach should give sufficient flexibility
      4. Keep state diagram very simple (with comment about error state being universally applicable)
    2. Verbs
      1. Compute / Network / Storage (with subtypes for e.g. physical/virtual machines and networks, drives and snapshots, etc.)
      2. IP addresses, VLANs, etc. (IDs inside networks is ok for EH - details need to be codified and ratified)
      3. High level agreement / consensus on most issues - little contention
  4. Draft
    1. No action required beyond developing information in the wiki
    2. Taxonomy/Ontology to be defined by end April (already mostly complete)
    3. Formats to be defined by mid May (work and discussion underway)
    4. Feedback to be solicited internally and externally in the latter two weeks of may respectively
  5. Todo
    1. Formats
    2. Documentation
      1. TM to advise on documentation requirements for OGF
      2. SJ has DocBook templates underway
    3. Other issues potentially in scope?
      1. Network management API (basic)
      2. Storage management API (basic)
      3. Security functionality (basic)
  1. Deadlines