Yes I know this is not perfect and Virtualbox does not pass the VT-x instructions making using it painfully slow. I will adding provider to use VMware Fusion and hopefully ESXi.
With the that out of the way.
- "git clone https://github.com/EntropyWorks/bifrost.git"
- "cd bitfrost"
- "curl -L -o Vagrantfile https://goo.gl/qP9Zla"
- "curl -L -o vagrant.yml https://goo.gl/jILciH"
- "vagrant up"
- "vagrant ssh"
- "cp -r ~vagrant/.ssh /root
- "exit"
- "vagrant provision"
That got me closer but still not all the way.
PLAY [Tests connectivity to the VM] *******************************************
TASK: [bifrost-test-vm | Execute ping step to verify connectivity and login to the host. If this fails, the configdrive may not have loaded.] ***
<192.168.122.2> ESTABLISH CONNECTION FOR USER: cirros
<192.168.122.2> EXEC ssh -C -tt -vvv -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/root/.ansible/cp/ansible-ssh-%h-%p-%r" -o Port=22 -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=cirros -o ConnectTimeout=10 192.168.122.2 hostname
fatal: [192.168.122.2] => SSH Error: data could not be sent to the remote host. Make sure this host can be reached over ssh
FATAL: all hosts have already failed -- aborting
PLAY RECAP ********************************************************************
to retry, use: --limit @/root/test-bifrost-dynamic.yaml.retry
127.0.0.1 : ok=79 changed=32 unreachable=0 failed=0
192.168.122.2 : ok=0 changed=0 unreachable=1 failed=0
testvm1 : ok=36 changed=26 unreachable=0 failed=0
****************************
Test failed. See logs folder
****************************
Making logs directory and collecting logs.
FATAL: all hosts have already failed -- aborting
PLAY RECAP ********************************************************************
to retry, use: --limit @/Users/yazz/vagrant.retry
bifrost : ok=11 changed=5 unreachable=0 failed=1
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
Login in again "vagrant ssh"
vagrant@vagrant-ubuntu-vivid-64:~$ virsh list --all
Id Name State
----------------------------------------------------
5 testvm1 running
vagrant@vagrant-ubuntu-vivid-64:~$ cd /srv/bifrost/
vagrant@vagrant-ubuntu-vivid-64:/srv/bifrost$ . env-vars
vagrant@vagrant-ubuntu-vivid-64:/srv/bifrost$ ironic node-list
+--------------------------------------+------+---------------+-------------+--------------------+-------------+
| UUID | Name | Instance UUID | Power State | Provisioning State | Maintenance |
+--------------------------------------+------+---------------+-------------+--------------------+-------------+
| a8cb6624-0d9f-c882-affc-046ebb96ec01 | None | None | power on | active | False |
+--------------------------------------+------+---------------+-------------+--------------------+-------------+
vagrant@vagrant-ubuntu-vivid-64:/srv/bifrost$ ironic port-list
+--------------------------------------+-------------------+
| UUID | Address |
+--------------------------------------+-------------------+
| 22d28ab5-3507-4ca4-bd09-b7d01b5eb5a0 | 52:54:00:8b:07:3f |
+--------------------------------------+-------------------+
vagrant@vagrant-ubuntu-vivid-64:/srv/bifrost$ ironic driver-list
+---------------------+-------------------------+
| Supported driver(s) | Active host(s) |
+---------------------+-------------------------+
| agent_ilo | vagrant-ubuntu-vivid-64 |
| agent_ipmitool | vagrant-ubuntu-vivid-64 |
| agent_ssh | vagrant-ubuntu-vivid-64 |
| agent_ucs | vagrant-ubuntu-vivid-64 |
| pxe_amt | vagrant-ubuntu-vivid-64 |
+---------------------+-------------------------+