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

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

let nodes = import networkExpr; in

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

(makeTest { inherit nodes; testScript = ""; }).driver
* 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 04:38:22 -08: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 00:41:11 -08: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 15:50:12 -07:00			`, networkExpr`
			`}:`

* 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 06:01:42 -07:00			`let nodes = import networkExpr; in`

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 00:41:11 -08:00			`with import ../../../../lib/testing.nix {`
			`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 04:43:47 -08: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 00:41:11 -08: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 13:57:09 -08:00
nixos-build-vms: Fix function invocation to test driver 2014-06-09 04:36:26 -07:00			`(makeTest { inherit nodes; testScript = ""; }).driver`