Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@deltacloud.apache.org
Received-SPF: pass (nike.apache.org: domain of dug@us.ibm.com designates
 32.97.110.159 as permitted sender)
In-Reply-To: <95C8CDD9-7A4F-430D-B08E-9008E4C7C013@cgoncalves.info>
To: dev@deltacloud.apache.org
MIME-Version: 1.0
Subject: Re: DeltaCloud API and CIMI
From: Doug Davis <dug@us.ibm.com>
Message-ID: 
 <OF68C8ACEF.365B13BC-ON852579F3.005D32B8-852579F3.005D3EF5@us.ibm.com>
Date: Thu, 3 May 2012 12:58:29 -0400
Content-Type: multipart/alternative;
 boundary="=_alternative 005D3D1D852579F3_="

--=_alternative 005D3D1D852579F3_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<de-lurking>  https://blueprints.launchpad.net/nova/+spec/cimi=20
</de-lurking>

Just FYI.

thanks
-Doug
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.


Carlos Gon=E7alves <mail@cgoncalves.info>=20
05/03/2012 12:32 PM
Please respond to
dev@deltacloud.apache.org


To
dev@deltacloud.apache.org
cc

Subject
Re: DeltaCloud API and CIMI


Hi Dies,

I did not mean the API between IaaS providers and DeltaCloud because I=20
don't see providers such as Amazon EC2 supporting CIMI at least in the=20
sort run, but the API DeltaCloud users use to communicate with DeltaCloud=20
abstracting themselves from each IaaS provider own API.

If CIMI gets really spread I guess some IaaS software projects,=20
open-source mainly, will start supporting CIMI, either as their only=20
available API or as an secondary API. For instance, there is a working=20
group adding OCCI support on OpenStack[1]. While some providers may opt to =

offer a standard cloud API (OCCI or CIMI) to their services, others just=20
won't because that would somehow mean easing interoperability with=20
competitor cloud vendors, giving up of their vendor lock-in strategy and=20
hence loosing money - that's my point of view :-)

So, no, I don't see DeltaCloud getting obsolete, ever (?).

Hope I've answered all your questions. If not, please let me know and I'll =

rephrase.

Thanks,
Carlos Goncalves

[1] http://occi-wg.org/2012/02/14/occi-in-openstack/

On 3 May 2012, at 14:14, Koper, Dies wrote:

> Hi Carlos,
>=20
> I wonder how many cloud providers will support the CIMI API.
> If all DMTF members will support it, wouldn't that render DC obsolete?
> If few DMTF members will actually support it, what is the real benefit=20
to users for DC to be CIMI -only?
>=20
> Are you assuming it will take a long time for the members to release=20
their respective CIMI implementations (as it took them a long time to=20
publish the standard) and DC's objective should be to bridge that period?
>=20
> Regards,
> Dies Koper
>=20
>=20
>> -----Original Message-----
>> From: Carlos Gon=E7alves [mailto:mail@cgoncalves.info]
>> Sent: Thursday, 3 May 2012 8:48 PM
>> To: dev@deltacloud.apache.org
>> Subject: DeltaCloud API and CIMI
>>=20
>> Dear all,
>>=20
>> As suggested by Marios on IRC the other day, I'm opening here a new
>> thread for max discussion on the subject of the future of DeltaCloud in
>> terms of APIs available to the user. The question is short, though I=20
foresee
>> complex and perhaps political answers due to the nature of the topic.
>>=20
>> Currently DeltaCloud supports two APIs: its own API and CIMI API. They=20
are
>> not interoperable between them, and neither have been standardized yet.
>> CIMI is just a step away from being officially released as a first=20
final version
>> (1.0.0) cloud standard by DMTF, where DeltaCloud API has not yet even
>> been proposed to be one as far as I know.
>>=20
>> Until very recently I though CIMI support on DeltaCloud was somewhat a
>> trivial and an "automagically" translation from/to DeltaCloud API but=20
I've
>> been proven to mistaken when I gave Marios' new OpenStack v2 driver a
>> spin using CIMI. This led me to question of whether DeltaCloud should
>> support both APIs or just focus on just one, with CIMI being the most
>> logical model and interface to be adopted rather DeltaCloud's own.
>>=20
>> I believe the possible move to CIMI-only would bump the project=20
visibility
>> but would require a major code rewritten, I suppose.
>>=20
>> So, thoughts on this? :-)
>>=20
>> Regards,
>> Carlos Goncalves
>>=20
>=20
>=20


--=_alternative 005D3D1D852579F3_=--