| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| | |
Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
|
|/
|
|
|
|
|
|
| |
The correct name is "enabled', not "basicAuditEnabled"
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1439619
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change allows for the use of either the traditional package install
of docker OR a system container install of docker.
Two new inventory options, openshift_docker_use_system_container and
openshift_docker_systemcontainer_image_registry_override, have been
added which are be used to install with a system container. By default
this option is commented out.
One new fact has been added:
- docker.service_name: docker by default, container-engine-docker
for system container
|
| |
|
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| | |
Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
|
|/ |
|
| |
|
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In openshift_repos and everywhere, ensure deployment_type and
openshift_deployment_type are defined and the same.
We really want to set openshift_deployment_type, but users will likely
still have just deployment_type, so accept both. And don't make every
playbook default openshift_deployment_type to deployment_type.
This introduces the openshift_sanitize_inventory role to run before anything else.
|
| | |
|
|/ |
|
| |
|
|\
| |
| | |
Merged by openshift-bot
|
| | |
|
| | |
|
|\ \
| |/
|/| |
Merged by openshift-bot
|
| | |
|
|\ \
| |/
|/| |
Merged by openshift-bot
|
| |
| |
| |
| |
| | |
Add parameters to allow overriding minTLSVersion and
cipherSuites in master and node servingInfo config stanzas.
|
| | |
|
|/ |
|
| |
|
| |
|
|\
| |
| | |
Reverting commit 3257 and renaming master_url to openshift_logging_ma…
|
| |
| |
| |
| | |
playbooks
|
| | |
|
|/
|
|
|
|
| |
openshift_cockpit_deployer_version
Fixes Bug 1393666
|
|\
| |
| | |
Copies CloudFront pem file to registry hosts
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change copies the CloudFront private key to registry hosts when
the provider is set to s3 and CloudFront baseurl, privatekey, and
keyparid are all provided. It also adds the following variable
examples in the host inventory files:
- openshift_hosted_registry_storage_s3_cloudfront_baseurl
- openshift_hosted_registry_storage_s3_cloudfront_privatekeyfile
- openshift_hosted_registry_storage_s3_cloudfront_keypairid
See https://bugzilla.redhat.com/show_bug.cgi?id=1395168
|
|\ \
| |/
|/| |
fixes 1417261. Points playbooks to the correct 3.5 roles for logging …
|
| | |
|
|\ \
| | |
| | | |
Restructure certificate redeploy playbooks
|
| |/ |
|
|/ |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Begin requiring Docker 1.12.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Building off the work done for Docker 1.10, we now require Docker 1.12
by default.
The upgrade process was already set to ensure you are running the latest
docker during upgrade, and the standalone docker upgrade playbook can
also be used if desired.
As before, you can override this Docker 1.12 requirement by setting a
docker_version=1.10.3 (or similar), and you can skip the default to
upgrade docker by setting docker_upgrade=False.
|
| |
| |
| |
| | |
libviert -> libvirt
|
|\ \
| | |
| | | |
Update aws dynamic inventory
|
| | |
| | |
| | |
| | | |
Fetch from https://raw.githubusercontent.com/ansible/ansible/devel/contrib/inventory/ec2.py
|
| | |
| | |
| | |
| | | |
Fetch from https://raw.githubusercontent.com/ansible/ansible/devel/contrib/inventory/gce.py
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Move pylint tests to tox
- Move yamllint tests to tox
- Create separate tox config (and setup.py) for root
- bump ansible requirement
- unify pylint config
- add docs
- remove git directory containing old testing tools
- install python-six if not present for openshift-facts
- add python-six as a dependency for openshift-ansible-utils
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
strict-order forces dnsmasq to iterate through nameservers in order. If one of
the nameservers is down this will slow things down while dnsmasq waits for a
timeout. Also, this option prevents dnsmasq from querying other nameservers if
the first one returns a negative result. While I think it's odd to have a
nameserver that returns negative results for a query that another returns
positive results for this does seem to fix the issue in testing.
Fixes Bug 1399577
|