On 14/05/13 17:08, Mingyu Li wrote: > As the CIMI standard will be adopted by more and more cloud service > providers, the clouds would provide uniform APIs.
right - but that's a BIG if, as well as a WHEN... I don't see providers having much incentive to provide CIMI at the moment. Perhaps once adoption is greater this will increase the pressure on those providers. But I still don't see AWS being pressured into changing their API any time soon. And then there is no need > to use Deltacloud or Sirocco or any other similar software working as an > API gateway. So, I think, these projects are all transitional. right, in the fullness of time, perhaps (as above). However Deltacloud also supports "private cloud", i.e. virt solutions like RHEV-M and VSphere which you want to expose as an internal private cloud. marios > > > 2013/5/14 DANG TRAN Frederic <frederic.dangt...@orange.com> > >> FYI the Sirocco project is backed by France Telecom-Orange and was tested >> during the last CIMI plugfest against Deltacloud. >> >> Regards, >> Frederic Dang Tran >> Orange Labs >> >> >> On May 14, 2013, at 2:58 PM, Chip Childers wrote: >> >>> On Tue, May 14, 2013 at 12:11:28PM +0300, mar...@redhat.com wrote: >>>>> >>>>> What is your view on existing libraries as jcloud and libcloud? Do you >> see it as important that CIMI gets added to these? >>>>> >>>> >>>> Absolutely! Right now I am not aware of any other project that offers >>>> CIMI API support. An important aspect of a new specification like CIMI >>>> gaining traction and acceptance is obviously wide >>>> implementation/adoption/availability >>> >>> FWIW, there is one other CIMI implementation that I know of. Sirocco. >>> >>> Java client is here: >>> >>> http://sirocco.projects.ow2.org/xwiki/bin/view/Components/cimiclient >>> >>> And the server side implementation is here: >>> >>> http://sirocco.projects.ow2.org/xwiki/bin/view/Main/WebHome >>> >>> I have not used or reviewed it in detail, so no clue how "done" it is. >> >> >
