System configuration for the OpenDev Collaboratory
Go to file
Clark Boylan dd8dca09f8 Add note about python -u to external id cleanup script
This makes it easier to track progress.

Change-Id: Iaa1a9f2006bead7d400e8c21931d8768bb4ec3a0
2021-04-12 08:44:57 -07:00
doc openafs-server-config: install UserList 2021-03-30 09:49:53 +11:00
docker Merge "Upgrade gitea to 1.13.6" 2021-03-29 23:42:59 +00:00
hiera Clean up OpenEdge configuration 2021-03-31 01:42:36 +00:00
inventory Clean up OpenEdge configuration 2021-03-31 01:42:36 +00:00
kubernetes Update opendev git references in puppet modules 2019-04-20 18:26:07 +00:00
launch launch-node : cap to 8gb swap 2021-03-25 16:34:15 +11:00
manifests Merge "kerberos: switch servers to Ansible control" 2021-03-17 04:03:03 +00:00
modules/openstack_project Clean up OpenEdge configuration 2021-03-31 01:42:36 +00:00
playbooks Merge "Set MaxConnectionsPerChild 8192 for Gitea backends" 2021-04-09 02:13:34 +00:00
roles openafs-client: trim CellServDB 2021-03-02 14:36:18 +11:00
roles-test Remove Puppet 5 testing 2020-06-09 10:15:05 +10:00
testinfra Add zookeeper-statsd 2021-03-17 14:52:31 -07:00
tools Add note about python -u to external id cleanup script 2021-04-12 08:44:57 -07:00
zuul.d Merge "zuul-summary-status : handle SKIPPED and ERROR jobs" 2021-04-09 02:08:58 +00: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
bindep.txt Add libffi dev packages needed for ansible install 2016-10-04 15:20:00 -07: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
install_modules.sh Merge "Better checking for tags when cloning puppet modules" 2020-01-16 23:01:33 +00:00
install_puppet.sh Install the puppetlabs puppet package 2018-08-23 14:55:08 +10:00
modules.env Cleanup grafana.openstack.org 2020-10-29 07:59:42 +11:00
Rakefile Further changes to bring puppetboard online 2014-03-22 12:54:38 -07:00
README.rst Update README.rst 2020-09-07 17:09:36 +10:00
run_k8s_ansible.sh Invoke run_k8s_ansible from its directory 2019-05-07 16:03:59 -07:00
run_puppet.sh 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
setup.py 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.

Testing

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).

Contributing

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.

Documentation

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.