| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Update the playbook mappings for 3.2
|
|\
| |
| | |
add 3.3 to installer
|
| | |
|
|\ \
| | |
| | | |
Add nfs group to OSEv3:vars
|
| | |
| | |
| | |
| | | |
Fixes #2129
|
|/ / |
|
|\ \
| | |
| | | |
Bug 1366595 - installer failed at task "Validate permissions on certificate files"
|
|/ / |
|
|\ \
| | |
| | | |
a-o-i: Fix broken upgrades
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Upgrade was looking for the hosts in the old location. Quick fix to get it looking in the
correct location.
Fixes BZ#1357627.
|
|/ / |
|
|\ \
| | |
| | | |
Reference tmpdir from first master hostvars when evacuating nodes.
|
|/ / |
|
|\ \
| | |
| | | |
Improvements for Docker 1.10+ Upgrade Image Nuking
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In a parallel step prior to real upgrade tasks, clear out all unused
Docker images on all hosts. This should be relatively safe to interrupt
as no real upgrade steps have taken place.
Once into actual upgrade, we again clear all images only this time with
force, and after stopping and removing all containers.
Both rmi commands use a new and hopefully less error prone command to do
the removal, this should avoid missed orphans as we were hitting before.
Added some logging around the current image count before and after this
step, most of them are only printed if we're crossing the 1.10 boundary
but one does not, just for additional information in your ansible log.
|
| | |
| | |
| | |
| | |
| | | |
This avoids the automatic image migration in 1.10, which can take a very
long time and potentially cause rpm db corruption.
|
|\ \ \
| | | |
| | | | |
a-o-i: Automatically Label Nodes as Infra
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In interactive mode, automatically label nodes as infrastructure nodes. Two cases are covered:
1) If all nodes are masters, all hosts are labeled infra
2) If dedicated nodes are defined, the first two (or one) nodes are labeled as infra
|
|\ \ \ \
| | | | |
| | | | | |
Support for redeploying certificates
|
| |/ / / |
|
|\ \ \ \
| |/ / /
|/| | | |
qps typo
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
a-o-i: Restrict installed host check
|
|/ / /
| | |
| | |
| | | |
Restrict installed host check to only masters and nodes.
|
|\ \ \
| | | |
| | | | |
docker-registry's middleware stanza should contain 'registry' and 'storage' by default
|
| | | | |
|
| |/ /
| | |
| | |
| | | |
by default
|
|/ / |
|
|\ \
| | |
| | | |
Ansible 2.2 Support
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Bug 1365379 - Need to have 'NoVolumeZoneConflict' scheduler policy enabled by installer
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
a-o-i: Move ansible_ssh_user to deployment
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Update the nosetests to reflect the new location of ansible_ssh_user
in the config file.
|
| |/ / / |
|
|\ \ \ \
| |/ / /
|/| | | |
a-o-i: Labeling nodes only
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
make the improved log formatter work with ansible 2.1
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Ansible 2.1 changed the base class used for log formatting. Using
the old one with ansible 2.1 caused a "too much recursion" problem.
The fix is to call _dump_results in the new CallbackBase base class
when using ansible 2.1 or later.
|
|\ \ \
| | | |
| | | | |
Set become=no for etcd server certificates temporary directory.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
1.3 / 3.3 Upgrades
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When adding a property to a section that does not yet exist, the
property was being inserted into the section above where it should have
due to the pointer not being adjusted for the new section we created.
Adds a test sub-directory, would like to eventually move all the
ooinstall tests here as well so nosetests just works from top level
directory.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Refactored the 3.2 upgrade common files out to a path that does not
indicate they are strictly for 3.2.
3.3 upgrade then becomes a relatively small copy of the byo entry point,
all calling the same code as 3.2 upgrade.
Thus far there are no known 3.3 specific upgrade tasks. In future we
will likely want to allow hooks out to version specific pre/upgrade/post
tasks.
Also fixes a bug where the handlers were not restarting
nodes/openvswitch containers doing upgrades, due to a change in Ansible
2+.
|