Instead of it being the first master hostname in the single-master scenario or the first load balancer mostname in multi-master, the sample cluster will always have the following entrypoint by default: https://console.{{env_id}}.{{public_dns_domain}}:8443 That will simplify the documentation and be easier to look up and understand for the newcomers trying it out.
OpenShift and Atomic Platform Ansible Contrib
This repository contains unsupported code that can be used in conjunction with the openshift-ansible repository, namely:
- additional roles for OpenShift deployment
- code for provisioning various cloud providers (GCP, AWS, VMware, Azure, OpenStack and Red Hat Virtualization (RHV) / oVirt)
- supporting scripts and playbooks for the various reference architectures Red Hat has published
Contributing
If you're submitting a pull request or doing a code review, please take a look at our contributing guide.
Running tests locally
We use tox to manage virtualenvs and run tests. Alternatively, tests can be run using detox which allows for running tests in parallel
pip install tox detox
List the test environments available:
tox -l
Run all of the tests with:
tox
Run all of the tests in parallel with detox:
detox
Running a particular test environment (python 2.7 flake8 tests in this case):
tox -e py27-ansible22-flake8
Running a particular test environment in a clean virtualenv (python 3.5 yamllint tests in this case):
tox -r -e py35-ansible22-yamllint
If you want to enter the virtualenv created by tox to do additional testing/debugging (py27-flake8 env in this case):
source .tox/py27-ansible22-flake8/bin/activate