forked from Fediversity/Fediversity
Nicolas “Niols” Jeannerod
ee5c2b90b7
Closes Fediversity/Fediversity#276 This PR adds a CLI deployment test. It builds on top of Fediversity/Fediversity#323. This test features a deployer node and four target nodes. The deployer node runs `nixops4 apply` on a deployment built with our actual code in `deployment/default.nix`, which pushes onto the four target machines combinations of Garage/Mastodon/Peertube/Pixelfed depending on a JSON payload. We check that the expected services are indeed deployed on the machines. Getting there involved reworking the existing basic test to extract common patterns, and adding support for ACME certificates negotiation inside the NixOS test. What works: - deployer successfully runs `nixops4 apply` with various payloads - target machines indeed get the right services pushed onto them and removed - services on target machines successfully negotiate ACME certificates What does not work: the services themselves depend a lot on DNS and that is not taken care of at all, so they are probably very broken. Still, this is a good milestone. Test it yourself by running `nix build .#checks.x86_64-linux.deployment-basic -vL` and `nix build .#checks.x86_64-linux.deployment-cli -vL`. On the very beefy machine that I am using, the basic test runs in ~4 minutes and the CLI test in ~17 minutes. We know from Fediversity/Fediversity#323 that the basic test runs in ~12 minutes on the CI runner, so maybe about an hour for the CLI test? Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io> Reviewed-on: Fediversity/Fediversity#329 Reviewed-by: kiara Grouwstra <kiara@procolix.eu> Reviewed-by: Valentin Gagarin <valentin.gagarin@tweag.io> Co-authored-by: Nicolas “Niols” Jeannerod <nicolas.jeannerod@moduscreate.com> Co-committed-by: Nicolas “Niols” Jeannerod <nicolas.jeannerod@moduscreate.com>
67 lines
2 KiB
Nix
67 lines
2 KiB
Nix
/**
|
|
This file contains options shared by various components of the integration test, i.e. deployment resources, test nodes, target configurations, etc.
|
|
All these components are declared as modules, but are part of different evaluations, which is the options in this file can't be shared "directly".
|
|
Instead, each component imports this module and the same values are set for each of them from a common call site.
|
|
Not all components will use all the options, which allows not setting all the values.
|
|
*/
|
|
|
|
{ config, lib, ... }:
|
|
|
|
let
|
|
inherit (lib) mkOption types;
|
|
|
|
in
|
|
{
|
|
options = {
|
|
targetMachines = mkOption {
|
|
type = with types; listOf str;
|
|
description = ''
|
|
Names of the nodes in the NixOS test that are “target machines”. This is
|
|
used by the infrastructure to extract their network configuration, among
|
|
other things, and re-import it in the deployment.
|
|
'';
|
|
};
|
|
|
|
pathToRoot = mkOption {
|
|
type = types.path;
|
|
description = ''
|
|
Path from the location of the working directory to the root of the
|
|
repository.
|
|
'';
|
|
};
|
|
|
|
pathFromRoot = mkOption {
|
|
type = types.path;
|
|
description = ''
|
|
Path from the root of the repository to the working directory.
|
|
'';
|
|
apply = x: lib.path.removePrefix config.pathToRoot x;
|
|
};
|
|
|
|
pathToCwd = mkOption {
|
|
type = types.path;
|
|
description = ''
|
|
Path to the current working directory. This is a shortcut for
|
|
pathToRoot/pathFromRoot.
|
|
'';
|
|
default = config.pathToRoot + "/${config.pathFromRoot}";
|
|
};
|
|
|
|
enableAcme = mkOption {
|
|
type = types.bool;
|
|
description = ''
|
|
Whether to enable ACME in the NixOS test. This will add an ACME server
|
|
to the node and connect all the target machines to it.
|
|
'';
|
|
default = false;
|
|
};
|
|
|
|
acmeNodeIP = mkOption {
|
|
type = types.str;
|
|
description = ''
|
|
The IP of the ACME node in the NixOS test. This option will be set
|
|
during the test to the correct value.
|
|
'';
|
|
};
|
|
};
|
|
}
|