Migrating Java Services Release into Ansible Tower

Hello Fellow Engineers,

Following the launch of Ansible Tower and anticipating the upcoming deprecation of deploy-app dashboards on 25 October 2017 (link), for the past weeks, we've been exploring and experimenting with migrating the release of several java services belonging to user team into using the Tower capabilities.

You can read more about Ansible Tower and how to migrate your java services in the provided link. Since we're moving into per team's decentralized repository for the release roles and playbooks, if you want to, you can fork this sample repository, as a base to kickoff your migration process.

Migrating to Ansible Tower will bring several benefits, such as more agile process, better dashboard stability and features, and a more secure way to interact with production machines (since each team will be able to manage their own user authorizations).

Feedbacks will be very appreciated, and if you have further questions regarding the migration, you could leave questions in the related confluence pages, or alternatively in this document so we could later collate it into an FAQ list.

Thanks!!