On Wed, May 13, 2009 at 6:21 PM, Richard Davies < richard.davies@elastichosts.com> wrote:
I am preparing a proposal for OCCI-API 1.0 that I will distribute when ready. I would like the first specification to be a simplification of previous discussions on the list in order to achieve an agreement on the core functionality to be provided by the API. In particular, the only "noun" would be the VM.
As we said on the call, I don't think the API is usable until it has servers, storage and network, so I think this can't be OCCI-API 1.0.
For many (perhaps yourselves included) it's not implementable until it's got billing... others might require performance monitoring and SLAs too. Everyone needs comute, network and storage though and OCCI 1.0 would be essentially useless without it. This is yet another reason to keep the core as compact as possible (ideally without reference to infrastructure at all) and do everything as modules - following the open source community's mantra: "release early, release often". I know this approach is trivial with AtomPub (it's what I've relied on to get so far so fast) but I'm not sure how easy it would be otherwise (namespaces really do help here). It's also a good reason not to try to go through the traditional process of getting a complete module in place and then blatting it out onto the wire... incremental, ongoing and ideally parallel development is going to work best for us. Sam