summaryrefslogtreecommitdiffstats
path: root/playbooks
Commit message (Collapse)AuthorAgeFilesLines
* Flush handlers before marking a node schedulable after upgrade.Devan Goodwin2016-09-091-0/+2
| | | | | | Handlers normally only trigger at the end of the play, but in this case we just set our node schedulable again resulting in it immediately getting taken down again.
* Don't loop over hostvars when setting node schedulability.Andrew Butcher2016-09-071-1/+0
|
* Merge pull request #2409 from abutcher/secure-registryScott Dodson2016-09-041-1/+83
|\ | | | | Secure registry for atomic registry deployment
| * Secure registry for atomic registry deployment (deployment_subtype=registry).Andrew Butcher2016-09-021-1/+83
| |
* | Record schedulability of node prior to upgrade and re-set it to thatScott Dodson2016-09-021-1/+13
| | | | | | | | | | | | | | Previously we were setting schedulability to the state defined in the inventory without regard to whether or not it was manually made schedulable or unschedulable. The right thing seems to be to record the state prior to upgrade and set it back.
* | Fix ops/qps typoJordan Liggitt2016-09-022-3/+3
| |
* | Merge pull request #2313 from mdanter/unschedulableMasterAsNodeScott Dodson2016-09-011-1/+1
|\ \ | | | | | | In AWS where the master node was not part of the nodes and unschedulable
| * | This fixes an issue in AWS where the master node was not part of the nodes ↵Matyas Danter2016-08-301-1/+1
| | | | | | | | | | | | in an unschedulable way
* | | Merge pull request #2347 from brenton/BZ1369410Scott Dodson2016-09-011-16/+18
|\ \ \ | |_|/ |/| | Bug 1369410 - uninstall fail at task [restart docker] on atomic-host
| * | Bug 1369410 - uninstall fail at task [restart docker] on atomic-hostBrenton Leanhardt2016-08-231-16/+18
| | | | | | | | | | | | | | | | | | | | | | | | * Moved the restarting of docker and network services lower. * Added /etc/systemd/system/docker.service.d/docker-sdn-ovs.conf to the list of files to be removed (I suspect the RPM uninstall handles this for non-containerized installs) * sorted the file names
* | | Add flannel package removal in uninstallation playbookManjunath A Kumatagi2016-09-011-0/+5
| | |
* | | Reload docker facts after upgrading dockerScott Dodson2016-08-301-0/+4
| |/ |/|
* | Merge pull request #2366 from Mangirdaz/masterJason DeTiberus2016-08-261-0/+9
|\ \ | | | | | | add run_once to repeatable actions
| * | add check for server and account already existMangirdas2016-08-261-0/+4
| | |
| * | add run_once to repeatable actionsMangirdas2016-08-261-0/+5
| | |
* | | Remove atomic check and cockpit.socketSamuel Munilla2016-08-263-3/+3
| | |
* | | Re-organize registry-console deployment.Andrew Butcher2016-08-262-2/+3
| | |
* | | Add support for Atomic Registry InstallsSamuel Munilla2016-08-262-1/+4
| | | | | | | | | | | | Add the Registry deployment subtype as an option in the quick installer.
* | | Merge pull request #2052 from sdodson/metricsScott Dodson2016-08-254-1/+37
|\ \ \ | | | | | | | | Metrics improvements
| * | | Deploy metrics after our routerScott Dodson2016-08-241-1/+1
| | | | | | | | | | | | | | | | | | | | Metrics deployer now checks for route activation. As such we need a router before we install metrics.
| * | | Pull in keynote demo changesScott Dodson2016-08-241-0/+6
| | | |
| * | | [tags] add some support for running a subset of config via tagsJason DeTiberus2016-08-243-0/+30
| | | |
* | | | Merge pull request #2337 from mkumatag/rm_dup_flannel_regAndrew Butcher2016-08-251-10/+0
|\ \ \ \ | | | | | | | | | | Remove duplicate flannel registration
| * | | | Fix review commentsManjunath A Kumatagi2016-08-221-8/+2
| | | | |
| * | | | Remove duplicate flannel registrationManjunath A Kumatagi2016-08-211-4/+0
| | | | |
* | | | | don't gather facts when bootstrapping ansible for Fedora hostsAdam Miller2016-08-241-0/+1
| | | | | | | | | | | | | | | | | | | | Signed-off-by: Adam Miller <maxamillion@fedoraproject.org>
* | | | | Fix upgrade failure when master-config does not have pluginOrderOverride.Devan Goodwin2016-08-241-0/+1
| |/ / / |/| | |
* | | | Merge pull request #2339 from dgoodwin/plugin-order-warningScott Dodson2016-08-231-0/+13
|\ \ \ \ | | | | | | | | | | Add warning at end of 3.3 upgrade if pluginOrderOverride is found.
| * | | | Add warning at end of 3.3 upgrade if pluginOrderOverride is found.Devan Goodwin2016-08-221-0/+13
| | | | |
* | | | | Don't run node config upgrade hook if host is not a node.Devan Goodwin2016-08-231-1/+1
| |_|_|/ |/| | |
* | | | Merge pull request #2340 from lhuard1A/ansible_virt_moduleJason DeTiberus2016-08-225-41/+34
|\ \ \ \ | | | | | | | | | | Replace some virsh commands by native virt_XXX ansible module
| * | | | Replace some virsh commands by native virt_XXX ansible moduleLénaïc Huard2016-08-225-41/+34
| | | | |
* | | | | Merge pull request #2336 from sdodson/etcd-uninstallScott Dodson2016-08-221-1/+4
|\ \ \ \ \ | |/ / / / |/| | | | Fix etcd uninstall
| * | | | Fix etcd uninstallScott Dodson2016-08-191-1/+4
| | | | |
* | | | | Merge pull request #2330 from lhuard1A/open_node_portsJason DeTiberus2016-08-193-0/+14
|\ \ \ \ \ | | | | | | | | | | | | Open OpenStack security group for the service node port range
| * | | | | Open OpenStack security group for the service node port rangeLénaïc Huard2016-08-193-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | | Merge pull request #2329 from lhuard1A/fix_nodeonmasterJason DeTiberus2016-08-191-1/+1
|\ \ \ \ \ \ | |_|/ / / / |/| | | | | Fix the “node on master” feature
| * | | | | Fix the “node on master” featureLénaïc Huard2016-08-191-1/+1
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | What we want to do is to add the master as a node if: * `g_nodeonmaster` is set to true, and * we are not in the case where we want to add new nodes. The second test was done by only checking whether `g_new_node_hosts` was defined. This was wrong because, in all cloud-provider setups, this variable was set with the default value of “empty list” (`[]`). The test has been changed to use the `bool` filter so that it correctly evaluates to false (and hence, effectively add the master as a node) when `g_new_node_hosts` is the empty list.
* | | | | Merge pull request #2331 from dgoodwin/docker-upgrade-symlinkScott Dodson2016-08-191-0/+1
|\ \ \ \ \ | | |/ / / | |/| | | Fix standalone Docker upgrade missing symlink.
| * | | | Fix standalone Docker upgrade missing symlink.Devan Goodwin2016-08-191-0/+1
| | | | |
* | | | | Fix warnings in OpenStack provider with ansible 2.1Lénaïc Huard2016-08-193-22/+24
| |/ / / |/| | | | | | | | | | | Some expressions now need to be enclosed inside `{{…}}`.
* | | | Update uninstall.ymlScott Dodson2016-08-171-1/+1
| |/ / |/| | | | | Fixes #2317
* | | Reconcile roles after master upgrade, but before nodes.Devan Goodwin2016-08-161-43/+46
|/ / | | | | | | | | | | | | | | | | | | 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.
* | Merge pull request #2220 from jkhelil/fix_key_error_when_ssh_failingScott Dodson2016-08-161-1/+1
|\ \ | | | | | | fixing openshift key error in case of node failure during run (ssh is…
| * | fixing openshift key error in case of node failure during run (ssh issue)jawed2016-08-091-1/+1
| | |
* | | Reference tmpdir from first master hostvars when evacuating nodes.Andrew Butcher2016-08-111-4/+4
| | |
* | | Merge pull request #2285 from dgoodwin/nuke-images-2Scott Dodson2016-08-114-20/+59
|\ \ \ | | | | | | | | Improvements for Docker 1.10+ Upgrade Image Nuking
| * | | Improvements for Docker 1.10+ upgrade image nuking.Devan Goodwin2016-08-114-20/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | Shutdown Docker before upgrading the rpm.Devan Goodwin2016-08-101-0/+4
| |/ / | | | | | | | | | | | | This avoids the automatic image migration in 1.10, which can take a very long time and potentially cause rpm db corruption.
* / / Support for redeploying certificates.Andrew Butcher2016-08-113-1/+270
|/ /
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-24 12:11:53 +0000