System configuration for the OpenDev Collaboratory
Go to file
Ian Wienand eb07ab3613 borg-backup: add fuse
Add the FUSE dependencies for our hosts backed up with borg, along
with a small script to make mounting the backups easier.  This is the
best way to recover something quickly in what is sure to be a
stressful situation.

Documentation and testing is updated.

Change-Id: I1f409b2df952281deedff2ff8f09e3132a2aff08
2020-11-05 11:56:46 +11:00
doc borg-backup: add fuse 2020-11-05 11:56:46 +11:00
docker Update to gitea 1.12.4 2020-09-24 11:12:00 +10:00
hiera Cleanup 2020-10-29 07:59:42 +11:00
inventory Merge "RAX DFW/IAD : add internal mirror DNS to cert" 2020-11-04 03:28:57 +00:00
kubernetes Update opendev git references in puppet modules 2019-04-20 18:26:07 +00:00
launch Merge "Wait for ipv6 addrs when launching nodes" 2020-09-22 19:39:14 +00:00
manifests Cleanup 2020-10-29 07:59:42 +11:00
modules/openstack_project Merge "Add service-incident@opendev mailing list" 2020-10-30 15:37:51 +00:00
playbooks borg-backup: add fuse 2020-11-05 11:56:46 +11:00
roles Gerrit image cleanups/fixes 2020-08-11 13:15:06 -07:00
roles-test Remove Puppet 5 testing 2020-06-09 10:15:05 +10:00
testinfra borg-backup: add fuse 2020-11-05 11:56:46 +11:00
tools Install older setuptools in puppet apply jobs 2020-09-01 13:59:21 -07:00
zuul.d Merge "ARM64 : run base test on Focal too" 2020-10-28 03:57:05 +00:00
.ansible-lint Work around new ansible lint errors. 2020-08-20 12:55:46 +10:00
.gitignore Ignore ansible .retry files 2016-07-15 12:04:48 -07:00
.gitreview OpenDev Migration Patch 2019-04-19 19:26:05 +00:00
COPYING.GPL Add yamlgroup inventory plugin 2018-11-02 08:19:53 +11:00
Gemfile Update some paths for opendev 2019-04-20 09:31:14 -07:00
README.rst Update README.rst 2020-09-07 17:09:36 +10:00
Rakefile Further changes to bring puppetboard online 2014-03-22 12:54:38 -07:00
bindep.txt Add libffi dev packages needed for ansible install 2016-10-04 15:20:00 -07:00 Merge "Better checking for tags when cloning puppet modules" 2020-01-16 23:01:33 +00:00 Install the puppetlabs puppet package 2018-08-23 14:55:08 +10:00
modules.env Cleanup 2020-10-29 07:59:42 +11:00 Invoke run_k8s_ansible from its directory 2019-05-07 16:03:59 -07:00 Clean up bashate failures 2014-09-30 12:40:59 -07:00
setup.cfg Mention new mailing lists 2020-04-06 18:19:28 +00:00 Update to openstackdocstheme 2018-06-25 11:19:43 +10:00
tox.ini tox: drop test-requirements.txt 2020-08-25 08:41:44 +10:00


OpenDev System Configuration

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 docker/.

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 manifests and modules.


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.

Continuous Deployment

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

That documentation is generated from this repository. You can geneate it yourself with tox -e docs.