I am running AWX running DockerCE community version on a CentOS 7 Virtual Machine. I see there are newer images of the Web UI and Task images and want to know what is the proper way up upgrade those 2 containers without loosing my data?
There was just a large merge of work into the AWX codebase. As such there will most likely be some backwards incompatible changes that make upgrading difficult. This is mentioned in a thread on the release of 1.0.2
Do you foresee to do this on a regular basis in this project?
What will Tower users do? There must be an upgrade path?
Hi John - can we get some clarity regarding upgrading and problems ? My thoughts were / belief that the configuration is held in Postgres dB ? Therefore we should be able to blow away the web and task docker containers at will and redeploy ? If we have the inventory / or enter previous values into new inventory ie passwords. Are you therefore suggesting it is changes to the dB schema that will cause an upgrade to fail ?
Andy
A reminder: the primary purpose of Tower is stability, and the primary
purpose of AWX is to move fast, even at the risk of occasionally
breaking things.
Tower upgrades are different because we have much stronger assurances
about customer environments, and because we're on the hook to fix
those issues if they go wrong. Upgrades for AWX are not a priority,
and we don't want to make promises about upgradability that we won't
be able to keep.
One possible workaround for AWX users is to export data from the old
AWX instance using the Tower API/CLI, and then import that data to the
new AWX instance.