The usptream haproxy image switched to running as a user, rather than as root. This means it can not bind to 80/443 and instantly dies. I've added a comment with some discussion, but for now, use the root user. 
|2 days ago|
|doc||2 weeks ago|
|docker||6 days ago|
|hiera||5 days ago|
|inventory||5 days ago|
|kubernetes||2 years ago|
|launch||4 days ago|
|manifests||7 days ago|
|modules/openstack_project||7 days ago|
|playbooks||2 days ago|
|roles||2 weeks ago|
|roles-test||2 weeks ago|
|testinfra||5 days ago|
|tools||1 month ago|
|zuul.d||4 days ago|
|.gitignore||5 years ago|
|.gitreview||2 years ago|
|COPYING.GPL||3 years ago|
|Gemfile||2 years ago|
|README.rst||8 months ago|
|Rakefile||7 years ago|
|bindep.txt||5 years ago|
|install_modules.sh||1 year ago|
|install_puppet.sh||3 years ago|
|modules.env||7 months ago|
|run_k8s_ansible.sh||2 years ago|
|run_puppet.sh||7 years ago|
|setup.cfg||1 year ago|
|setup.py||3 years ago|
|tox.ini||3 months ago|
This is the machinery that drives the configuration, testing, continuous integration and deployment of services provided by the OpenDev project.
Services are driven by Ansible playbooks and associated roles stored here. If you are interested in the configuration of a particular service, starting at
playbooks/service-<name>.yaml will show you how it is configured.
Most services are deployed via containers; many of them are built or customised in this repository; see
A small number of legacy services are still configured with Puppet. Although the act of running puppet on these hosts is managed by Ansible, the actual core of their orchestration lives in
OpenDev infrastructure runs a complete testing and continuous-integration environment, powered by Zuul.
Any changes to playbooks, roles or containers will trigger jobs to thoroughly test those changes.
Tests run the orchestration for the modified services on test nodes assigned to the job. After the testing deployment is configured (validating the basic environment at least starts running), specific tests are configured in the
testinfra directory to validate functionality.
Once changes are reviewed and committed, they will be applied automatically to the production hosts. This is done by Zuul jobs running in the
deploy pipeline. At any one time, you may see these jobs running live on the status page or you could check historical runs on the pipeline results (note there is also an
opendev-prod-hourly pipeline, which ensures things like upstream package updates or certificate renewals are incorporated in a timely fashion).
Contributions are welcome!
You do not need any special permissions to make contributions, even those that will affect production services. Your changes will be automatically tested, reviewed by humans and, once accepted, deployed automatically.
Bug fixes or modifications to existing code are great places to start, and you will see the results of your changes in CI testing.
You can develop all the playbooks, roles, containers and testing required for a new service just by uploading a change. Using a similar service as a template is generally a good place to start. If deploying to production will require new compute resources (servers, volumes, etc.) these will have to be deployed by an OpenDev administrator before your code is committed. Thus if you know you will need new resources, it is best to coordinate this before review.
The #opendev IRC channel is the main place for interactive discussion. Feel free to ask any questions and someone will try to help ASAP. The OpenDev meeting is a co-ordinated time to synchronize on infrastructure issues. Issues should be added to the agenda for discussion; even if you can not attend, you can raise your issue and check back on the logs later. There is also the service-discuss mailing list where you are welcome to send queries or questions.
The latest documentation is available at https://docs.opendev.org/opendev/system-config/latest/
That documentation is generated from this repository. You can geneate it yourself with
tox -e docs.