| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Cleanup not required dns bits
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Do not manage hostnames for openstack cloud provider,
let cloud-init to do its job.
* Make python-dns / dnspython dependency check conditional.
* Drop not used dns node flavor and image.
* Do not manage dns nodes and sec groups in heat stacks.
* Keep supporting dynamic updates for private DNS records, yet only
limited to an external DNS managed elsewhere (not deployed by
the openshift_openstack provider). So users may still benefit from
this feature, sending nsupdates to private and public servers as
they want it.
* Fix openstack default for external nsupdate keys. It should be
undefined by default as the dns-populate logic is based on that.
* Fix dns records generation for openstack provider's populate-dns
* Update docs
|
|\ \
| | |
| | | |
Add missing symlinks in openshift-logging
|
| | | |
|
|\ \ \
| | | |
| | | | |
Remove entry point files no longer needed by CI
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
Remove duplicate init import in network_manager.yml
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | | |
Remove all references to pacemaker (pcs, pcsd) and openshift.master.cluster_method.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
openshift.master.cluster_method.
With pacemaker removed there is no longer a need for
openshift.master.cluster_method. We only have one option.
|
|\ \ \
| | | |
| | | | |
Playbook Consolidation - openshift-logging
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Fix hosted vars
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Remove hosted vars from openshift_facts.
The current pattern is causing a bunch of undesired sideffects.
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
Fix oreg_auth_credentials_create register var
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
There is a variable collision for the *oreg_auth_credentials_create
variables in openshift_master and openshift_node registry_create
tasks.
This commit ensures standard and alternative oreg auth
credential placement tasks don't use the same register
variable.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1520866
|
|\ \ \ \
| |/ / /
|/| | | |
Cleanup unused openstack provider code
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove references for bastion, ssh UI tunnek and static inventory.
Update docs.
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
|
|\ \ \ \
| | | | |
| | | | | |
Use openshift testing repos for openstack
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Use testing openshift repos to sidestep packaging issues for 3.6 clients being
used in 3.7 deployments or something.
Poke host requirements Centos 7.4 as 7.3 can't see that testing repo.
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
Implement container runtime role
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Automatic merge from submit-queue.
Playbook Consolidation - Redeploy Certificates
This PR moves the certificate redeploy playbooks out of {byo,common}/openshift-cluster and into their respective component areas.
- playbooks/openshift-etcd (redeploy-certificates.yml, redeploy-ca.yml)
- playbooks/openshift-master (redeploy-certificates.yml, redeploy-openshift-ca.yml)
- playbooks/openshift-node (redeploy-certificates.yml)
- playbooks/openshift-hosted (redeploy-registry-certificates.yml, redeploy-router-certificates.yml)
playbooks/byo/openshift-cluster/redeploy-certificates.yml was moved to
playbooks/redeploy-certificates.yml
Trello: https://trello.com/c/zCz6RIHM/578-2-playbook-consolidation-openshift-cluster-redeploy-certificates
|
| | | | | | |
|
|\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
Allow number of retries in openshift_management to be configurable
|
| | |_|/ /
| |/| | | |
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Add v3.9 support
|
| | |_|/
| |/| | |
|
| | | | |
|
|\ \ \ \
| |_|_|/
|/| | | |
Initial upgrade for scale groups.
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
Bug 1512793- Fix idempotence issues in ASB deploy
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Add support for annotations in oc_service
- Use oc_service instead of oc_obj
- Use oc_pvc instead of oc_obj
- Work around lack of idempotency for oc_obj DeploymentConfig
|
|\ \ \ \
| | | | |
| | | | | |
Bug 1514417 - Adding correct advertise-client-urls
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
storage_glusterfs: fix typo
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
retry package operations
|
| | |_|_|_|/
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When a package install/update fails due to network blips or other spotty
availability, retry it. If the failure is a real failure (e.g. package
is really not there) it still fails after 3 tries (Ansible default).
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
Fix glusterfs checkpoint info
|
| |/ / / / |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Do not escalate privileges in jks generation tasks
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Correct usage of include_role
|
| | | | |
| | | | |
| | | | |
| | | | | |
Switch to import_role for some required roles.
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
Use IP addresses for OpenStack nodes
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Unlike other cloud providers, OpenStack VMs are not able to resolve each
other by their names. If you try to run the playbooks against nodes
without a pre-created /etc/hosts or a DNS that provides the hostname/ip
resolution, it will fail.
By setting the `openshift_hostname` variable to each node's IP address,
we're able to deploy a functional cluster without running a custom DNS.
It is still possible to provide an external server with nsupdate keys
and have it be populated, but that is no longer a hard requirement.
|