nixpkgs/nixos/modules/installer/tools/nixos-build-vms/build-vms.nix

{ system ? builtins.currentSystem
, config ? {}
, networkExpr
}:

let
  nodes = builtins.mapAttrs (vm: module: {
    _file = "${networkExpr}@node-${vm}";
    imports = [ module ];
  }) (import networkExpr);
in

with import ../../../../lib/testing-python.nix {
  inherit system;
  pkgs = import ../../../../.. { inherit system config; };
};

(makeTest { inherit nodes; testScript = ""; }).driverInteractive
* Remove the use of the NIXPKGS and NIXOS environment variables. Instead use $NIX_PATH. NIXOS_CONFIG is still supported. svn path=/nixos/trunk/; revision=32739 2012-03-02 12:38:22 +00:00			`{ system ? builtins.currentSystem`
tests: refactor to carry the package set as an argument This way, the package set will be possible to pass without re-importing all the time 2018-11-11 17:41:11 +09:00			`, config ? {}`
- Added nixos-build-vms command, which builds a virtual network from a network.nix expression (also used by nixos-deploy-network) - Added a backdoor option to the interactive run-vms script. This allows me to intergrate the virtual network approach with Disnix - Small documentation fixes Some explanation: The nixos-build-vms command line tool can be used to build a virtual network of a network.nix specification. For example, a network configuration (network.nix) could look like this: { test1 = {pkgs, config, ...}: { services.openssh.enable = true; ... }; test2 = {pkgs, config, ...}: { services.openssh.enable = true; services.xserver.enable = true; } ; } By typing the following instruction: $ nixos-build-vms -n network.nix a virtual network is built, which can be started by typing: $ ./result/bin/run-vms It is also possible to enable a backdoor. In this case *.socket files are stored in the current directory which can be used by the end-user to invoke remote instruction on a VM in the network through a Unix domain socket. For example by building the network with the following instructions: $ nixos-build-vms -n network.nix --use-backdoor and launching the virtual network: $ ./result/bin/run-vms You can find two socket files in your current directory, namely: test1.socket and test2.socket. These Unix domain sockets can be used to remotely administer the test1 and test2 machine in the virtual network. For example by running: $ socat ./test1.socket stdio ls /root You can retrieve the contents of the /root directory of the virtual machine with identifier test1 svn path=/nixos/trunk/; revision=24410 2010-10-21 22:50:12 +00:00			`, networkExpr`
			`}:`

nixos/build-vms: propagate file location When trying to build a VM using `nixos-build-vms` with a configuration that doesn't evaluate, an error "at `<unknown-file>`" is usually shown. This happens since the `build-vms.nix` creates a VM-network of NixOS-configurations that are attr-sets or functions and don't contain any file information. This patch manually adds the `_file`-attribute to tell the module-system which file contained broken configuration: ``` $ cat vm.nix { vm.invalid-option = 1; } $ nixos-build-vms vm.nix error: The option `invalid-option' defined in `/home/ma27/Projects/nixpkgs/vm.nix@node-vm' does not exist. (use '--show-trace' to show detailed location information) ``` 2020-04-13 17:43:44 +02:00			`let`
			`nodes = builtins.mapAttrs (vm: module: {`
			`_file = "${networkExpr}@node-${vm}";`
nixos-build-vms: use the driverInteractive attribute instead This reverts commit aab534b894c60e69199aba4cc57b8b3f8fd1a8c2 & uses the driverInteractive attribute for the test driver instead. This has the same effect but removes the extra module in the nixos-build-vms code. 2020-10-25 00:59:59 +02:00			`imports = [ module ];`
nixos/build-vms: propagate file location When trying to build a VM using `nixos-build-vms` with a configuration that doesn't evaluate, an error "at `<unknown-file>`" is usually shown. This happens since the `build-vms.nix` creates a VM-network of NixOS-configurations that are attr-sets or functions and don't contain any file information. This patch manually adds the `_file`-attribute to tell the module-system which file contained broken configuration: ``` $ cat vm.nix { vm.invalid-option = 1; } $ nixos-build-vms vm.nix error: The option `invalid-option' defined in `/home/ma27/Projects/nixpkgs/vm.nix@node-vm' does not exist. (use '--show-trace' to show detailed location information) ``` 2020-04-13 17:43:44 +02:00			`}) (import networkExpr);`
			`in`
* nixos-build-vms/build-vms.nix: drop the "nixos" function argument, since the path to the NixOS source tree is known. svn path=/nixos/trunk/; revision=26989 2011-04-27 13:01:42 +00:00
nixos/nixos-build-vms: switch to python test-driver In 0945178b3c6fd9e33002dd6e3c6f77dfca49565a we decided that Perl-based VM tests should be deprecated and will be removed between 20.03 and 20.09. So let's switch `nixos-build-vms(8)` to python as well (which is entirely interactive, so other scripts won't break). In my experience, the test-driver isn't used most of the time, so this patch is mainly supposed to get rid of the (probably misleading) deprecation warning when running `nixos-build-vms`. Apart from that, the interface for python's test-driver is way nicer. 2020-02-15 18:49:18 +01:00			`with import ../../../../lib/testing-python.nix {`
tests: refactor to carry the package set as an argument This way, the package set will be possible to pass without re-importing all the time 2018-11-11 17:41:11 +09:00			`inherit system;`
nixos-build-vms: fix eval Previously I got the following error message: ``` error: opening file '/home/ma27/Projects/nixpkgs/nixos/modules/installer/default.nix': No such file or directory ``` Probably related to 6c68fbd4e1f8beac39cb1f499ff90c78256262d6. 2018-11-23 13:43:47 +01:00			`pkgs = import ../../../../.. { inherit system config; };`
tests: refactor to carry the package set as an argument This way, the package set will be possible to pass without re-importing all the time 2018-11-11 17:41:11 +09:00			`};`
Fixed nixos-build-vms to use the new test driver. Backdoor option does not work anymore though. I have to look for another solution svn path=/nixos/trunk/; revision=25591 2011-01-16 21:57:09 +00:00
nixos-build-vms: use the driverInteractive attribute instead This reverts commit aab534b894c60e69199aba4cc57b8b3f8fd1a8c2 & uses the driverInteractive attribute for the test driver instead. This has the same effect but removes the extra module in the nixos-build-vms code. 2020-10-25 00:59:59 +02:00			`(makeTest { inherit nodes; testScript = ""; }).driverInteractive`