Return-Path: X-Original-To: apmail-deltacloud-dev-archive@www.apache.org Delivered-To: apmail-deltacloud-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 84C53F557 for ; Fri, 26 Apr 2013 14:16:17 +0000 (UTC) Received: (qmail 36754 invoked by uid 500); 26 Apr 2013 14:16:17 -0000 Delivered-To: apmail-deltacloud-dev-archive@deltacloud.apache.org Received: (qmail 36686 invoked by uid 500); 26 Apr 2013 14:16:16 -0000 Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@deltacloud.apache.org Delivered-To: mailing list dev@deltacloud.apache.org Received: (qmail 36657 invoked by uid 99); 26 Apr 2013 14:16:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Apr 2013 14:16:16 +0000 Date: Fri, 26 Apr 2013 14:16:16 +0000 (UTC) From: "Michal Fojtik (JIRA)" To: dev@deltacloud.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DTACLOUD-557) Update EC2 Driver to support EBS backed instances MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DTACLOUD-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642876#comment-13642876 ] Michal Fojtik commented on DTACLOUD-557: ---------------------------------------- There are some related JIRA's and threads on mailing list on this. In general, I think it would be easy to add support for EBS, just by modifying the ec2_driver state machine and adding stop/start methods there. Everything else will be done my Rabbit magic. On the other hand, this approach does not work for the non-ebs based instances, where calling 'stop' operation means that the instance cannot be started again. I'm not sure how to advertise this difference, without having two state machines. Possible solutions: * Create a new driver that inherits from EC2 driver but have different state machine and implements missing methods. * Make the EC2 driver support only EBS state machine and then don't advertise the 'start' operation when the image is 'ebs' (we already advertise the image type in image referenced from instance) * Add second state machine to Ec2 driver and make instance resource point to the right state machine (link :href => /instance_states/ebs) I personally like option 2) which also can be advertised as a 'feature'. > Update EC2 Driver to support EBS backed instances > ------------------------------------------------- > > Key: DTACLOUD-557 > URL: https://issues.apache.org/jira/browse/DTACLOUD-557 > Project: DeltaCloud > Issue Type: New Feature > Reporter: David Ellinger > Labels: features > Original Estimate: 6h > Remaining Estimate: 6h > > Currently the deltacloud implementation does not support EBS backed instances -- and due to this "Start" / "Stop" are currently not implemented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira