[
https://issues.apache.org/jira/browse/JCLOUDS-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-290:
--------------------------------
Component/s: jclouds-compute
> CreatePlacementGroupIfNeeded should not try to recreate existing placement
> groups
> ---------------------------------------------------------------------------------
>
> Key: JCLOUDS-290
> URL: https://issues.apache.org/jira/browse/JCLOUDS-290
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-compute
> Affects Versions: 1.5.10, 1.6.0, 1.6.1, 1.6.2
> Reporter: G Gordon Worley III
>
> The current behavior of CreatePlacementGroupIfNeeded is not the expected
> behavior or the most useful. If a placement group is not specified
> explicitly, it will try to create a placement group, even if one with the
> auto generated name it will use exists already, resulting in an error. A
> better and more useful behavior from my perspective would be to just use the
> placement group if it already exists and only try to create one of it doesn't
> exist.
> This way the default case is that jclouds will manage placement groups for
> the developer rather than the default case needing to be that the developer
> manages placement groups because of a need to avoid errors when calling to
> CreatePlacementGroupIfNeeded.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
