Mailing-List: contact libcloud-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: libcloud@incubator.apache.org
Message-ID: <28205789.134001294152105818.JavaMail.jira@thor>
Date: Tue, 4 Jan 2011 09:41:45 -0500 (EST)
From: "Jerry Chen (JIRA)" <jira@apache.org>
To: libcloud@incubator.apache.org
In-Reply-To: <922546.61531293645467144.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: [libcloud] [jira] Resolved: (LIBCLOUD-69) Support for EC2 Idempotent
 launches


     [ https://issues.apache.org/jira/browse/LIBCLOUD-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Chen resolved LIBCLOUD-69.
--------------------------------

    Resolution: Fixed

Thanks for the tests and the new Exception; they are committed in r1055059.

As for not being able to reproduce it, I think I kept the same instance name and token.

> Support for EC2 Idempotent launches
> -----------------------------------
>
>                 Key: LIBCLOUD-69
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-69
>             Project: Libcloud
>          Issue Type: New Feature
>          Components: Core
>            Reporter: David LaBissoniere
>            Assignee: Jerry Chen
>            Priority: Minor
>             Fix For: 0.4.1
>
>         Attachments: ec2-idempotent-launch.diff, ec2_idem_tests.diff
>
>
> As of API version 2010-08-31, EC2 supports idempotent instance creation. An optional clientToken can be included in launch requests. Usage is detailed in this document: 
> http://docs.amazonwebservices.com/AWSEC2/latest/DeveloperGuide/index.html?Run_Instance_Idempotency.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.