Hi Carlos, 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 to users for DC to be CIMI -only?
Are you assuming it will take a long time for the members to release their respective CIMI implementations (as it took them a long time to publish the standard) and DC's objective should be to bridge that period? Regards, Dies Koper > -----Original Message----- > From: Carlos Gonçalves [mailto:[email protected]] > Sent: Thursday, 3 May 2012 8:48 PM > To: [email protected] > Subject: DeltaCloud API and CIMI > > Dear all, > > 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 foresee > complex and perhaps political answers due to the nature of the topic. > > Currently DeltaCloud supports two APIs: its own API and CIMI API. They are > not interoperable between them, and neither have been standardized yet. > CIMI is just a step away from being officially released as a first 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. > > Until very recently I though CIMI support on DeltaCloud was somewhat a > trivial and an "automagically" translation from/to DeltaCloud API but 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. > > I believe the possible move to CIMI-only would bump the project visibility > but would require a major code rewritten, I suppose. > > So, thoughts on this? :-) > > Regards, > Carlos Goncalves >
