046aad9276
When we restarted Gerrit recently there were a number of caches that were over their default max sizes so were pruned. Gerrit prunes daily at 0100 or when restarted. This gives us a good indication for which caches are currently configured to be too small for typically operation as we restarted several hours before 0100. All of the logged cache pruning can be found in this paste [0]. Many of these caches were floating around their configured maximum and we leave them alone. However four related caches are well above their default max which is a good indication we need to increase their sizes. The four are identified below with their documented purpose/function from the upstream docs [1]: * cache "git_modified_files" Each item caches the list of git modified files between two git trees corresponding to two different commits. This cache does not read the actual file contents nor does it include the edits (modified regions) of the files. * cache "modified_files" Each item caches the list of modified files between two commits. This cache is similar to the git_modified_files cache but performs extra logic including filtering out files that are untouched by both commits because they were purely modified between the parent commits. * cache "git_file_diff" Each item caches the pure git diff between two git trees for a specific file path. The diff includes all the file attributes (old/new paths, change/patch types) as well as the list of edits corresponding to the modified regions in the file. * cache "gerrit_file_diff" Each item caches the diff between two git commits for a specific file path. This cache is similar to the git_file_diff cache but performs extra logic including identifying the edits that are due to rebase. The diff for the "commit message" and "merge list" can also be requested from this cache. Entries in this cache are relatively large, so memoryLimit is an estimate in bytes of memory used. Administrators should try to target cache.diff.memoryLimit to fit all changes users will view in a 1 or 2 day span. The same applies for other diff caches: "git_modified_files", "modified_files" and "git_file_diff". The note at the end of cache "gerrit_file_diff" is what we use to determine these new sizes though we're more conservative with the memory limits (default of which is 10m for each of these caches) as memory is more scarce than disk. [0] https://paste.opendev.org/show/bk4pTIuQLCsWaF3dVVF7/ [1] https://gerrit-review.googlesource.com/Documentation/config-gerrit.html#cache Change-Id: I521b53c130892fc2152586da1c4858ea4099479f
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.
The files in this repository are provided as an opinionated example service deployment, and to allow the OpenDev Collaboratory to use public software development workflows in order to coordinate changes and improvements to the systems it runs. This repository is not intended as a reconsumable project on its own, and anyone wishing to adjust it to suit their own needs should do so with a fork. The system-config reviewers are unable to evaluate and support use cases for the contents here other than their own.
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. Please remember that this repository consists of configuration and orchestration for OpenDev Collaboratory production systems, so contributions to it will be evaluated on the basis of whether they're useful or applicable to OpenDev's services. Changes intended to make the contents more easily reusable outside OpenDev itself are not in scope, and so will be rejected by reviewers.
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.
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.