|Tom Hughes 709c582dd5 Configure weighted plugin for gdnsd||18 hours ago|
|cookbooks||18 hours ago|
|hooks||2 years ago|
|roles||2 days ago|
|test||2 years ago|
|.dockerignore||6 months ago|
|.editorconfig||1 month ago|
|.gitignore||3 years ago|
|.kitchen.provision.rb||3 years ago|
|.kitchen.yml||2 years ago|
|.mailmap||9 months ago|
|.rubocop.yml||2 months ago|
|.rubocop_todo.yml||1 week ago|
|.ruby-version||6 months ago|
|.travis.yml||2 months ago|
|CONTRIBUTING.md||5 years ago|
|Dockerfile||1 week ago|
|Gemfile||2 months ago|
|Gemfile.lock||1 week ago|
|LICENSE||1 year ago|
|README.md||7 months ago|
This repository manages the configuration of all the servers run by the OpenStreetMap Foundation’s Operations Working Group. We use Chef to automated the configuration of all of our servers.
We make extensive use of roles to configure the servers. In general we have:
These deal with particular setup or quirks of a server, such as its IP address. They also include roles representing the service they are performing, and the location they are in and any particular hardware they have that needs configuration. All our servers are named after dragons.
Covers anything specific to a certain piece of hardware, like a motherboard, that could apply to multiple machines.
These form a hierarchy of datacentres, organisations, and countries where our servers are located.
These cover the services that the server is running, and will include the recipes required for that service along with any specific configurations and other cascading roles.
We use the ‘Organization Repository’ approach, where we have all our cookbooks in this repository (as opposed to one repository per cookbook). Additionally we don’t make use of external cookbooks so every cookbook required is in this repository.
Contributions are welcome! Please see CONTRIBUTING.md for more details.