summaryrefslogtreecommitdiffstats
path: root/playbooks
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #6691 from abutcher/oc-adm-csr-cnAndrew Butcher2018-01-191-36/+5
|\ | | | | Use master group's ansible_ssh_user when accepting nodes.
| * Remove duplication in node acceptance playbook and setup master groups so ↵Andrew Butcher2018-01-161-36/+5
| | | | | | | | that we can use the first master's ansible_ssh_user when delegating.
* | Fix OpenStack readmeTomas Sedovic2018-01-191-1/+1
| | | | | | | | | | | | The ansible-playbook command in the OpenStack readme is missing a trailing backslash after the dynamic inventory. This prevents being able to copy/paste the command into the terminal and just run it as is.
* | Merge pull request #6771 from tomassedovic/fix-readmeOpenShift Merge Robot2018-01-191-5/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Drop the testing repo var from openstack readme This was introduced as a temporary fix for the origin+centos deployments. It is no longer necessary and it's confusing to newcomers.
| * | Drop the testing repo var from openstack readmeTomas Sedovic2018-01-181-5/+1
| | | | | | | | | | | | | | | | | | This was introduced as a temporary fix for the origin+centos deployments. It is no longer necessary and it's confusing to newcomers.
* | | Merge pull request #6760 from mgugino-upstream-stage/fix-docker-atomic-proxiesOpenShift Merge Robot2018-01-181-1/+1
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Ensure atomic_proxies are configured with docker In some setups, system containers may be used in conjunction with package_docker. This commit ensures that the atomic proxies are configured while using package_docker and containerized components. This commit also ensures containerized_groups are based on openshift_is_containerized instead of 'containerized' variable directly to account for possible use of atomic hosts which users may not specify containerized in inventory directly. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1535323
| * | Ensure atomic_proxies are configured with dockerMichael Gugino2018-01-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In some setups, system containers may be used in conjunction with package_docker. This commit ensures that the atomic proxies are configured while using package_docker and containerized components. This commit also ensures containerized_groups are based on openshift_is_containerized instead of 'containerized' variable directly to account for possible use of atomic hosts which users may not specify containerized in inventory directly. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1535323
* | | Merge pull request #6076 from abutcher/bz1511357Scott Dodson2018-01-171-1/+1
|\ \ \ | | | | | | | | Bug 1511357: Task "Reload generated facts" failed while scaling up containerized masters
| * | | Pull openshift_image_tag from oo_masters_to_config rather oo_first_master.Andrew Butcher2018-01-171-1/+1
| |/ /
* | | Merge pull request #6181 from mrsiano/grafanaScott Dodson2018-01-175-0/+13
|\ \ \ | | | | | | | | Add new grafana playbook.
| * | | Add new grafana playbook.Eldad Marciano2018-01-175-0/+13
| | |/ | |/| | | | | | | | | | | | | | | | this patch introduce a new playbook and roles to deploy grafana automaticly using openshift-ansible capabilities. this patch will abstract the grafana deployment process specially for openshift.
* | | Merge pull request #6744 from sosiouxme/20180115-fix-checksMichael Gugino2018-01-171-0/+1
|\ \ \ | | | | | | | | openshift_checks: repair adhoc list-checks mode
| * | | openshift_checks: repair adhoc list-checks modeLuke Meyer2018-01-161-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fixes bug https://bugzilla.redhat.com/show_bug.cgi?id=1509157 docker_image_availability.__init__ was loading a variable that of course was not defined for localhost, which is how this play runs. Fixed that. Would be nice if there were a more generic way to solve that class of problem but I can't think of anything for now that isn't worse. Also noticed that this play gathers facts for localhost. That's not necessary for what it's doing, so disabled that.
* | | | Merge pull request #6759 from mgugino-upstream-stage/etcd-upgrade-factsScott Dodson2018-01-171-1/+4
|\ \ \ \ | |_|_|/ |/| | | Add init/main.yml to etc-upgrade
| * | | Add init/main.yml to etc-upgradeMichael Gugino2018-01-171-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, etcd upgrade playbook only calls evaluate_groups to limit the number of tasks that are run against nodes during initialization. Recently, changes have been added to allow skipping of most node tasks via providing variablized host groups during initialization code. This commit allows etcd upgrades to use common init code to ensure necessary facts are defined and proper variables are sanity checked. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1527771
* | | | Merge pull request #6520 from sdodson/37-38-39Scott Dodson2018-01-178-33/+53
|\ \ \ \ | |/ / / |/| | | Faciliate 3.7 to 3.8 to 3.9 upgrade
| * | | Add call to 3.8 playbook in 3.9 upgradeScott Dodson2018-01-175-6/+53
| | | |
| * | | Remove 3.8 and 3.9 specific steps right nowScott Dodson2018-01-175-27/+0
| | | |
| * | | Exclude 3.9 packages during 3.8 upgradeScott Dodson2018-01-172-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are some obsoletes in 3.9 packages which lead yum to upgrade directly from 3.7 to 3.9 when you ask for 3.8 packages while 3.9 repos are enabled. Since we'd like to allow people to run one playbook to upgrade from 3.7 to 3.8 to 3.9 we need to exclude those packages when upgrading to 3.8
| * | | fix typosScott Dodson2018-01-172-2/+2
| | | |
* | | | Merge pull request #6714 from tomassedovic/move-openstack-inventoryOpenShift Merge Robot2018-01-172-1/+9
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Move OpenStack inventory.py out of sample-inventory This moves the dynamic inventory for OpenStack from the `sample-inventory` dir users are expected to copy and edit to `/inventory/openstack`. This will ensure that people don't use an outdated inventory as well as communicates that the inventory (similar to the playbooks and roles) is not something they are expected to modify under normal circumstances. The sample inventory will now contain only `group_vars` and as such, moving from that to providing vars explicitly is also more obvious (you replace the `-i inventory` command with `-e @vars.yaml` and you're good to go).
| * | | Document the inventory changeTomas Sedovic2018-01-161-1/+9
| | | |
| * | | Move the OpenStack dynamic inventory from sampleTomas Sedovic2018-01-161-0/+0
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | Keeping the dynamic inventory in the `sample-inventory` alongside the `group_vars` poses a problem: when we update the inventory, our users won't get the latest version. The dynamic inventory should be independent of the OpenShift or OpenStack configuration and the users should be able to either pass it explicitly or create a symlink if they want.
* | | Merge pull request #6719 from wmengRH/fix_bug_1534271Scott Dodson2018-01-161-4/+4
|\ \ \ | |/ / |/| | fix bug 1534271
| * | fix bug 1534271MENG Weihua2018-01-151-4/+4
| |/
* | Merge pull request #6692 from abutcher/cluster-operatorOpenShift Merge Robot2018-01-155-2/+49
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Separate ELB & S3 from master node group provisioning Moved s3 and elb provisioning out of `roles/openshift_aws/tasks/provisioning.yml` and into their own playbooks. These playbooks are now included in the provision playbook and in a WIP infrastructure playbook we intend to run up front in place of prerequisites. @kwoodson what are your thoughts on something like this?
| * | Add cluster-operator playbook directory.Andrew Butcher2018-01-102-0/+22
| | |
| * | Move s3 & elb provisioning into their own playbooks s.t. they are applied ↵Andrew Butcher2018-01-103-2/+27
| | | | | | | | | | | | outside of the openshift_aws master provisioning tasks.
* | | Adjust openstack provider dependencies versionsBogdan Dobrelya2018-01-151-4/+3
| | | | | | | | | | | | Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
* | | Fix openstack provider playbook name in docsBogdan Dobrelya2018-01-151-1/+1
| |/ |/| | | | | Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
* | Merge pull request #6707 from spadgett/console-upgradeScott Dodson2018-01-131-3/+9
|\ \ | | | | | | Install web console on upgrade
| * | Install web console on upgradeSamuel Padgett2018-01-111-3/+9
| | |
* | | Merge pull request #6695 from mbruzek/openstack_md_fixesOpenShift Merge Robot2018-01-121-7/+7
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Spelling and grammar changes to the advanced-configuration.md file. I noticed some spelling errors when trying to read the OpenStack `advanced_configuration.md` file so I wanted to contribute the fixed spelling.
| * | | Spelling and grammar changes to the advanced-configuration.md file.Matt Bruzek2018-01-101-7/+7
| | |/ | |/|
* | | Merge pull request #6614 from mgugino-upstream-stage/plugins-to-lib-utilsScott Dodson2018-01-111-0/+1
|\ \ \ | |_|/ |/| | Move more plugins to lib_utils
| * | Move more plugins to lib_utilsMichael Gugino2018-01-101-0/+1
| |/ | | | | | | | | | | | | This commit continues moving plugins into lib_utils. This commit does not move any plugins for add-on roles such as logging and metrics.
* | Merge pull request #6607 from tomassedovic/fix-cinder-pvOpenShift Merge Robot2018-01-113-2/+111
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Fix Cinder Persistent Volume support This documents how to use Cinder-backed persistent volumes with OpenStack. It needed a change to the dynamic inventory because the "openstack" cloudprovider plugin does actually require internal name resolution -- and the `openshift_hostname` value must match the name of the Nova server. In addition, we need to be able to specify the V2 of the Cinder API for now as described in: https://github.com/openshift/openshift-docs/issues/5730
| * | Fix typo in the advanced config docsTomas Sedovic2018-01-101-1/+1
| | |
| * | Write guide on setting up PVs with CinderTomas Sedovic2018-01-101-0/+106
| | |
| * | Allow using server names in openstack dynamic invTomas Sedovic2018-01-101-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | When deploying on OpenStack with internal DNS configured, this will set `openshift_hostname` to the Nova server name instead of its IP address. Without those two matching, the OpenStack cloud provider configuration will fail and the OpenShift nodes will not start.
| * | Specify the Cinder version in the inventoryTomas Sedovic2018-01-101-0/+1
| | | | | | | | | | | | | | | | | | | | | As described in[1], OpenShift currently only works with Block Storage API v2 and the version autodetection is failing to figure that out. [1]: https://github.com/openshift/openshift-docs/issues/5730
* | | Merge pull request #5080 from sdodson/drain-timeoutsOpenShift Merge Robot2018-01-104-11/+29
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Add the ability to specify a timeout for node drain operations A timeout to wait for nodes to drain pods can be specified to ensure that the upgrade continues even if nodes fail to drain pods in the allowed time. The default value of 0 will wait indefinitely allowing the admin to investigate the root cause and ensuring that disruption budgets are respected. In practice the `oc adm drain` command will eventually error out, at least that's what we've seen in our large online clusters, when that happens a second attempt will be made to drain the nodes, if it fails again it will abort the upgrade for that node or for the entire cluster based on your defined `openshift_upgrade_nodes_max_fail_percentage`. `openshift_upgrade_nodes_drain_timeout=0` is the default and will wait until all pods have been drained successfully `openshift_upgrade_nodes_drain_timeout=600` would wait for 600s before moving on to the tasks which would forcefully stop pods such as stopping docker, node, and openvswitch.
| * | | Add the ability to specify a timeout for node drain operationsScott Dodson2018-01-104-11/+29
| | | |
* | | | Merge pull request #6666 from sdodson/fix_client_binaryScott Dodson2018-01-103-3/+8
|\ \ \ \ | | | | | | | | | | Ensure that openshift_facts role is imported whenever we rely on
| * | | | Ensure that openshift_facts role is imported whenever we rely onScott Dodson2018-01-093-3/+8
| | | | | | | | | | | | | | | | | | | | openshift_client_binary
* | | | | Merge pull request #6647 from ↵Scott Dodson2018-01-101-4/+4
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | vrutkovs/3.9-upgrades-remove-openshift.common.service_type 3.9 upgrade: remove openshift.common.service_type
| * | | | | 3.9 upgrade: remove openshift.common.service_typeVadim Rutkovsky2018-01-081-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | See eb6b20fc9183cc2aae424c72efd1191b99110a93
* | | | | | Add defaults for openshift_pkg_versionMichael Gugino2018-01-101-2/+2
| |_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This variable may or may not be defined by the users. During deployments, it will be set to '-{{ openshift_version }}' if undefined. During upgrades, it will remain undefined. This commit ensures that if the variable is undefined, empty strings '' are set.
* | | | | Merge pull request #6674 from mgugino-upstream-stage/remove-becomes2Scott Dodson2018-01-1013-20/+17
|\ \ \ \ \ | | | | | | | | | | | | Remove become statements
| * | | | | Chmod temp dirs created on localhostMichael Gugino2018-01-094-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After remove become:no statements on local_action tasks, we need to ensure that the proper file permssions are applied to local temp directories. This reason for this is that the 'fetch' module does not use 'become' for the localhost, just the remote host. Additionally, users may not wish for the localhost to become during a fetch. local_action will execute with whatever permissions are specified in inventory or via cli.