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 <i...@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" <h...@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 <run...@gmail.com> > wrote: > > > > > > > > > On Nov 21, 2014, at 8:33 AM, Nux! <n...@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" <daan.hoogl...@gmail.com> > > >>> To: "dev" <dev@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! <n...@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" <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. > > >>>>> --- > > >>> > > >>> > > >>> > > >>> -- > > >>> Daan > > > > > > > >
