# Vagrant Ansible Provisioner - best practice

**URL:** <https://forum.ansible.com/t/vagrant-ansible-provisioner-best-practice/18652>\
**Category:** Ansible Project\
**Tags:** galaxy-ng\
**Created:** [July 1, 2015, 3:08pm UTC](https://forum.ansible.com/t/vagrant-ansible-provisioner-best-practice/18652 "2015-07-01T15:08:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![chinedu\_uzoka](https://avatars.discourse-cdn.com/v4/letter/c/839c29/32.png) [@chinedu\_uzoka](https://forum.ansible.com/u/chinedu_uzoka)\
**Post date:** [July 1, 2015, 3:08pm UTC](https://forum.ansible.com/t/vagrant-ansible-provisioner-best-practice/18652/1 "2015-07-01T15:08:45Z")

</div>

Ive been asked to use Ansible to create a CI and CD pipeline - i have extensive knowledge of Puppet and know experience of Ansible - im almost two weeks in and after trying to model Ansible with same concepts derived from Puppet im almost happy

Some frustrations aside i wondered whether I am doing things a ok

My setup is thus -

I have a Packer repo to build OS  
I have an Ansible repo using ansible-galaxy (like i did with r10k)  
Vagrant repo and ansible is including in the project as a submodule

I have a nodes.yaml file like so: