System configuration for OpenStack Infrastructure
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
smarcet 2f970563c0 OpenstackId config updates 21 hours ago
doc docs: Update some of sysadmin details 2 weeks ago
docker Explain "why opendev" on opendev.org index page 2 weeks ago
hiera Merge "Remove mirror01.regionone.linaro-us.opendev.org" 4 days ago
inventory Remove nb04 3 days ago
kubernetes Update opendev git references in puppet modules 1 year ago
launch launch: move old scripts out of top-level 2 weeks ago
manifests OpenstackId config updates 21 hours ago
modules/openstack_project OpenstackId config updates 21 hours ago
playbooks letsencrypt: Fix graphite02 restart handler 1 day ago
roles Gerrit image cleanups/fixes 1 month ago
roles-test Remove Puppet 5 testing 3 months ago
testinfra Remove nb04 3 days ago
tools Install older setuptools in puppet apply jobs 2 weeks ago
zuul.d Remove nb04 3 days ago
.ansible-lint Work around new ansible lint errors. 1 month ago
.gitignore Ignore ansible .retry files 4 years ago
.gitreview OpenDev Migration Patch 1 year ago
COPYING.GPL Add yamlgroup inventory plugin 1 year ago
Gemfile Update some paths for opendev 1 year ago
README.rst Update README.rst 2 weeks ago
Rakefile Further changes to bring puppetboard online 6 years ago
bindep.txt Add libffi dev packages needed for ansible install 4 years ago
install_modules.sh Merge "Better checking for tags when cloning puppet modules" 8 months ago
install_puppet.sh Install the puppetlabs puppet package 2 years ago
modules.env Stop cloning more puppet modules 3 months ago
run_k8s_ansible.sh Invoke run_k8s_ansible from its directory 1 year ago
run_puppet.sh Clean up bashate failures 6 years ago
setup.cfg Mention new mailing lists 5 months ago
setup.py Update to openstackdocstheme 2 years ago
tox.ini tox: drop test-requirements.txt 4 weeks ago

README.rst

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.