[Capi-bof] Charter Status...

[Taka Matsutsuka]

Hi Andy,

Cloud is a vague notion, but now let's assume it is layered architecture,
consists of IaaS/PaaS/SaaS, following the charter.

If we assume PaaS is in the middle, it offeres a set of API for a layer
above (SaaS in this case).  At the same time, PaaS requires a set of
capability from the lower layer (i.e. IaaS).  This capability is what
I meant SPI.

The charter states that the focus is "API for interfacing IaaS," which seems
fairly low level to me.  In this sense, I don't think we need SPI for IaaS
either.

-- Taka

In subject "RE: [Capi-bof] Charter Status...",
 "Edmonds, AndrewX" <andrewx.edmonds at intel.com> wrote:
> Abstractly, I would imagine that as we are only dealing with the interface to a service that provides infrastructure, a SPI in that context is equivocal but a more generic term. In this sense I could have a collection of SPIs, some of which are PaaS, SaaS and others that are complimenting services such as a networking service that is used only within IaaS. If you are referring to SPI in this collection [1] and if it is one of these, bar [2], then I'd say it's too low level to embed its semantics in the OCCI. In that case the idea is a sound and valid one as OCCI only sets out to define an interface to infrastructure and the supporting schema, not the implementation of such a service.
> 
> Andy