[occi-wg] OCCI Latest Draft
Randy Bias
randyb at neotactics.com
Tue Jul 7 13:48:31 CDT 2009
I think that object storage is out of scope IMHO. It deserves a
separate API.
--Randy
On Jul 6, 2009, at 10:13 PM, Adrian Cole wrote:
> Hi, Sam.
>
> Very clear document. Thanks for getting this together.
>
> I noticed that the storage noun is related to mountable storage.
> Forgive me, if I missed the discussion. What is the status of
> object storage (ex. Amazon S3)? I'm currently working on cloud
> object storage interop in jclouds. I'd expect something like the
> following, if we aren't deferring this service to extensions:
>
> Object Storage
>
> An object storage resource is capable of mass, and potentially
> limitless storage of key, value pairs.
>
> Table 3. Storage Attributes
>
> Attribute Type Description
> occi.objectstorage.public Boolean (true,false)
> Expose objects without access controls
> occi.objectstorage.cname String cname that identifies global namespace
>
> What are your thoughts?
>
> Regards,
> -Adrian
>
> jclouds
> http://code.google.com/p/jclouds
> http://anyweight.blogspot.com/
>
> On Tue, Jul 7, 2009 at 5:25 AM, Sam Johnston <samj at samj.net> wrote:
> Morning all,
>
> I've been doing some more work on the draft over the weekend and
> today as I hope to have it in good condition in time for the various
> cloud interop events next week. It's finally starting to take shape
> now that extensions (e.g. state machines), attributes and registries
> (e.g. HTTP status codes) have been added, even if they're a long way
> from finished.
>
> The OCCI Core profile is generic and can be used with any resource,
> while OCCI Infrastructure defines compute, network and storage nouns
> (with attributes that are designed to be both extensible and
> trivially mapped to txt, json and xml formats) as well as extensions
> for relevant functionality like state machines.
>
> Anyway the GridForge subversion repository just blew up and my local
> version doesn't build any more so given it's after 4am already I'm
> going to call it a day and send what I have so far by mail
> (attached). The master's DocBook v5 but there's HTML, XML-FO and PDF
> renderings too... I'll fix the subversion repository tomorrow so
> others can get in on the action.
>
> If you do plan to contribute though, please bear in mind that I am
> making personal contributions available under CC-BY-SA in addition
> to the standard OGF terms which I consider far too restrictive. I'd
> very much rather other editors follow my example so as the spec is
> not inextricably bound to any single organisation, as is customary
> for other cloud APIs (e.g. GoGrid, Sun Cloud API).
>
> Thanks,
>
> Sam
>
>
> _______________________________________________
> occi-wg mailing list
> occi-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/occi-wg
>
>
> _______________________________________________
> occi-wg mailing list
> occi-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/occi-wg
Randy Bias, Cloud Strategist
+1 (415) 939-8507 [m], randyb at neotactics.com
BLOG: http://cloudscaling.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/occi-wg/attachments/20090707/c6ea2ccf/attachment.html
More information about the occi-wg
mailing list