OAH VM SPECIFICATION

Layout

Must be a GIT repo accesible to OAH-Shell

Must be a valid Ansible Role

Naming Convention :

Must follow the naming convention of ansible-role-oah-XXXX where XXXX is the oah community accepted name that clearly mentions the purpose of the roles.

Must Have files :

Each oah ansible role must have the following Task files in the tasks folder of the ansible role

• main.yml
• oah-install.yml
• oah-remove.yml
• oah-reset.yml
• oah-update.yml
• oah-validate.yml

OAH task yml files should have tasks to safely install, update, reset , validate or remove the all changes done by the role.

Each OAH role will have a in-built Task to validate (and determine) if the role has been successfully installed.

EACH OAH Roles must follow the best practices as mentioned(http://docs.ansible.com/ansible/playbooks_best_practices.html)

OAH_ROLE Ansible Variables

All OAH Ansible Variables will begin with a OAH_

OAH_COMMAND : Is used to determine the operation mode of a role.

OAH_COMMAND param can have the following values => install , remove , reset , update and validate )

OAH_COMMAND will default to update , it can have values install,remove, reset, update and validate. (i.e If OAH_COMMAND param is not passed to the main.yml in tasks folder for a role , main will include oah_update.yml or oah_install.yml if the role has not be installed yet.)