Hello,

EC2 compatibility is an essential feature for potential ACS adopters. 
What alternatives are there for the AWSAPI component?

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "pyr" <g...@git.apache.org>
> To: dev@cloudstack.apache.org
> Sent: Friday, 21 November, 2014 10:18:58
> Subject: [GitHub] cloudstack pull request: Remove AWS api bridge

> GitHub user pyr opened a pull request:
> 
>    https://github.com/apache/cloudstack/pull/44
> 
>    Remove AWS api bridge
> 
>    This has been a discussion point for a while. The (mostly generated)
>    code for the AWS api bridge is by far the largest source component in
>    Cloudstack, while seldomly used.
>    
>    Now that alternate options exist to provide EC2 compatibility, it
>    makes sense to remove it for the few users who cannot directly
>    talk to the cloudstack API.
> 
> You can merge this pull request into a Git repository by running:
> 
>    $ git pull https://github.com/pyr/cloudstack feature/no-dead-code
> 
> Alternatively you can review and apply these changes as the patch at:
> 
>    https://github.com/apache/cloudstack/pull/44.patch
> 
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
> 
>    This closes #44
>    
> ----
> commit 84042f2c3259203b1ea1956cd239b9122079bae9
> Author: Pierre-Yves Ritschard <p...@spootnik.org>
> Date:   2014-11-21T10:17:18Z
> 
>    Remove AWS api bridge
>    
>    This has been a discussion point for a while. The (mostly generated)
>    code for the AWS api bridge is by far the largest source component in
>    Cloudstack, while seldomly used.
>    
>    Now that alternate options exist to provide EC2 compatibility, it
>    makes sense to remove it for the few users who cannot directly
>    talk to the cloudstack API.
> 
> ----
> 
> 
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---

Reply via email to