You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "David LaBissoniere (JIRA)" <ji...@apache.org> on 2010/12/29 18:57:47 UTC
[libcloud] [jira] Created: (LIBCLOUD-69) Support for EC2 Idempotent launches
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
Priority: Minor
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.
[libcloud] [jira] Updated: (LIBCLOUD-69) Support for EC2 Idempotent launches
Posted by "David LaBissoniere (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David LaBissoniere updated LIBCLOUD-69:
---------------------------------------
Attachment: ec2-idempotent-launch.diff
Attached is a patch providing EC2 idempotent launch support.
> 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
> Priority: Minor
> Attachments: ec2-idempotent-launch.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.
[libcloud] [jira] Resolved: (LIBCLOUD-69) Support for EC2 Idempotent launches
Posted by "Jerry Chen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Chen resolved LIBCLOUD-69.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.4.1
Assignee: Jerry Chen
Thanks for your contribution. This has been committed in r1054521.
I'm going to close this ticket, but if you can provide a test in test/test_ec2.py for ex_createnode, that would be great, especially for the following situation:
- If you repeat the request with the same client token, but change another request parameter, Amazon EC2 returns an IdempotentParameterMismatch error.
When testing with the live API though, I did not seem to receive this error.
> 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
>
>
> 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.
[libcloud] [jira] Resolved: (LIBCLOUD-69) Support for EC2 Idempotent launches
Posted by "Jerry Chen (JIRA)" <ji...@apache.org>.
[ 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.
[libcloud] [jira] Updated: (LIBCLOUD-69) Support for EC2 Idempotent launches
Posted by "David LaBissoniere (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David LaBissoniere updated LIBCLOUD-69:
---------------------------------------
Attachment: ec2_idem_tests.diff
Thanks for quick integration of the feature. Attached is a patch which provides tests for EC2 idempotent node creation. I also added a new exception type for the parameter mismatch error and appropriate handling in parse_error().
I may not have rigged up the new fixtures in the best way, but all passes. I'm not sure why you were unable to reproduce the error with EC2 itself, I am able to by adjusting the instance count parameters and using the same client 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.
[libcloud] [jira] Reopened: (LIBCLOUD-69) Support for EC2 Idempotent launches
Posted by "David LaBissoniere (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David LaBissoniere reopened LIBCLOUD-69:
----------------------------------------
Reopening because of the new patch including tests.
> 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.