The dgnum infrastructure
Find a file
catvayor bd4c64db02
All checks were successful
Check meta / check_dns (pull_request) Successful in 26s
Check workflows / check_workflows (pull_request) Successful in 25s
Check meta / check_meta (pull_request) Successful in 32s
Build all the nodes / ap01 (pull_request) Successful in 40s
Build all the nodes / netaccess01 (pull_request) Successful in 31s
Build all the nodes / netcore01 (pull_request) Successful in 32s
Build all the nodes / netcore02 (pull_request) Successful in 38s
Build all the nodes / geo02 (pull_request) Successful in 1m39s
Build all the nodes / bridge01 (pull_request) Successful in 2m23s
Build all the nodes / geo01 (pull_request) Successful in 2m31s
Build all the nodes / build01 (pull_request) Successful in 2m37s
Build all the nodes / hypervisor02 (pull_request) Successful in 2m37s
Build all the nodes / hypervisor01 (pull_request) Successful in 2m41s
Build all the nodes / storage01 (pull_request) Successful in 2m0s
Build all the nodes / hypervisor03 (pull_request) Successful in 2m48s
Build all the nodes / tower01 (pull_request) Successful in 1m57s
Build all the nodes / cof02 (pull_request) Successful in 2m53s
Build all the nodes / vault01 (pull_request) Successful in 2m11s
Build the shell / build-shell (pull_request) Successful in 39s
Build all the nodes / compute01 (pull_request) Successful in 3m14s
Run pre-commit on all files / pre-commit (pull_request) Successful in 42s
Build all the nodes / rescue01 (pull_request) Successful in 2m52s
Build all the nodes / web02 (pull_request) Successful in 1m57s
Build all the nodes / web01 (pull_request) Successful in 2m48s
Build all the nodes / web03 (pull_request) Successful in 3m3s
Check meta / check_meta (push) Successful in 17s
Check meta / check_dns (push) Successful in 24s
Build all the nodes / netaccess01 (push) Successful in 22s
Build all the nodes / netcore01 (push) Successful in 25s
Build all the nodes / ap01 (push) Successful in 39s
Build all the nodes / netcore02 (push) Successful in 37s
Build all the nodes / build01 (push) Successful in 1m38s
Build all the nodes / geo02 (push) Successful in 1m40s
Build all the nodes / cof02 (push) Successful in 1m57s
Build all the nodes / bridge01 (push) Successful in 2m16s
Build all the nodes / storage01 (push) Successful in 1m56s
Build all the nodes / hypervisor01 (push) Successful in 2m35s
Build the shell / build-shell (push) Successful in 40s
Build all the nodes / hypervisor02 (push) Successful in 2m39s
Build all the nodes / geo01 (push) Successful in 2m50s
Run pre-commit on all files / pre-commit (push) Successful in 34s
Build all the nodes / hypervisor03 (push) Successful in 2m50s
Build all the nodes / rescue01 (push) Successful in 2m32s
Build all the nodes / vault01 (push) Successful in 2m24s
Build all the nodes / tower01 (push) Successful in 2m41s
Build all the nodes / compute01 (push) Successful in 3m10s
Build all the nodes / web01 (push) Successful in 2m35s
Build all the nodes / web03 (push) Successful in 1m43s
Build all the nodes / web02 (push) Successful in 1m53s
feat(cof02): init cof staging vm
The purpose of cof02 is to allow presenting under development features
on gestiocof, or check that the next update of gestiocof works in
production-like environment, by placing it in a near perfect copy of
this environment
2025-03-10 10:19:04 +01:00
.forgejo/workflows feat(cof02): init cof staging vm 2025-03-10 10:19:04 +01:00
iso chore: Refactor meta to a module architecture 2025-02-06 13:08:04 +01:00
lib fix(wrappers/colmena): ensure purity of evaluation 2025-03-02 22:20:10 +01:00
LICENSES feat(compute01/search): init search.infra and modules/nixos/extranix 2024-12-28 22:25:26 +01:00
machines feat(cof02): init cof staging vm 2025-03-10 10:19:04 +01:00
meta feat(cof02): init cof staging vm 2025-03-10 10:19:04 +01:00
modules feat(django-apps): allow adding extra init steps 2025-03-09 21:53:18 +01:00
npins chore(npins): Update nix-actions 2025-03-09 21:39:35 +01:00
patches chore(npins): Revert failed update 2025-02-10 16:52:12 +01:00
scripts feat(netconf/scripts): init script for deployment 2025-02-03 15:08:36 +01:00
workflows fix(nix-actions): now steps are under lib 2025-03-09 21:39:35 +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
bootstrap.nix chore(bootstrap): Rename file 2025-02-06 13:08:04 +01:00
CONTRIBUTE.md chore: Add license and copyright information 2024-12-13 12:41:38 +01:00
default.nix fix(radius): Be less verbose in the logs not to overflow journald 2025-03-09 18:34:20 +01:00
hive.nix chore(bootstrap): Rename file 2025-02-06 13:08:04 +01:00
keys.nix fix(keys): Make it so agenix works again 2025-02-13 17:38:12 +01:00
README.md chore: Refactor meta to a module architecture 2025-02-06 13:08:04 +01:00
REUSE.toml fix(radius): Be less verbose in the logs not to overflow journald 2025-03-09 18:34:20 +01: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.nix).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.