[
https://issues.apache.org/jira/browse/LIBCLOUD-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomaz Muraus resolved LIBCLOUD-274.
-----------------------------------
Resolution: Fixed
Assignee: Tomaz Muraus
Thanks.
I merged it into trunk
(https://svn.apache.org/viewvc?view=revision&revision=1429674) with a minor
change - I've added _wait_until_runing back for backward compatibility.
> Allow multiple nodes to be passed to _wait_until_running
> --------------------------------------------------------
>
> Key: LIBCLOUD-274
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-274
> Project: Libcloud
> Issue Type: Bug
> Components: Compute
> Affects Versions: 0.11.2
> Reporter: Nick Bailey
> Assignee: Tomaz Muraus
> Attachments:
> 0001-Allow-passing-multiple-nodes-to-wait_until_running.patch
>
>
> In compute/base.py, we have a _wait_until_running method that polls launched
> instances and waits for them to finish coming up and have valid ssh
> interfaces.
> This change does 2 things:
> 1. Makes that method public. It is currently used by the deploy call but it
> is generally useful to clients as well. You may want to simply launch
> instances but have an easy way to tell when they are done launching.
> 2. Allows multiple nodes to be passed to wait_until_running(). Since this
> method takes a polling approach, it retrieves the list of all instances each
> time it polls. From a client perspective, it makes sense to launch multiple
> nodes and then block until all of them are running.
--
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
