vagrant-provision

Is it possible to restart a machine when provisioning a machine using Vagrant and pickup where the script left off?

独自空忆成欢 提交于 2019-12-09 14:14:43
问题 I was reading a tutorial in bash where they said to restart the machine, there was no option to restart a service directly, it was a matter of restarting the machine, and then there were more commands after that that still needed to be run when provisioning. So is there any way to restart a box amid provisioning and then pick up where you left off after that? 回答1: As far as I know you can't have a single script/set of commands that would carry on where it left off if it attempts to restart

Ansible bitbucket clone provisioning ssh error

懵懂的女人 提交于 2019-12-08 14:29:43
In summary, When provisioning my vagrant box using Ansible, I get thrown a mysterious error when trying to clone my bitbucket private repo using ssh. The error states that the "Host key verification failed". Yet if I vagrant ssh and then run the ' git clone ' command, the private repo is successfully cloned. This indicates that the ssh forward agent is indeed working and the vagrant box can access my private key associated with the bitbucket repo. I have been struggling for two days on this issue and am loosing my mind! Please, somebody help me!!! Vagrantfile: Vagrant.configure("2") do |config

How do I separate stages of multi-machine cluster provisioning?

守給你的承諾、 提交于 2019-12-08 07:16:37
问题 Let's say I have 4 Vagrant boxes. 3 are variations of the same configuration, say, Consul, and one has a completely different configuration, say a database. I need to run a provisioning step with slight variations on the three similarly configured Consul VMs. Then, I need to run a provisioning step against 1 of those Vault VMs. Only after this provisioning step run on 1 of the VMs can I successfully run the next provisioning step, with slight variations, on the three similarly configured

How do I separate stages of multi-machine cluster provisioning?

只愿长相守 提交于 2019-12-06 14:45:19
Let's say I have 4 Vagrant boxes. 3 are variations of the same configuration, say, Consul, and one has a completely different configuration, say a database. I need to run a provisioning step with slight variations on the three similarly configured Consul VMs. Then, I need to run a provisioning step against 1 of those Vault VMs. Only after this provisioning step run on 1 of the VMs can I successfully run the next provisioning step, with slight variations, on the three similarly configured Vault VMs. I've read through the docs on Vagrant with multiple machines, looping over VM definitions, and