[
https://issues.apache.org/jira/browse/JCLOUDS-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer updated JCLOUDS-450:
---------------------------------
Fix Version/s: 1.7.2
Committed for 1.8.0, waiting for 1.7.1 to release and then committing to 1.7.x
as well.
> Support min/max count and client token fields for AWS EC2 RunInstances
> ----------------------------------------------------------------------
>
> Key: JCLOUDS-450
> URL: https://issues.apache.org/jira/browse/JCLOUDS-450
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-compute
> Reporter: Andrew Bayer
> Assignee: Andrew Bayer
> Fix For: 1.8.0, 1.7.2
>
>
> AWS's RunInstances API method
> (http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-RunInstances.html)
> allows for specifying minimum and maximum count - if given, you'll get at
> least the minimum number and no more than the maximum, unless the minimum is
> greater than the number of instances you can launch in that AZ/region (say,
> if you've already got enough instances of a size that's got a per-region
> limit such that creating min count more would push over the limit), in which
> case you don't get any. It'd be nice to support this, both to simplify
> multiple instance creation (rather than X separate calls to RunInstances,
> just one...) and to take advantage of the behavior if you try to launch more
> than you can.
> As well, we should have some form of support for RunInstances' idempotency -
> see
> http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Run_Instance_Idempotency.html
> - if you pass a client token to the call, each subsequent call with the same
> arguments (including the client token) will return the same response, only
> varying in the HTTP response code. So you can keep making the same call (say,
> with a > 1 min count) until you get a terminating response.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
