This documentation is known to work with all Linux or BSD Flavors (including OSX).
First, you need to ensure that python2 with virtualenv and pip support is installed on your system. Please refer to your OS documentation.
I don't need to explain that.
$ git clone https://github.com/your_login/obm-deploy
$ cd obm-deploy$ virtualenv --no-site-packages obm-deploy-env# virtualenvwrapper must be installed on your OS
$ mkvirtualenv -p /usr/bin/python2 --no-site-packages obm-deploy-env$ source obm-deploy-env/bin/activate# You must have created your virtualenv with virtualenvwrapper
$ workon obm-deploy-env$ pip install paramiko PyYAML jinja2 pyasn1 pycrypto python-keyczar==0.71b$ git clone https://github.com/ansible/ansible -b release1.5.5$ source ansible/hacking/env-setup# If you only want to setup ansible environment on activation
$ cat > ~/.virtualenvs/obm-deploy-env/bin/postactivate << EOF
#!/bin/bash
source $(pwd)/ansible/hacking/env-setup
EOF
# If you also want to automatically cd in to obm-deploy directory
$ cat > ~/.virtualenvs/obm-deploy-env/bin/postactivate << EOF
#!/bin/bash
cd $(pwd)
source ansible/hacking/env-setup
EOF
$ chmod +x ~/.virtualenvs/obm-deploy-env/bin/postactivateYou can use any kind of VM.
Make sure that you have access to it using SSH and user root.
If you want to use our test infrastructure, add this to you /etc/hosts :
ip_of_your_vm toto.example.com
ip_of_your_vm obm.example.comansible-playbook -i dev site.xml$ deactivate$ cd obm-deploy
$ source obm-deploy-env/bin/activate
$ source ansible/hacking/env-setup$ workon obm-deploy-env