You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by pyr <gi...@git.apache.org> on 2014/11/21 11:18:58 UTC
[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 <py...@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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Remove AWS api bridge
Posted by pyr <gi...@git.apache.org>.
Github user pyr commented on the pull request:
https://github.com/apache/cloudstack/pull/44#issuecomment-65030920
closing this since a new branch has been created by @runseb
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Remove AWS api bridge
Posted by runseb <gi...@git.apache.org>.
Github user runseb commented on the pull request:
https://github.com/apache/cloudstack/pull/44#issuecomment-64176274
I just committed this to a new noawsapi branch:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/noawsapi
we should fix the rpm build on that branch, test upgrades etc…
If folks agree we can merge it in master for 4.6
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Remove AWS api bridge
Posted by runseb <gi...@git.apache.org>.
Github user runseb commented on the pull request:
https://github.com/apache/cloudstack/pull/44#issuecomment-63965999
This is green on travis, so let's discuss on the list. I am asking asf infra to create a cloudstack-awsapi repo.
One alternative is https://github.com/BroganD1993/ec2stack/commits/master but it will need more work.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Remove AWS api bridge
Posted by pyr <gi...@git.apache.org>.
Github user pyr closed the pull request at:
https://github.com/apache/cloudstack/pull/44
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Remove AWS api bridge
Posted by resmo <gi...@git.apache.org>.
Github user resmo commented on the pull request:
https://github.com/apache/cloudstack/pull/44#issuecomment-64081042
:+1:
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
Re: [GitHub] cloudstack pull request: Remove AWS api bridge
Posted by Darren Brogan <br...@darrenbrogan.ie>.
Hi all,
I was involved in the development of ec2stack and gstack. I'm completely
fine with both projects being donated.
Darren
On Sat, Nov 22, 2014 at 11:59 AM, Ian Duffy <ia...@ianduffy.ie> wrote:
> Hi Chip,
>
> Bringing Darren and Sebastien into this since they wrote some of it to.
>
> I'm totally OK with it being donated.
>
> On 22 November 2014 at 10:59, Chip Childers <ch...@apache.org>
> wrote:
>
>> Ian,
>>
>> Since that code was developed outside of the project, would you and
>> your compatriots be willing to donate it to the project officially?
>>
>> (Actually, same request for the GCE interface work)
>>
>> IMO, I'd love this for a couple of reasons:
>>
>> 1) it's newer code, and likely works better
>> 2) we should consider AWS (or GCE) API support to be non-core to the
>> project, but it's important to have that functionality available for
>> those that want it
>> 3) if it's in the project officially, we can try build a community
>> around maintaining it beyond current maintainers
>> 4) (and this is a general thought that I haven't fully formed) - we
>> need to find ways to focus on solidifying the "core" of CloudStack so
>> that it's rock solid and exceptionally fast to get started with
>> (faster than we are today). Features that are outside of the core
>> should be add-ons to the core (like AWS API support)
>>
>> My 2 cents..
>>
>>
>> On Fri, Nov 21, 2014 at 3:50 PM, Ian Duffy <ia...@ianduffy.ie> wrote:
>> > +1 on ec2stack working well (bias view).
>> >
>> > I've used it via vagrant-aws, boto and eucalyptus eutester without
>> issue.
>> >
>> > It could use some documentation on deployment for production purposes,
>> the
>> > embedded webserver it exposes is OK but I'd feel safer with it bring
>> behind
>> > nginx/Apache.
>> > On 21 Nov 2014 14:31, "Hugo Trippaers" <hu...@trippaers.nl> wrote:
>> >
>> >> Let’s start by getting this on a feature branch.
>> >>
>> >> I would like to make sure that everything works before we remove the
>> code
>> >> and that includes deb and rpm packaging. We also need to think about
>> the
>> >> upgrade path. If a user is currently using awsapi, he needs an upgrade
>> path
>> >> the start using the replacement.
>> >>
>> >> Cheers,
>> >>
>> >> Hugo
>> >>
>> >> > On 21 nov. 2014, at 14:39, Sebastien Goasguen <ru...@gmail.com>
>> wrote:
>> >> >
>> >> >
>> >> > On Nov 21, 2014, at 8:33 AM, Nux! <nu...@li.nux.ro> wrote:
>> >> >
>> >> >> +1 what Daan said.
>> >> >>
>> >> >> Once ec2stack works well, then nuke awsapi.
>> >> >>
>> >> >
>> >> > it works well.
>> >> >
>> >> > where can we see test about awsapi ?
>> >> >
>> >> >> my 2 pence
>> >> >>
>> >> >> --
>> >> >> Sent from the Delta quadrant using Borg technology!
>> >> >>
>> >> >> Nux!
>> >> >> www.nux.ro
>> >> >>
>> >> >> ----- Original Message -----
>> >> >>> From: "Daan Hoogland" <da...@gmail.com>
>> >> >>> To: "dev" <de...@cloudstack.apache.org>
>> >> >>> Sent: Friday, 21 November, 2014 13:16:25
>> >> >>> Subject: Re: [GitHub] cloudstack pull request: Remove AWS api
>> bridge
>> >> >>
>> >> >>> As Seb mentioned on list there is an alternative. I don't think we
>> >> >>> should remove this before the factored out version is working as
>> well
>> >> >>> (or the alternative he mentions is at least as complete) The idea
>> of
>> >> >>> isolating this bit is appealing though.
>> >> >>>
>> >> >>> Daan
>> >> >>>
>> >> >>> On Fri, Nov 21, 2014 at 12:23 PM, Nux! <nu...@li.nux.ro> wrote:
>> >> >>>> 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" <gi...@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 <py...@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 infrastructure@apache.org or file a
>> JIRA
>> >> ticket
>> >> >>>>> with INFRA.
>> >> >>>>> ---
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> --
>> >> >>> Daan
>> >> >
>> >>
>> >>
>>
>
>
Re: [GitHub] cloudstack pull request: Remove AWS api bridge
Posted by Ian Duffy <ia...@ianduffy.ie>.
Hi Chip,
Bringing Darren and Sebastien into this since they wrote some of it to.
I'm totally OK with it being donated.
On 22 November 2014 at 10:59, Chip Childers <ch...@apache.org> wrote:
> Ian,
>
> Since that code was developed outside of the project, would you and
> your compatriots be willing to donate it to the project officially?
>
> (Actually, same request for the GCE interface work)
>
> IMO, I'd love this for a couple of reasons:
>
> 1) it's newer code, and likely works better
> 2) we should consider AWS (or GCE) API support to be non-core to the
> project, but it's important to have that functionality available for
> those that want it
> 3) if it's in the project officially, we can try build a community
> around maintaining it beyond current maintainers
> 4) (and this is a general thought that I haven't fully formed) - we
> need to find ways to focus on solidifying the "core" of CloudStack so
> that it's rock solid and exceptionally fast to get started with
> (faster than we are today). Features that are outside of the core
> should be add-ons to the core (like AWS API support)
>
> My 2 cents..
>
>
> On Fri, Nov 21, 2014 at 3:50 PM, Ian Duffy <ia...@ianduffy.ie> wrote:
> > +1 on ec2stack working well (bias view).
> >
> > I've used it via vagrant-aws, boto and eucalyptus eutester without issue.
> >
> > It could use some documentation on deployment for production purposes,
> the
> > embedded webserver it exposes is OK but I'd feel safer with it bring
> behind
> > nginx/Apache.
> > On 21 Nov 2014 14:31, "Hugo Trippaers" <hu...@trippaers.nl> wrote:
> >
> >> Let’s start by getting this on a feature branch.
> >>
> >> I would like to make sure that everything works before we remove the
> code
> >> and that includes deb and rpm packaging. We also need to think about the
> >> upgrade path. If a user is currently using awsapi, he needs an upgrade
> path
> >> the start using the replacement.
> >>
> >> Cheers,
> >>
> >> Hugo
> >>
> >> > On 21 nov. 2014, at 14:39, Sebastien Goasguen <ru...@gmail.com>
> wrote:
> >> >
> >> >
> >> > On Nov 21, 2014, at 8:33 AM, Nux! <nu...@li.nux.ro> wrote:
> >> >
> >> >> +1 what Daan said.
> >> >>
> >> >> Once ec2stack works well, then nuke awsapi.
> >> >>
> >> >
> >> > it works well.
> >> >
> >> > where can we see test about awsapi ?
> >> >
> >> >> my 2 pence
> >> >>
> >> >> --
> >> >> Sent from the Delta quadrant using Borg technology!
> >> >>
> >> >> Nux!
> >> >> www.nux.ro
> >> >>
> >> >> ----- Original Message -----
> >> >>> From: "Daan Hoogland" <da...@gmail.com>
> >> >>> To: "dev" <de...@cloudstack.apache.org>
> >> >>> Sent: Friday, 21 November, 2014 13:16:25
> >> >>> Subject: Re: [GitHub] cloudstack pull request: Remove AWS api bridge
> >> >>
> >> >>> As Seb mentioned on list there is an alternative. I don't think we
> >> >>> should remove this before the factored out version is working as
> well
> >> >>> (or the alternative he mentions is at least as complete) The idea of
> >> >>> isolating this bit is appealing though.
> >> >>>
> >> >>> Daan
> >> >>>
> >> >>> On Fri, Nov 21, 2014 at 12:23 PM, Nux! <nu...@li.nux.ro> wrote:
> >> >>>> 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" <gi...@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 <py...@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 infrastructure@apache.org or file a
> JIRA
> >> ticket
> >> >>>>> with INFRA.
> >> >>>>> ---
> >> >>>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> Daan
> >> >
> >>
> >>
>
Re: [GitHub] cloudstack pull request: Remove AWS api bridge
Posted by Chip Childers <ch...@apache.org>.
Additional point - IMO, if we do this we would manage both ec2bridge
and the GCE code as separate repos (just like how docs and cloudmonkey
are), so that they can be released independently. We'd also want to
package them with DEB and RPM so that they can be easily installed
alongside or on their own very easily.
On Sat, Nov 22, 2014 at 11:59 AM, Chip Childers <ch...@apache.org> wrote:
> Ian,
>
> Since that code was developed outside of the project, would you and
> your compatriots be willing to donate it to the project officially?
>
> (Actually, same request for the GCE interface work)
>
> IMO, I'd love this for a couple of reasons:
>
> 1) it's newer code, and likely works better
> 2) we should consider AWS (or GCE) API support to be non-core to the
> project, but it's important to have that functionality available for
> those that want it
> 3) if it's in the project officially, we can try build a community
> around maintaining it beyond current maintainers
> 4) (and this is a general thought that I haven't fully formed) - we
> need to find ways to focus on solidifying the "core" of CloudStack so
> that it's rock solid and exceptionally fast to get started with
> (faster than we are today). Features that are outside of the core
> should be add-ons to the core (like AWS API support)
>
> My 2 cents..
>
>
> On Fri, Nov 21, 2014 at 3:50 PM, Ian Duffy <ia...@ianduffy.ie> wrote:
>> +1 on ec2stack working well (bias view).
>>
>> I've used it via vagrant-aws, boto and eucalyptus eutester without issue.
>>
>> It could use some documentation on deployment for production purposes, the
>> embedded webserver it exposes is OK but I'd feel safer with it bring behind
>> nginx/Apache.
>> On 21 Nov 2014 14:31, "Hugo Trippaers" <hu...@trippaers.nl> wrote:
>>
>>> Let’s start by getting this on a feature branch.
>>>
>>> I would like to make sure that everything works before we remove the code
>>> and that includes deb and rpm packaging. We also need to think about the
>>> upgrade path. If a user is currently using awsapi, he needs an upgrade path
>>> the start using the replacement.
>>>
>>> Cheers,
>>>
>>> Hugo
>>>
>>> > On 21 nov. 2014, at 14:39, Sebastien Goasguen <ru...@gmail.com> wrote:
>>> >
>>> >
>>> > On Nov 21, 2014, at 8:33 AM, Nux! <nu...@li.nux.ro> wrote:
>>> >
>>> >> +1 what Daan said.
>>> >>
>>> >> Once ec2stack works well, then nuke awsapi.
>>> >>
>>> >
>>> > it works well.
>>> >
>>> > where can we see test about awsapi ?
>>> >
>>> >> my 2 pence
>>> >>
>>> >> --
>>> >> Sent from the Delta quadrant using Borg technology!
>>> >>
>>> >> Nux!
>>> >> www.nux.ro
>>> >>
>>> >> ----- Original Message -----
>>> >>> From: "Daan Hoogland" <da...@gmail.com>
>>> >>> To: "dev" <de...@cloudstack.apache.org>
>>> >>> Sent: Friday, 21 November, 2014 13:16:25
>>> >>> Subject: Re: [GitHub] cloudstack pull request: Remove AWS api bridge
>>> >>
>>> >>> As Seb mentioned on list there is an alternative. I don't think we
>>> >>> should remove this before the factored out version is working as well
>>> >>> (or the alternative he mentions is at least as complete) The idea of
>>> >>> isolating this bit is appealing though.
>>> >>>
>>> >>> Daan
>>> >>>
>>> >>> On Fri, Nov 21, 2014 at 12:23 PM, Nux! <nu...@li.nux.ro> wrote:
>>> >>>> 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" <gi...@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 <py...@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 infrastructure@apache.org or file a JIRA
>>> ticket
>>> >>>>> with INFRA.
>>> >>>>> ---
>>> >>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>> Daan
>>> >
>>>
>>>
Re: [GitHub] cloudstack pull request: Remove AWS api bridge
Posted by Chip Childers <ch...@apache.org>.
Ian,
Since that code was developed outside of the project, would you and
your compatriots be willing to donate it to the project officially?
(Actually, same request for the GCE interface work)
IMO, I'd love this for a couple of reasons:
1) it's newer code, and likely works better
2) we should consider AWS (or GCE) API support to be non-core to the
project, but it's important to have that functionality available for
those that want it
3) if it's in the project officially, we can try build a community
around maintaining it beyond current maintainers
4) (and this is a general thought that I haven't fully formed) - we
need to find ways to focus on solidifying the "core" of CloudStack so
that it's rock solid and exceptionally fast to get started with
(faster than we are today). Features that are outside of the core
should be add-ons to the core (like AWS API support)
My 2 cents..
On Fri, Nov 21, 2014 at 3:50 PM, Ian Duffy <ia...@ianduffy.ie> wrote:
> +1 on ec2stack working well (bias view).
>
> I've used it via vagrant-aws, boto and eucalyptus eutester without issue.
>
> It could use some documentation on deployment for production purposes, the
> embedded webserver it exposes is OK but I'd feel safer with it bring behind
> nginx/Apache.
> On 21 Nov 2014 14:31, "Hugo Trippaers" <hu...@trippaers.nl> wrote:
>
>> Let’s start by getting this on a feature branch.
>>
>> I would like to make sure that everything works before we remove the code
>> and that includes deb and rpm packaging. We also need to think about the
>> upgrade path. If a user is currently using awsapi, he needs an upgrade path
>> the start using the replacement.
>>
>> Cheers,
>>
>> Hugo
>>
>> > On 21 nov. 2014, at 14:39, Sebastien Goasguen <ru...@gmail.com> wrote:
>> >
>> >
>> > On Nov 21, 2014, at 8:33 AM, Nux! <nu...@li.nux.ro> wrote:
>> >
>> >> +1 what Daan said.
>> >>
>> >> Once ec2stack works well, then nuke awsapi.
>> >>
>> >
>> > it works well.
>> >
>> > where can we see test about awsapi ?
>> >
>> >> my 2 pence
>> >>
>> >> --
>> >> Sent from the Delta quadrant using Borg technology!
>> >>
>> >> Nux!
>> >> www.nux.ro
>> >>
>> >> ----- Original Message -----
>> >>> From: "Daan Hoogland" <da...@gmail.com>
>> >>> To: "dev" <de...@cloudstack.apache.org>
>> >>> Sent: Friday, 21 November, 2014 13:16:25
>> >>> Subject: Re: [GitHub] cloudstack pull request: Remove AWS api bridge
>> >>
>> >>> As Seb mentioned on list there is an alternative. I don't think we
>> >>> should remove this before the factored out version is working as well
>> >>> (or the alternative he mentions is at least as complete) The idea of
>> >>> isolating this bit is appealing though.
>> >>>
>> >>> Daan
>> >>>
>> >>> On Fri, Nov 21, 2014 at 12:23 PM, Nux! <nu...@li.nux.ro> wrote:
>> >>>> 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" <gi...@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 <py...@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 infrastructure@apache.org or file a JIRA
>> ticket
>> >>>>> with INFRA.
>> >>>>> ---
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Daan
>> >
>>
>>
Re: [GitHub] cloudstack pull request: Remove AWS api bridge
Posted by Pierre-Yves Ritschard <py...@spootnik.org>.
It would be interesting to have usage stats on the AWS cloud bridge.
It is very hard to get working right correctly (especially when compared to
something like ec2stack) so I'd be very surprised if:
- There were a large number of users
- They had upgrade path issues
I think the idea of chunking out awsapi in its own repo has some merit,
even though it will most likely ending up being bitrot.
As far as packaging is concerned, this PR still builds packages correctly
for debian, someone should do a test build for RPM packages (i did the spec
changes but didn't build).
On Fri, Nov 21, 2014 at 3:50 PM, Ian Duffy <ia...@ianduffy.ie> wrote:
> +1 on ec2stack working well (bias view).
>
> I've used it via vagrant-aws, boto and eucalyptus eutester without issue.
>
> It could use some documentation on deployment for production purposes, the
> embedded webserver it exposes is OK but I'd feel safer with it bring behind
> nginx/Apache.
> On 21 Nov 2014 14:31, "Hugo Trippaers" <hu...@trippaers.nl> wrote:
>
> > Let’s start by getting this on a feature branch.
> >
> > I would like to make sure that everything works before we remove the code
> > and that includes deb and rpm packaging. We also need to think about the
> > upgrade path. If a user is currently using awsapi, he needs an upgrade
> path
> > the start using the replacement.
> >
> > Cheers,
> >
> > Hugo
> >
> > > On 21 nov. 2014, at 14:39, Sebastien Goasguen <ru...@gmail.com>
> wrote:
> > >
> > >
> > > On Nov 21, 2014, at 8:33 AM, Nux! <nu...@li.nux.ro> wrote:
> > >
> > >> +1 what Daan said.
> > >>
> > >> Once ec2stack works well, then nuke awsapi.
> > >>
> > >
> > > it works well.
> > >
> > > where can we see test about awsapi ?
> > >
> > >> my 2 pence
> > >>
> > >> --
> > >> Sent from the Delta quadrant using Borg technology!
> > >>
> > >> Nux!
> > >> www.nux.ro
> > >>
> > >> ----- Original Message -----
> > >>> From: "Daan Hoogland" <da...@gmail.com>
> > >>> To: "dev" <de...@cloudstack.apache.org>
> > >>> Sent: Friday, 21 November, 2014 13:16:25
> > >>> Subject: Re: [GitHub] cloudstack pull request: Remove AWS api bridge
> > >>
> > >>> As Seb mentioned on list there is an alternative. I don't think we
> > >>> should remove this before the factored out version is working as well
> > >>> (or the alternative he mentions is at least as complete) The idea of
> > >>> isolating this bit is appealing though.
> > >>>
> > >>> Daan
> > >>>
> > >>> On Fri, Nov 21, 2014 at 12:23 PM, Nux! <nu...@li.nux.ro> wrote:
> > >>>> 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" <gi...@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 <py...@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 infrastructure@apache.org or file a JIRA
> > ticket
> > >>>>> with INFRA.
> > >>>>> ---
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> Daan
> > >
> >
> >
>
Re: [GitHub] cloudstack pull request: Remove AWS api bridge
Posted by Ian Duffy <ia...@ianduffy.ie>.
+1 on ec2stack working well (bias view).
I've used it via vagrant-aws, boto and eucalyptus eutester without issue.
It could use some documentation on deployment for production purposes, the
embedded webserver it exposes is OK but I'd feel safer with it bring behind
nginx/Apache.
On 21 Nov 2014 14:31, "Hugo Trippaers" <hu...@trippaers.nl> wrote:
> Let’s start by getting this on a feature branch.
>
> I would like to make sure that everything works before we remove the code
> and that includes deb and rpm packaging. We also need to think about the
> upgrade path. If a user is currently using awsapi, he needs an upgrade path
> the start using the replacement.
>
> Cheers,
>
> Hugo
>
> > On 21 nov. 2014, at 14:39, Sebastien Goasguen <ru...@gmail.com> wrote:
> >
> >
> > On Nov 21, 2014, at 8:33 AM, Nux! <nu...@li.nux.ro> wrote:
> >
> >> +1 what Daan said.
> >>
> >> Once ec2stack works well, then nuke awsapi.
> >>
> >
> > it works well.
> >
> > where can we see test about awsapi ?
> >
> >> my 2 pence
> >>
> >> --
> >> Sent from the Delta quadrant using Borg technology!
> >>
> >> Nux!
> >> www.nux.ro
> >>
> >> ----- Original Message -----
> >>> From: "Daan Hoogland" <da...@gmail.com>
> >>> To: "dev" <de...@cloudstack.apache.org>
> >>> Sent: Friday, 21 November, 2014 13:16:25
> >>> Subject: Re: [GitHub] cloudstack pull request: Remove AWS api bridge
> >>
> >>> As Seb mentioned on list there is an alternative. I don't think we
> >>> should remove this before the factored out version is working as well
> >>> (or the alternative he mentions is at least as complete) The idea of
> >>> isolating this bit is appealing though.
> >>>
> >>> Daan
> >>>
> >>> On Fri, Nov 21, 2014 at 12:23 PM, Nux! <nu...@li.nux.ro> wrote:
> >>>> 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" <gi...@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 <py...@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 infrastructure@apache.org or file a JIRA
> ticket
> >>>>> with INFRA.
> >>>>> ---
> >>>
> >>>
> >>>
> >>> --
> >>> Daan
> >
>
>
Re: [GitHub] cloudstack pull request: Remove AWS api bridge
Posted by Hugo Trippaers <hu...@trippaers.nl>.
Let’s start by getting this on a feature branch.
I would like to make sure that everything works before we remove the code and that includes deb and rpm packaging. We also need to think about the upgrade path. If a user is currently using awsapi, he needs an upgrade path the start using the replacement.
Cheers,
Hugo
> On 21 nov. 2014, at 14:39, Sebastien Goasguen <ru...@gmail.com> wrote:
>
>
> On Nov 21, 2014, at 8:33 AM, Nux! <nu...@li.nux.ro> wrote:
>
>> +1 what Daan said.
>>
>> Once ec2stack works well, then nuke awsapi.
>>
>
> it works well.
>
> where can we see test about awsapi ?
>
>> my 2 pence
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> ----- Original Message -----
>>> From: "Daan Hoogland" <da...@gmail.com>
>>> To: "dev" <de...@cloudstack.apache.org>
>>> Sent: Friday, 21 November, 2014 13:16:25
>>> Subject: Re: [GitHub] cloudstack pull request: Remove AWS api bridge
>>
>>> As Seb mentioned on list there is an alternative. I don't think we
>>> should remove this before the factored out version is working as well
>>> (or the alternative he mentions is at least as complete) The idea of
>>> isolating this bit is appealing though.
>>>
>>> Daan
>>>
>>> On Fri, Nov 21, 2014 at 12:23 PM, Nux! <nu...@li.nux.ro> wrote:
>>>> 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" <gi...@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 <py...@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 infrastructure@apache.org or file a JIRA ticket
>>>>> with INFRA.
>>>>> ---
>>>
>>>
>>>
>>> --
>>> Daan
>
Re: [GitHub] cloudstack pull request: Remove AWS api bridge
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Nov 21, 2014, at 8:33 AM, Nux! <nu...@li.nux.ro> wrote:
> +1 what Daan said.
>
> Once ec2stack works well, then nuke awsapi.
>
it works well.
where can we see test about awsapi ?
> my 2 pence
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> ----- Original Message -----
>> From: "Daan Hoogland" <da...@gmail.com>
>> To: "dev" <de...@cloudstack.apache.org>
>> Sent: Friday, 21 November, 2014 13:16:25
>> Subject: Re: [GitHub] cloudstack pull request: Remove AWS api bridge
>
>> As Seb mentioned on list there is an alternative. I don't think we
>> should remove this before the factored out version is working as well
>> (or the alternative he mentions is at least as complete) The idea of
>> isolating this bit is appealing though.
>>
>> Daan
>>
>> On Fri, Nov 21, 2014 at 12:23 PM, Nux! <nu...@li.nux.ro> wrote:
>>> 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" <gi...@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 <py...@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 infrastructure@apache.org or file a JIRA ticket
>>>> with INFRA.
>>>> ---
>>
>>
>>
>> --
>> Daan
Re: [GitHub] cloudstack pull request: Remove AWS api bridge
Posted by Nux! <nu...@li.nux.ro>.
+1 what Daan said.
Once ec2stack works well, then nuke awsapi.
my 2 pence
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Daan Hoogland" <da...@gmail.com>
> To: "dev" <de...@cloudstack.apache.org>
> Sent: Friday, 21 November, 2014 13:16:25
> Subject: Re: [GitHub] cloudstack pull request: Remove AWS api bridge
> As Seb mentioned on list there is an alternative. I don't think we
> should remove this before the factored out version is working as well
> (or the alternative he mentions is at least as complete) The idea of
> isolating this bit is appealing though.
>
> Daan
>
> On Fri, Nov 21, 2014 at 12:23 PM, Nux! <nu...@li.nux.ro> wrote:
>> 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" <gi...@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 <py...@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 infrastructure@apache.org or file a JIRA ticket
>>> with INFRA.
>>> ---
>
>
>
> --
> Daan
Re: [GitHub] cloudstack pull request: Remove AWS api bridge
Posted by Daan Hoogland <da...@gmail.com>.
As Seb mentioned on list there is an alternative. I don't think we
should remove this before the factored out version is working as well
(or the alternative he mentions is at least as complete) The idea of
isolating this bit is appealing though.
Daan
On Fri, Nov 21, 2014 at 12:23 PM, Nux! <nu...@li.nux.ro> wrote:
> 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" <gi...@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 <py...@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 infrastructure@apache.org or file a JIRA ticket
>> with INFRA.
>> ---
--
Daan
Re: [GitHub] cloudstack pull request: Remove AWS api bridge
Posted by Nux! <nu...@li.nux.ro>.
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" <gi...@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 <py...@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 infrastructure@apache.org or file a JIRA ticket
> with INFRA.
> ---