Astronaut

This release finished the migration to Ansible Galaxy. All Roles are moved out to separate repos, because Galaxy supports only one role per repo yet.
During the migration all roles were reviewed and full automatically tested. End the end there are a coverage of 640 use cases, and Travis will check this in every commit and at least once per week, to check if something changed on OTC APIs. Monitor status is here: https://travis-ci.org/eumel8/
Cleanups and smaller bug fixes are also include in this release. So please use always the latest version.

Crossroads

This minor release includes new role otc_cts (Cloud Trace Service). Some robustness was added with retry loops if an API call goes failed.
To fit #18 some considerations are required about the future of the project structure. The developement will based on this release

Diet

Slim down the Ansible task for each workflow - this is the main feature for release 4.0 of ansible-otc. The un-common usage of tags are removed and focus is set on variable "localaction", which takes specific action on the give role like "create ECS". The minimized count of roles can be checked with ARA, Ansible Run Analyse. A small documentation and use case was added.
Another feature is idempotence of roles. In the previous releases after multiple runs of playbook multiple resources with the same name were created. This is avoid now with a resource check before.
Some smaller bugfixes are also included and a full run with ansible-lint on all roles. Enjoy DIet.

Magic Spring

As in the pre-release 2.5 mentioned this version of ansible-otc is now complete reworked. Roles exists corresponding to the OTC services. For example otc_ecs contains all interaction with ECS service on OTC.
Therefore interactions follow the CRUD model (Create Read Update Delete ressources).
Each role has a README.rst which is includes in the centralized Sphinx documentation on
http://ansible-otc.readthedocs.io/ - workshop documentation, DNS, connect cheat sheet are adjusted.
Travis includes some basic test cases. Of course, not all use cases are tested, we will focus on Ansible > 2.4 compatible functions.

Winter Wonder

We are in the middle of the complete re-factoring of ansible-otc. Roles are migrated to otc_*. These roles are compact and usable with CRUD (Create Read Update Delete) resources.
Current status: bootstrap ECS with all resources like network and storage. Manage DNS. All with 3 configuration backends: ini, json, yaml.
Documentation is moved to http://ansible-otc.readthedocs.io/ and build by Sphinx.
Code will be now tested with different Ansible versions by Travis.
Open work: ELB, S3, and new services

Action

Action

With this release we bring some action to API and OTC services. A central configuration file is now tenant.ini. Here are all services like ECS, ELB, EVS declared in sections. A default section is also present, i.e. you want to start all ECS with the same image and in the same VPC.
2 new playbooks were added: tenant_create.yml and tenant_delete.yml. Look into example tenant.ini howto deploy resources.
A new implementation of DNS service started to work on OTC. You can now configure public and private zones and PTR records of EIP. A complete example is described in DNS.md
Sometimes you want to boot your complete configured or well prepared image on various VMs instead standard OS images and install your stuff again and again. To met this target a build service is required. Look into buildservice.yml if you are interested. Description of the PoC is in BUILDSERVICE.md
As you can see, there are a lot of action in this release. You can try out and improve.

Viewpoint

In this release are the views of different OTC resources implemented. Ecs-, image and network resources are connected and the JSON output can be reviewed. Basicly functions are separated like create resources for VMs, ELBs, IMS or upload data in S3. The goal of this release is to understand Fusion API behind OTC and interact with them.