Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support standard option config.vm.boot_timeout #227

Closed
ggiamarchi opened this issue Apr 15, 2015 · 1 comment
Closed

Support standard option config.vm.boot_timeout #227

ggiamarchi opened this issue Apr 15, 2015 · 1 comment
Labels
enhancement
Milestone
0.7.2

Comments

@ggiamarchi
Copy link
Owner

See how to support it in contrast with other specific timeout settings.
@ggiamarchi ggiamarchi mentioned this issue Apr 15, 2015
Closed
Sharpie added a commit to Sharpie/vagrant-openstack-provider that referenced this issue Apr 13, 2016
@Sharpie
Switch to WaitForCommunicator
6d722e3 
The OpenStack provider's action_up used a custom WaitForServerToBeAccessible
action to poll instances via SSH in order to determine when the VM is up and
running. One large shortcoming of this custom implementation is that it does
not support communicators other than SSH, notably WinRM. This patch replaces
the WaitForServerToBeAccessible with the built-in WaitForCommunicator action
which has been part of Vagrant since v1.3 and is able to handle multiple
communicators.

Fixes ggiamarchi#264.
Closes ggiamarchi#227.
Sharpie added a commit to Sharpie/vagrant-openstack-provider that referenced this issue Apr 13, 2016
@Sharpie
Switch to WaitForCommunicator
c5d651e 
The OpenStack provider's action_up used a custom WaitForServerToBeAccessible
action to poll instances via SSH in order to determine when the VM is up and
running. One large shortcoming of this custom implementation is that it does
not support communicators other than SSH, notably WinRM. This patch replaces
the WaitForServerToBeAccessible with the built-in WaitForCommunicator action
which has been part of Vagrant since v1.3 and is able to handle multiple
communicators.

Fixes ggiamarchi#264.
Closes ggiamarchi#227.
@Sharpie
Copy link
Contributor

Sharpie commented Apr 13, 2016

I've implemented this in PR #281 as part of a switch to the built-in WaitForCommunicator middleware.

@ggiamarchi ggiamarchi added this to the 0.7.2 milestone Apr 30, 2016
Sharpie added a commit to Sharpie/vagrant-openstack-provider that referenced this issue Jul 25, 2016
@Sharpie
Switch to WaitForCommunicator
d610ae8 
The OpenStack provider's action_up used a custom WaitForServerToBeAccessible
action to poll instances via SSH in order to determine when the VM is up and
running. One large shortcoming of this custom implementation is that it does
not support communicators other than SSH, notably WinRM. This patch replaces
the WaitForServerToBeAccessible with the built-in WaitForCommunicator action
which has been part of Vagrant since v1.3 and is able to handle multiple
communicators.

Fixes ggiamarchi#264.
Closes ggiamarchi#227.
Sharpie added a commit to Sharpie/vagrant-openstack-provider that referenced this issue Jul 31, 2016
@Sharpie
Switch to WaitForCommunicator
300f9a7 
The OpenStack provider's action_up used a custom WaitForServerToBeAccessible
action to poll instances via SSH in order to determine when the VM is up and
running. One large shortcoming of this custom implementation is that it does
not support communicators other than SSH, notably WinRM. This patch replaces
the WaitForServerToBeAccessible with the built-in WaitForCommunicator action
which has been part of Vagrant since v1.3 and is able to handle multiple
communicators.

Fixes ggiamarchi#264.
Closes ggiamarchi#227.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
0.7.2
Development

No branches or pull requests
2 participants
@Sharpie @ggiamarchi