The dgnum infrastructure
Find a file
Ryan Lahfa e0cf11276d
All checks were successful
Check meta / check_dns (pull_request) Successful in 20s
Check meta / check_meta (pull_request) Successful in 28s
Check workflows / check_workflows (pull_request) Successful in 30s
Build all the nodes / ap01 (pull_request) Successful in 1m11s
Build all the nodes / bridge01 (pull_request) Successful in 1m54s
Build all the nodes / geo01 (pull_request) Successful in 2m2s
Build all the nodes / geo02 (pull_request) Successful in 2m5s
Build all the nodes / rescue01 (pull_request) Successful in 2m28s
Build all the nodes / compute01 (pull_request) Successful in 2m50s
Build all the nodes / storage01 (pull_request) Successful in 2m15s
Run pre-commit on all files / check (pull_request) Successful in 32s
Build all the nodes / vault01 (pull_request) Successful in 1m51s
Build all the nodes / web02 (pull_request) Successful in 1m48s
Build all the nodes / web03 (pull_request) Successful in 1m43s
Build all the nodes / web01 (pull_request) Successful in 2m28s
Build all the nodes / ap01 (push) Successful in 1m28s
Build all the nodes / geo01 (push) Successful in 2m3s
Build all the nodes / bridge01 (push) Successful in 2m6s
Build all the nodes / geo02 (push) Successful in 2m13s
Build all the nodes / rescue01 (push) Successful in 2m34s
Build all the nodes / compute01 (push) Successful in 2m43s
Run pre-commit on all files / check (push) Successful in 41s
Build all the nodes / storage01 (push) Successful in 2m4s
Build all the nodes / vault01 (push) Successful in 2m9s
Build all the nodes / web02 (push) Successful in 1m58s
Build all the nodes / web03 (push) Successful in 1m56s
Build all the nodes / web01 (push) Successful in 2m48s
feat(monitoring): support cgroup exporting of metrics
This needs an update in our node_exporter dashboard but nothing too
hard.

Signed-off-by: Ryan Lahfa <ryan@dgnum.eu>
2024-12-11 11:08:07 +01:00
.forgejo/workflows feat(machines): add ap01 initial configuration 2024-12-08 15:24:40 +01:00
iso feat(infra): Internalize nix-lib, and make keys management simpler 2024-10-09 18:58:46 +02:00
keys feat(organization): Added Antoine Groudiev and Matthieu Boyer to organization 2024-11-09 22:55:24 +01:00
lib feat(meta/*): support generalized deployments 2024-12-07 15:26:13 +01:00
machines feat(hive): Add serverNodes to the arguments 2024-12-08 22:31:14 +01:00
meta fix(ap01): switch Liminix nodes to 24.05 2024-12-08 21:14:28 +01:00
modules feat(monitoring): support cgroup exporting of metrics 2024-12-11 11:08:07 +01:00
npins feat(monitoring): support cgroup exporting of metrics 2024-12-11 11:08:07 +01:00
patches chore(patches): Reorganize 2024-11-25 11:15:20 +01:00
scripts feat(scripts): introduce manual push script 2024-12-08 21:14:28 +01:00
workflows chore: Abstract machines and modules 2024-12-08 13:39:10 +01:00
.envrc feat(workflows): Switch to a nix-based definition of workflows 2024-11-11 17:57:23 +01:00
.gitignore fix(infra): remove untrackable file 2024-02-17 22:56:25 +01:00
CONTRIBUTE.md feat(README): Add guidelines for contributions and doc for dev tools 2024-02-23 21:07:20 +01:00
default.nix fix(tvix-cache): Import an existing file 2024-12-10 11:14:10 +01:00
hive.nix feat(hive): Add serverNodes to the arguments 2024-12-08 22:31:14 +01:00
LICENSE keys: Separate keys and move them 2023-05-22 15:05:12 +02:00
README.md feat(infra): Internalize nix-lib, and make keys management simpler 2024-10-09 18:58:46 +02:00
shell.nix feat(nix): Use passthru for shells and return to importing the scripts 2024-11-14 22:18:40 +01:00

❄️ infrastructure

The dgnum infrastructure.

Contributing

Some instruction on how to contribute are available (in french) in /CONTRIBUTE.md. You're expected to read this document before commiting to the repo.

Some documentation for the development tools are provided in the aforementioned file.

Using the binary cache

Add the following module to your configuration (and pin this repo using your favorite tool: npins, lon, etc...):

{ lib, ... }:
let
  dgnum-infra = PINNED_PATH_TO_INFRA;
in {
  nix.settings = (import dgnum-infra { }).mkCacheSettings {
    caches = [ "infra" ];
  };
}

Adding a new machine

The first step is to create a minimal viable NixOS host, using tha means necessary. The second step is to find a name for this host, it must be unique from the other hosts.

Tip

For the rest of this part, we assume that the host is named host02

Download the keys

The public SSH keys of host02 have to be saved to keys, preferably only the ssh-ed25519 one.

It can be retreived with :

ssh-keyscan address.of.host02 2>/dev/null | awk '/ssh-ed25519/ {print $2,$3}'

Initialize the machine folder and configuration

  • Create a folder host02 under machines/
  • Copy the hardware configuration file generated by nixos-generate-config to machines/host02/_hardware-configuration.nix
  • Create a machines/host02/_configuration.nix file, it will contain the main configuration options, the basic content of this file should be the following
{ lib, ... }:

lib.extra.mkConfig {
  enabledModules = [
    # List of modules to enable
  ];

  enabledServices = [
    # List of services to enable
  ];

  extraConfig = {
    services.netbird.enable = true;
  };

  root = ./.;
}

Fill in the metadata

Network configuration

The network is declared in meta/network.nix, the necessary hostId value can be generated with :

head -c4 /dev/urandom | od -A none -t x4 | sed 's/ //'

Other details

The general metadata is declared in meta/nodes.nix, the main values to declare are :

  • site, where the node is physically located
  • stateVersion
  • nixpkgs, the nixpkgs version to use

Initialize secrets

Create the directory secrets in the configuration folder, and add a secrets.nix file containing :

(import ../../../keys).mkSecrets [ "host02" ] [
  # List of secrets for host02
]

This will be used for future secret management.

Update encrypted files

Both the Arkheon, Netbox and notification modules have secrets that are deployed on all machines. To make those services work correctly, run in modules/dgn-records, modules/dgn-netbox-agent and modules/dgn-notify :

agenix -r

Commit and create a PR

Once all of this is done, check that the configuration builds correctly :

colmena build --on host02

Apply it, and create a Pull Request.