search

bigfix / boxes

A collection of packer templates to create vagrant boxes for building and installing IBM Endpoint Manager
Apache License 2.0
6 stars 2 forks source link

Use Ansible to provision #24

Open gearoidibm opened 8 years ago

gearoidibm commented 8 years ago

I think a lot of users have Windows hosts so we'll need to support vagrant's Ansible local. I'm thinking this would be good in general because it means you don't have to install Ansible on the vagrant host, this makes it easier for users.

Anthonyo2015 commented 8 years ago

So if I'm wrapping my head around this correctly, we will be packaging our Ansible playbook along with Ansible local in the project, users then call vagrant up as usual and the vagrant file makes the call to run the Ansible playbook, which in turn provisions the client machine/machines. Is that accurate?

gearoidibm commented 8 years ago

I think that's almost correct. I think we'd install ansible in the base box ? The playbooks are in the shared folder (/vagrant on the host). Then ansible_local option is used in Vagrantfile.
Means that Ansible in not needed on the host - there's no Ansible available for Windows hosts, and I don't think there's every likely to be.

Anthonyo2015 commented 8 years ago

Oh I see now, so Ansible remote would be installed on the host and run a playbook to configure the guest machine from the host, but we will be installing Ansible on the base box and setting to use Ansible local in the Vagrant file so that the guest machine uses its own Ansible installation to configure itself with the playbook we provide through the /vagrant folder on the host