[Capi-bof] Charter for Open Cloud Computing Interface (OCCI) Working Group

[Sam Johnston]

On Wed, Mar 25, 2009 at 4:53 PM, Thijs Metsch <Thijs.Metsch at sun.com> wrote:

>
> Sam,
>
> It is not really about the timeline - I know we need to do it fast but
> the amount and the documents are important. Therefor I want a discussion
> on next OGf on this issue, specially see if we can get a first draft by
> then.
>

Ok so we should really be locking down deliverables in the charter rather
than talking about them at the first meeting (when we really want to be
delivering something). So far you have suggested:

   1. First draft of an API
   2. Document describing use cases and giving an overview of the current
   state of art
   3. Document defining entities to be managed, their life-cycle and the
   associated
   processes to manage the life-cycle
   4. Standardised API
   5. Final version of an API

I have listed 5 common use cases in the revised charter (with concise
descriptions) and boiled the deliverable down to a single API Technical
Specification document.

I considered adding a user guide and implementor handbook but figure both
can be rolled into the API document (e.g. simple 'curl/wget' examples,
sample wire traces, etc.). Any other deliverables would want to be well
justified as they will slow us down.

Sam


>
> On Wed, 2009-03-25 at 16:50 +0100, Sam Johnston wrote:
> > On Wed, Mar 25, 2009 at 1:00 PM, Thijs Metsch <Thijs.Metsch at sun.com>
> > wrote:
> >
> >         Hi,
> >
> >         Thanks for your efforts!
> >
> >         Next to the issue from Ignacio I want to point out: we also
> >         need the
> >         deliverables and the timeline fixed (liked it better as it
> >         was, stating
> >         to have 3 documents). I'm not quite sure about the licensing
> >         issues as
> >         well - We might need to swap them out. Next to that the
> >         questions
> >         section might need some reformulation.
> >
> > Regarding the deliverables your Final API is scheduled for OGF31 which
> > is itself unscheduled. With OGF25 in March, OGF26 in May and OGF27 in
> > October, at this rate we won't be delivering it until end 2010 or
> > start 2011!
> >
> > I would say that October this year for an implementable API is already
> > pushing it, and that ideally we should have an implementable draft by
> > May (if we don't you can be sure other groups will or a proprietary
> > API will be adopted). We are, after all, more looking at the consensus
> > of existing APIs rather than building one from the ground up, and the
> > result will be as concise as possible, not some WS-* type affair.
> >
> > Sam
> >
> >
> >         Cheers,
> >
> >         -Thijs
> >
> >
> >
> >         On Wed, 2009-03-25 at 12:50 +0100, Ignacio Martin Llorente
> >         wrote:
> >         > Hi,
> >         >
> >         > Two questions:
> >         >
> >         > - "Workload" could be confusing, there are other WGs working
> >         on "job
> >         > workloads", for example SAGA or DRMAA, we could say "IaaS
> >         based
> >         > services"
> >         > - I understand that the API will manage (create, cancel,
> >         shutdown,
> >         > pool...) the life-cycle of the "entities" offered by IaaS
> >         clouds,
> >         > where entity could mean Virtual Machine, and potentially
> >         slide and
> >         > physical resource. Why have you added the management of the
> >         container?
> >         >
> >         > Regards
> >         >
> >         > --
> >         > Ignacio M. Llorente, Full Professor (Catedratico): web
> >         http://dsa-research.org/llorente
> >         >   and blog http://imllorente.dsa-research.org/
> >         > DSA Research Group:  web http://dsa-research.org and blog
> >         http://blog.dsa-research.org
> >         > Globus GridWay Metascheduler: http://www.GridWay.org
> >         > OpenNebula Virtual Infrastructure Engine:
> >         http://www.OpenNebula.org
> >         >
> >         >
> >         >
> >         >
> >         >
> >         >
> >         >
> >         >
> >         >
> >         > On 25/03/2009, at 12:27, samj at samj.net wrote:
> >         >
> >         > >
> >         > > > If this is not what we want please send an update
> >         version of your
> >         > > text
> >         > > with your ideas.
> >         > >
> >         > > Please find attached an updated PDF version of the charter
> >         which I
> >         > > hope will satisfy all parties.
> >         > >
> >         > > Kind regards,
> >         > >
> >         > > Sam
> >         > >
> >         > > <Charter for Open Cloud Computing Interface
> >         > >
> >         (OCCI) .pdf>_______________________________________________
> >         > > Capi-bof mailing list
> >         > > Capi-bof at ogf.org
> >         > > http://www.ogf.org/mailman/listinfo/capi-bof
> >         >
> >         > _______________________________________________
> >         > Capi-bof mailing list
> >         > Capi-bof at ogf.org
> >         > http://www.ogf.org/mailman/listinfo/capi-bof
> >
> >         --
> >         Thijs Metsch                        Tel: +49 (0)941 3075-122
> >         (x60122)
> >         http://blogs.sun.com/intheclouds
> >         Software Engineer Grid Computing
> >         Sun Microsystems GmbH
> >         Dr.-Leo-Ritter-Str. 7
> >         mailto:thijs.metsch at sun.com
> >         D-93049 Regensburg                  http://www.sun.com
> >
> >
> > _______________________________________________
> > Capi-bof mailing list
> > Capi-bof at ogf.org
> > http://www.ogf.org/mailman/listinfo/capi-bof
> --
> Thijs Metsch                        Tel: +49 (0)941 3075-122 (x60122)
> http://blogs.sun.com/intheclouds
> Software Engineer Grid Computing
> Sun Microsystems GmbH
> Dr.-Leo-Ritter-Str. 7               mailto:thijs.metsch at sun.com
> D-93049 Regensburg                  http://www.sun.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/capi-bof/attachments/20090325/067759a5/attachment.html