Richard, On Thu, May 7, 2009 at 10:01 AM, Richard Davies <richard@daviesmail.org> wrote:
When the group was set up, I understood that our aim was to quickly write down and agree the common core between existing IaaS APIs: Amazon, Sun, GoGrid, ElasticHosts, etc.
We've done some work in that direction (the nouns, verbs and attributes),
And this is good.
but have also proposed a lot which would be going beyond what any/most IaaSes have actually implemented to date.
For example: embedding of OVF, proposed extensions such as a search service, billing and reporting.
The OVF thing is partly to do with our charter. But I am not convinced as to the right course of action *today*. You could just knock out a codegen to map OVF to JSON ;-)
We shouldn't be working on these - we should stick to 3 nouns, ~15 verbs, ~15 attributes (of which we have a good draft) and should wrap these in the simplest possible wire format (e.g. fix actuator URLs for each verb. Represent nouns as a single level JSON hash listing the attributes as key-value pairs).
See the ElasticHosts application/json format at http://www.elastichosts.com/products/api for how simple this can be (or equivalently GoGrid, Sun, etc. - though I believe that Sun's JSON has unnecessarily deep data structures).
Then we should declare victory and go home!
I assume you have a flight suit to hand ;-) a
Richard. _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg