http://www.servicemesh.com/cloud-it-resources/cloud-strategy-transform-it-b log/blog/apache-cloudstack-aws-for-every-man/
Forgot the link! Sorry. On 10/14/13 2:14 PM, "La Motta, David" <david.lamo...@netapp.com> wrote: >Hello, folks. In reading this article (), I found this: > >"Interestingly, Apache CloudStack will follow a dual-API strategy. First, >the project will maintain compatibility with the familiar AWS API, which >allows users to leverage tool sets built to work with AWS. Love it or hate >it, the AWS API is rapidly becoming the lingua franca of the cloud world. >The AWS API has limitations, however, and so the Apache CloudStack project >will also expose advanced functionality that is not covered by the AWS API >through a parallel CloudStack API. Users can choose whichever API is most >convenient and even use both for different reasons at the same time." > >Šwhich is great. Is this still valid? How can I differentiate between >one type of API or another? > >The question comes from the use case of having CloudStack on-premise, then >later migrating to AWS, but keeping the same APIs. In other words, the >use case is to make use of the AWS API flavor so migration from on-premise >to Amazon is transparent. > >Could somebody shed some light in this department? > >Thanks! > > >David La Motta >Technical Marketing Engineer - Citrix Solutions | NetApp >Direct: 1.919.476.5042 >
