I’ve talked before about how OpenCrowbar distributes SSH keys automatically as part of its deployment process. Now, it’s time to unleash some of the subsequent magic!
[5/21 Update: We added the “crowbar-access” role to the Drill release that allows you to inject/remove keys on a per node basis from the API or CLI at any point in the node life-cycle]
If you provision servers with your keys in place, then Ansible will just work with truly minimal configuration (one line in a file!).
Video Demo (steps bellow):
Here are my steps:
- Install OpenCrowbar and run some nodes to ready state [videos]
- Install Ansible [simple steps]
- Add hosts range “192.168.124.[81:83] ansible_ssh_user=root” to the
- If you are really lazy, add “[Default] // host_key_checking = False” to your “~/.ansible.cfg” file
- now ping the hosts, “ansible all -m ping”
- pat yourself on the back, you’re done.
- to show off:
- touch all machines “ansible all -a “/bin/echo hello”
- look at types of Linux “ansible all -a “uname -a”
Further integration work can make this even more powerful.
I’d like to see OpenCrowbar generate the Ansible inventory file from the discovery data and to map Ansible groups from deployments. Crowbar could also call Ansible directly to use playbooks or even do a direct hand-off to Tower to complete an install without user intervention.
Wow, that would be pretty handy! If you think so too, please join us in the OpenCrowbar community.