Add more ideas
This commit is contained in:
7
projects/100gb-networking.md
Normal file
7
projects/100gb-networking.md
Normal file
@@ -0,0 +1,7 @@
|
||||
# 100Gb Networking
|
||||
Establish a 100 gigabit networking in my Homelab
|
||||
|
||||
## Possible Hardware
|
||||
- [16 Port 100Gb Mikrotik switch](https://mikrotik.com/product/crs520_4xs_16xq_rm)
|
||||
- ConnectX-4 with 2x 100Gb Ports
|
||||
- ConnectX-5 with 2x 100Gb Ports
|
||||
6
projects/25gb-networking.md
Normal file
6
projects/25gb-networking.md
Normal file
@@ -0,0 +1,6 @@
|
||||
# 25Gb Networking
|
||||
Establish a 25 gigabit network in my Homelab
|
||||
|
||||
## Possible Hardware
|
||||
- [16 Port 25Gb Mikrotik switch](https://mikrotik.com/product/crs518_16xs_2xq)
|
||||
- ConnectX-4 with 2x 25Gb Ports
|
||||
8
projects/autoscaling-gitea-runners.md
Normal file
8
projects/autoscaling-gitea-runners.md
Normal file
@@ -0,0 +1,8 @@
|
||||
# Auto-Scaling Gitea Runners
|
||||
An automatic way to create/start extra gitea runners for actions, in case there is demand.
|
||||
My original idea was to have one or two extra servers that are usually not powered on, but only get turned on in case there is work for them to do (run CI jobs).
|
||||
|
||||
## Implementation idea
|
||||
- Gitea has an API to get pending jobs
|
||||
- Start server using WakeOnLan or ipmi api (depending on whats available)
|
||||
- Different policies
|
||||
9
projects/embedded-epyc-server.md
Normal file
9
projects/embedded-epyc-server.md
Normal file
@@ -0,0 +1,9 @@
|
||||
# Embedded Epyc Server
|
||||
|
||||
## Hardware
|
||||
- [Gigabyte MJ11-EC1](https://www.ram-koenig.de/gigabyte-mj11-ec1-amd-epyc-3151-mini-itx-inkl-atx-adapter)
|
||||
- 4x 16GB DDR4 RDIMM
|
||||
- 1U Server Case
|
||||
- PSU
|
||||
- 2x 120GB boot ssds
|
||||
- 4x 500GB or 1TB ssds for ceph storage
|
||||
Reference in New Issue
Block a user