I have seen the standard API adoption in the past look something like:
1) Proxy pattern that normalizes underlying interface - made available
but maybe not as a supported interface for the shipping offering.
Customers can use this to normalize across multiple clouds.`
2) Side-by-side interface that is an additional supported interface in
addition to that used by the installed base of customers. Customers will
start using this over the proxy for specific features that are offered
as extensions to the standard, but are not available via the proxy.
3) Exclusive Standard interface (with small vendor extensions) as
customers require and only use this.
Adoption tends to proceed 1) -> 2) -> 3) for the early adopters, but as
adoption expands, companies will jump straight to 2) or 3) as they enter
the market.
If a de facto API emerges (perhaps EC2/S3) offerings may be required to
support both the de facto and de jure interfaces by customers (i.e. NFS
and CIFS/SMB).
--mark
On 5/14/13 8:58 AM, mar...@redhat.com wrote:
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.
