[occi-wg] Quick OCCI Update
garymazzaferro at gmail.com
Mon Jun 8 14:05:16 CDT 2009
The issue was any document or external link I added to the wiki required
the person viewing the doc or link to be logged in. Andy just reset my
permission, I'll check it later.
Andre Merzky wrote:
> Hi Gary,
> what is your problem with the wiki? Your GridForge account
> has Member and Author permissions on the project, which
> should allow any action on the wiki.
> Best, Andre.
> Quoting [Gary Mazz] (Jun 08 2009):
>> Date: Mon, 08 Jun 2009 12:16:10 -0600
>> From: Gary Mazz <garymazzaferro at gmail.com>
>> To: "occi-wg at ogf.org" <occi-wg at ogf.org>
>> Subject: Re: [occi-wg] Quick OCCI Update
>> Before anyone hops on the snia bandwagon as an advocate, we need to
>> assess the "level" in cloud architecture that the snai api addresses. We
>> need to ask the question is their api an IaaS level api or focuses at
>> some other level. Or have we relegated ourselves to throwing everything
>> we can find in a rubbish heap ?
>> Incorrectly positioning functions and features can/will adversely affect
>> success of the IaaS interoperability specification and the
>> implementability of the OCCI IaaS api.
>> I have included a diagram with a proposed division of responsibilities
>> for each cloud layer.
>> If someone would like to add it the to wiki for comment, it would be
>> appreciated. ( my occi wiki permissions aren't quite right)
>> Comments welcome, as aways.
>> Sam Johnston wrote:
>>> Afternoon all,
>>> Over the last few weeks I've been busy evangelising OCCI at various
>>> cloud computing events througout Europe:
>>> * Cloud Computing Expo - Prague (18, 19 May 2009)
>>> * Cloud Computing Expo - London (20, 21 May 2009)
>>> * Cloud Views Conference - Porto (28, 29 May 2009)
>>> In addition to doing the Introduction to the Open Cloud Computing
>>> Interface (OCCI)
>>> presentation I had the opportunity to sit on panels at the events and
>>> to introduce "Interoperability" as the topic for Cloud Views 2010. It
>>> was great to meet many of you and to have various opportunities to
>>> discuss (often at length) the API - some great feedback was given and
>>> good progress made on working towards consensus. We've found ways to
>>> evict Atom from individual resources and adopt a simple key/value
>>> descriptor format for a start which should make some of you very happy.
>>> I also spent 90 minutes running through and discussing OCCI with the
>>> SNIA Cloud TWG at their last meeting (last week) which I think is a
>>> great opportunity for us to ensure that our respective standards are
>>> at least somewhat compatible and avoid a rerun of WS-* (I would hope
>>> for example that we can use an SNIA descriptor format to define
>>> non-trivial storage resources). Thijs is busy formalising this
>>> arrangement and a similar one with the DMTF and I encourage those of
>>> you who are interested in these projects to join them so we can get
>>> some cross-pollination going on (especially those of you employed by
>>> member companies - neither group is as open as we are).
>>> Anyway I'm back this week after my partner's surgery and between
>>> looking after her while she recovers over the course of the month I'm
>>> hoping we can make some good progress quickly. It's in all of our
>>> interests to deliver while we still have an opportunity to be relevant
>>> as the last thing we want is to end up playing follow the leader
>>> (regardless of whether the leader happens to be VMware via DMTF or
>>> Amazon with an "open" EC2).
>>> occi-wg mailing list
>>> occi-wg at ogf.org
>> occi-wg mailing list
>> occi-wg at ogf.org
More information about the occi-wg