3 | | Our server map is now in svn. We have both a [browser:trunk/admin/servers-available directory listing] and a [browser:trunk/admin/diagrams series of diagrams]. |
4 | | |
5 | | Each server is represented by a directory. Inside each directory are both files and sub-directories denoting properties of that server. |
6 | | |
7 | | In addition, in [browser:trunk/admin/tags the admin/tags] directory, we have further classified servers by tags. |
8 | | |
9 | | In the [browser:trunk/admin/scripts scripts] directory are a number of scripts that make use of the server database. |
10 | | |
11 | | In the [browser:trunk/admin/directives directives] directory are some automated tasks that can be run with the scripts/execute-directive script. |
12 | | |
13 | | == Checking out the repository == |
14 | | |
15 | | You can check out the entire repository with: |
16 | | |
17 | | {{{ |
18 | | svn co https://svn.mayfirst.org/mfpl/trunk/admin |
19 | | }}} |
20 | | |
21 | | Or, if you have write access: |
22 | | |
23 | | {{{ |
24 | | svn co svn+ssh://mfpl@svn.mayfirst.org/trunk/admin |
25 | | }}} |
26 | | |
27 | | == Adding a new server == |
28 | | |
29 | | A [wiki:add_server_to_server_svn_db separate page describes how to add a new server]. |
30 | | |
31 | | == Tags vs. Properties == |
32 | | |
33 | | In general, we use properties to define characteristics of servers. When we need to define a characteristic that is either too complicated to be conveyed in a simple property name (like the standard tag which identifies the servers which directly host members web sites and email accounts) or temporary (like tagging servers for upgrades), we use tags. |
| 3 | [[Include(puppet)]] |