Matthew Jones ea8b78ca49 Protect cluster nodes after an upgrade
* Modify instance model to container a version number for the node
* Update that version number during the heartbeat
* If during a heartbeat any of the nodes are of a newer version then
  shutdown the current node.

The idea behind this is that if all nodes were upgraded at the same
time then at the moment of the healthcheck they should all be at the
newer version. Otherwise we put the system in a state where it can
receive the upgrade but stay down until that happens. During setup
playbook run the services will be fully restarted.
2017-04-10 15:37:33 -04:00
2017-02-28 14:03:52 -05:00
2017-03-29 14:30:58 -04:00
2016-02-01 18:37:56 -05:00
2015-02-06 09:47:41 -05:00
2016-07-22 13:19:57 -04:00
2016-12-20 15:34:29 -05:00
2016-03-04 16:19:00 -05:00
2015-06-11 16:10:23 -04:00
2016-11-02 14:16:27 -04:00
2016-10-18 14:19:18 -04:00
2016-11-11 16:01:45 -05:00
2016-11-15 17:31:21 -05:00
2017-03-23 16:46:25 -04:00

Build Status Requirements Status

Ansible Tower

Tower provides a web-based user interface, REST API and task engine built on top of Ansible.

Resources

Refer to CONTRIBUTING.md to get started developing, testing and building Tower.

Refer to setup/README.md to get started deploying Tower.

Refer to docs/build_system.md for more about Jenkins and installing nightly builds (as opposed to running from source).

Refer to docs/release_process.md for information on the steps involved in creating a release.

Refer to http://docs.ansible.com/ansible-tower/index.html for information on installing/upgrading, setup, troubleshooting, and much more.

Description
AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
Readme 429 MiB
Languages
Python 97.8%
Jinja 0.9%
Makefile 0.5%
Shell 0.3%
HTML 0.2%
Other 0.2%