System configuration for the OpenDev Collaboratory
Go to file
Ian Wienand 7de885b5ee Cleanup
This was retired with I8a31f8fcf9b3064c0ae58e463a6014dc14b518a7

Change-Id: Ieafac856b0feb91f41f05084aa669e2ccb92569d
2021-06-08 14:35:28 +10:00
doc Cleanup 2021-06-08 14:35:28 +10:00
docker Update our documentation to reflect the move to OFTC 2021-05-31 15:26:58 +02:00
hiera Cleanup 2021-06-08 14:35:28 +10:00
inventory Cleanup 2021-06-08 14:35:28 +10:00
kubernetes Update opendev git references in puppet modules 2019-04-20 18:26:07 +00:00
launch Fix min swap value in 2021-05-14 14:09:11 -07:00
manifests Cleanup 2021-06-08 14:35:28 +10:00
modules/openstack_project Cleanup 2021-06-08 14:35:28 +10:00
playbooks Move gerritbot/accessbot to new eavesdrop server 2021-06-08 08:16:56 +10:00
roles Remove obsolete Bazel spawn strategies 2021-05-07 11:06:15 +10:00
roles-test system-config-roles: only match jobs on roles tested 2021-05-07 11:05:21 +10:00
testinfra Merge "Move gerritbot/accessbot to new eavesdrop server" 2021-06-08 04:23:45 +00:00
tools Add note about python -u to external id cleanup script 2021-04-12 08:44:57 -07:00
zuul.d Move gerritbot/accessbot to new eavesdrop server 2021-06-08 08:16:56 +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 Assort IRC TODOs 2021-05-29 17:18:55 +00: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 puppet things from zuul where we don't puppet anymore 2021-05-21 17:03:08 -07: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 Stop running ansible-lint on this repo 2021-02-09 22:08:38 +00: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 on OFTC 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.