Changes
Page history
Add information about Rhizome.
authored
Dec 19, 2022
by
Flancian
Hide whitespace changes
Inline
Side-by-side
tech-working-group/Infrastructure-overview.md
View page @
0f40c9db
...
@@ -9,12 +9,18 @@
...
@@ -9,12 +9,18 @@
## B. Infrastructure
## B. Infrastructure
We have a dedicated server on Hetzner:
As of 2022-12-18 we have two dedicated servers on Hetzner: Runko (95.216.13.24) and Rhizome (65.109.113.162).
*
32GB RAM (4x RAM 8192 MB DDR3)
*
i7-4770 CPU @ 3.40GHz).
*
2x 250 GB disks (SSD)
Disks are arranged as:
### Runko
Our primary server as of the time of writing; meaning it hosts PostgreSQL, Redis and our Mastodon instance.
*
Hostname: runko.social.coop
*
32GB RAM (4x RAM 8192 MB DDR3)
*
i7-4770 CPU @ 3.40GHz).
*
2x 250 GB disks (SSD, in a striped setup -- not mirrored)
Disks are arranged as follows (run
`sudo pvs`
,
`sudo vgs`
,
`sudo lvs`
in the server for live information):
```
```
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
...
@@ -40,6 +46,15 @@ Using LVM such that we have:
...
@@ -40,6 +46,15 @@ Using LVM such that we have:
`opt`
is mounted at
`/opt`
.
`opt`
is mounted at
`/opt`
.
### Rhizome
Currently our secondary or "hot spare" server; but we intend to migrate services here as it's newer and faster.
*
Hostname: rhizome.social.coop
*
64GB RAM (4x RAM 8192 MB DDR3)
*
AMD Ryzen 5 3600 CPU @ 3.60GHz.
*
2x 476GiB disks (NVM, RAID 1/mirrored).
### Third party services
### Third party services
*
DigitalOcean Spaces (S3 compatible, for storing Mastodon media and backups; also we use their transient VMs for development / testing)
*
DigitalOcean Spaces (S3 compatible, for storing Mastodon media and backups; also we use their transient VMs for development / testing)
...
...
...
...