After another year with work and usage of Ansible-OTC I want to share a project update and the vision for 2018.
- Role collection. There are a lots of roles in the Github Repo. This is good to show the work of OTC-API and for demonstration, but bad for overview and automation. I tried to collect functions following the CRUD standard into new roles. I.e. otc_ecs should Create, Read, Update, and Delete ECS resources on OTC: https://github.com/eumel8/ansible-otc/tree/dev/roles/otc_ecs
- Input-Handler. It was a good idea to use ini-files for configuration items, because it's good readable and easy to unterstand. Previously I used yml-files for the same function, other projects are using json. To split this function more from the Ansible roles I created different handlers for ini, yml and json, so the customer can choice: https://github.com/eumel8/ansible-otc/tree/dev/playbooks/vars
- Testing. Ansible developement goes really fast, so code can sometimes break because things aren't working anymore in newer versions of Ansible or Python. I started to play with Travis and included some functional tests: https://travis-ci.org/eumel8/ansible-otc
- Documentation. There are multiple Markdown files for use cases and role description. I switched to Sphinx, which is more portable and documentation is nearly to the code like the role documentation. A published version is on http://ansible-otc.readthedocs.io/en/dev/?badge=latest
As you can see the next release of Ansible-OTC will contain a lot of changes, so it will be easier to use OTC with Ansible.