| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
With OpenShift 3.2, creating a service accessible from the outside of the
cluster thanks to `nodePort` automatically opens the “local” `iptables`
firewall to allow incoming connection on the `nodePort` of the service.
In order to benefit from this improvement, the OpenStack security group
shouldn’t block those incoming connections.
This change opens, on the OS nodes, the port range dedicated to service
node ports.
|
| |\
| |
| | |
Update uninstall.yml
|
| |/
|
| |
Fixes #2317
|
| |\
| |
| | |
Fix padding on registry config
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
Edits to fix to typos, grammar, and product branding in cli_installer
|
| | | |
|
| |\ \
| | |
| | | |
a-o-i: Fix nosetests after removing 3.2 from installer
|
| | | |
| | |
| | |
| | |
| | | |
Update the tests to match 3.3 being the only version.
Add support for non-latest if it's specified in the config file.
|
| |\ \ \
| | | |
| | | | |
Reconcile roles after master upgrade, but before nodes.
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Prevents the network egress bug causing node restart to fail during 3.3
upgrade. (even though a separate fix is incoming for this)
Only catch is preventing the openshift_cli role, which requires docker,
from triggering a potential upgrade, which we still don't want at this
point. To avoid we use the same variable to protect docker installed
version as we use in pre.yml.
|
| |\ \ \
| |/ /
|/| | |
fixing openshift key error in case of node failure during run (ssh is…
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Bug 1367323 - the "OpenShift Container Platform 3.2" variant is still listed when quick install ose-3.3
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
when quick install ose-3.3
Remove 3.2 from the install options in 3.3 installer.
|
| |\ \ \ \
| |/ / /
|/| | | |
Bug 1367199 - iptablesSyncPeriod should default to 30s OOTB
|
| |/ / /
| | |
| | |
| | | |
Update the default to thirty seconds.
|
| |\ \ \
| | | |
| | | | |
Image stream sync
|
| | | | | |
|
| | | |/
| |/| |
|
| |\ \ \
| |/ /
|/| | |
Add additional options to RequestHeaderProvider optional items
|
| | | | |
|
| |\ \ \
| |/ /
|/| | |
a-o-i: Fix broken tests from installed hosts check
|
| |/ /
| |
| |
| |
| |
| | |
With the latest changes to behavior around uninstalled hosts during a scaleup,
nosetests were broken. This updates the tests to verify that we exit when we are
expecting.
|
| |\ \
| | |
| | | |
a-o-i: Bug1329455, [quick-install] Cannot add new nodes in pre-existing env
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
a-o-i: Mapping for 3.2 Upgrades
|
| |/ / /
| | |
| | |
| | | |
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
|
| |/ / / / |
|
