Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E80FF10243 for ; Fri, 21 Nov 2014 13:35:29 +0000 (UTC) Received: (qmail 34419 invoked by uid 500); 21 Nov 2014 13:35:29 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 34360 invoked by uid 500); 21 Nov 2014 13:35:29 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 34347 invoked by uid 99); 21 Nov 2014 13:35:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Nov 2014 13:35:28 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of nux@li.nux.ro designates 31.193.175.196 as permitted sender) Received: from [31.193.175.196] (HELO mailserver.lastdot.org) (31.193.175.196) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Nov 2014 13:35:03 +0000 Received: from localhost (localhost [IPv6:::1]) by mailserver.lastdot.org (Postfix) with ESMTP id 1FB002C4CBC for ; Fri, 21 Nov 2014 13:33:29 +0000 (GMT) Received: from mailserver.lastdot.org ([IPv6:::1]) by localhost (mailserver.lastdot.org [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id ncU-pDuXf-xM for ; Fri, 21 Nov 2014 13:33:20 +0000 (GMT) Received: from localhost (localhost [IPv6:::1]) by mailserver.lastdot.org (Postfix) with ESMTP id E61E52C4CBF for ; Fri, 21 Nov 2014 13:33:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.9.2 mailserver.lastdot.org E61E52C4CBF DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=li.nux.ro; s=C605E3A6-F3C6-11E3-AEB0-DFF9218DCAC4; t=1416576799; bh=syqDHFDbn44csYk/S+sEJ63PIV5k6fmAFnoMP/0sl8w=; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type: Content-Transfer-Encoding; b=XouEmKRCZxl8HlowKp4UlVsa51u8kAZGI7f5eJivGxM0wtZdm0CDAzNfk3H1NSgC6 JSjmuQ8xA745nd7RhYs4vfKChkVaatQ2nSzMnsdp/fA2kbz95En4K+EOOVzVY7KspM CkMqQHjgAyfUflbD29lROGRFWa37fVu5NjFNU/sw= X-Virus-Scanned: amavisd-new at mailserver.lastdot.org Received: from mailserver.lastdot.org ([IPv6:::1]) by localhost (mailserver.lastdot.org [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id NXS0m2LyJ5Gq for ; Fri, 21 Nov 2014 13:33:19 +0000 (GMT) Received: from mailserver.lastdot.org (mailserver.lastdot.org [31.193.175.196]) by mailserver.lastdot.org (Postfix) with ESMTP id A53272C4CBC for ; Fri, 21 Nov 2014 13:33:19 +0000 (GMT) Date: Fri, 21 Nov 2014 13:33:19 +0000 (GMT) From: Nux! To: dev@cloudstack.apache.org Message-ID: <453402101.17222.1416576799365.JavaMail.zimbra@li.nux.ro> In-Reply-To: References: <1173927162.17101.1416568991736.JavaMail.zimbra@li.nux.ro> Subject: Re: [GitHub] cloudstack pull request: Remove AWS api bridge MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Mailer: Zimbra 8.5.1_GA_3056 (ZimbraWebClient - FF33 (Linux)/8.5.1_GA_3056) Thread-Topic: cloudstack pull request: Remove AWS api bridge Thread-Index: aoBnKnWUmECOzfGi4TT+P62RoNyYrg== X-Virus-Checked: Checked by ClamAV on apache.org +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" > To: "dev" > 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! 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" >>> 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 >>> 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