x/monasca-vagrant
Code Issues Proposed changes

Ansible ssh issues appear to not be a race condition but a host key checking issue

Browse Source 
Change-Id: Ie5b85b4d7534c619ffceb34a73ad6ca3a44fb7c3
This commit is contained in:
Tim Kuhlman 2014-11-25 10:19:25 -07:00
parent e98b542158
commit e19a9424cc
2 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@ -111,6 +111,7 @@ your local ansible configuration (~/.ansible.cfg or a personal ansible.cfg in th
hostfile = .ansible_hosts
private_key_file = ~/.vagrant.d/insecure_private_key
remote_user = vagrant
host_key_checking = False
## Running behind a Web Proxy
If you are behind a proxy you can install the `vagrant-proxyconf` pluging to have Vagrant honor standard proxy-related environment variables and set the

6
Vagrantfile vendored
View File

@ -33,11 +33,10 @@ Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
vb.memory = 7168
vb.cpus = 4
end
# In Vagrant 1.6.5 there is a race condition where in some instances the ansible provisioner starts before ssh is ready the sleep is a workaround
ds.vm.provision "shell", inline: 'sleep 1'
ds.vm.provision "ansible" do |ansible|
ansible.playbook = "devstack.yml"
ansible.inventory_path = '.ansible_hosts'
ansible.host_key_checking = false
end
end
@ -50,11 +49,10 @@ Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
vb.memory = 6144
vb.cpus = 4
end
# In Vagrant 1.6.5 there is a race condition where in some instances the ansible provisioner starts before ssh is ready the sleep is a workaround
mm.vm.provision "shell", inline: 'sleep 1'
mm.vm.provision "ansible" do |ansible|
ansible.playbook = "mini-mon.yml"
ansible.inventory_path = '.ansible_hosts'
ansible.host_key_checking = false
end
end