feat: new section for procedures
Got started on how to init a new server
This commit is contained in:
parent
e1da7f7c9a
commit
2858674956
2 changed files with 69 additions and 2 deletions
BIN
_git.tar.gz
(Stored with Git LFS)
BIN
_git.tar.gz
(Stored with Git LFS)
Binary file not shown.
67
src/procedures/skynet/new_server.md
Normal file
67
src/procedures/skynet/new_server.md
Normal file
|
@ -0,0 +1,67 @@
|
|||
# New Server (LXC)
|
||||
|
||||
This is the instruction guide for setting up a new LXC server.
|
||||
|
||||
Rough steps are as follows:
|
||||
1. Plan the servers config
|
||||
2. Login to Proxmox
|
||||
3. Create Container using the base LXC image
|
||||
4. Grab server details
|
||||
5. Push new configuration
|
||||
|
||||
## Plan server Configuration
|
||||
To allocate he correct resources there are a few questions that need to be asked and answered.
|
||||
|
||||
1. What will this server be **For**?
|
||||
2. What will its **Name** be?
|
||||
3. What will its **IP** be?
|
||||
4. Fill the details into the tracking sheet.
|
||||
|
||||
### What is it **For**?
|
||||
What a server is for dictates what hardware resources need to be allocated.
|
||||
Is there one already existing that you can copy the configuration of?
|
||||
Do you have prior experience with what will be hosted on it?
|
||||
Is there documentation that you can use as a foundation?
|
||||
|
||||
When you know these, write it down and save for later.
|
||||
|
||||
### What is its **Name**?
|
||||
In our cluster we have a very definite naming scheme for the servers we have.
|
||||
There are two rules:
|
||||
|
||||
1. The login server (where folks have their home dirs and websites) is called Skynet.
|
||||
* [This can be traced back to 2007][server_name_skynet]
|
||||
* > By popular demand, the skynet name was retained for the login server
|
||||
2. All other servers are also named after AI's
|
||||
|
||||
|
||||
In the current cluster we tend to use groups of AI names for particular functions.
|
||||
For example:
|
||||
|
||||
* Vigil/Vendetta were AI's in the Mass effect series, pointing Shepherd forward, so they are our DNS servers
|
||||
* Glados/Wheatly from Portal, that game runs on the Source Engine, so they are our Source control servers
|
||||
* Optimus/Bumblebee from Transformers, their origin is a line of toys, so fittingly our games servers.
|
||||
* Neuromancer/Wintermute, from Neuromancer, each with multiple minds, thus became our backup (redundancy) servers.
|
||||
|
||||
If at all possible try to get the name to match its task.
|
||||
Some past names and ideas for others can be found on [the nixos wiki][server_names]
|
||||
|
||||
[server_name_skynet]: https://2009.skynet.ie/history.html
|
||||
[server_names]: https://forgejo.skynet.ie/Skynet/nixos/src/branch/main/Possible_Server_Names.md
|
||||
|
||||
|
||||
|
||||
|
||||
### What is its **IP** address?
|
||||
We have a ``/26`` allocation, so about 60 IP's we can make use of.
|
||||
Like with the names above several servers are grouped together IP wise.
|
||||
Check the [Server Inventory][server_inventory] to see what addresses are available.
|
||||
|
||||
[server_inventory]: https://forgejo.skynet.ie/Skynet/nixos/src/branch/main/ITD/Server_Inventory.csv
|
||||
|
||||
### Tracking sheet
|
||||
Now that ye have all the details about the build it is time to add them to the [Server Inventory][server_inventory].
|
||||
Add a new one, incrementing the index, and fill in the rest of the information.
|
||||
|
||||
For the IP address if the last segment (ABC in this: 193.1.99.ABC) is less than 100 then add a leading ``0`` to it.
|
||||
This is so that it can be easily sorted.
|
Loading…
Reference in a new issue