nordic-dev.net/nixpkgs
nordic-dev.net/nixpkgs
2
0
Fork 0
mirror of https://github.com/NixOS/nixpkgs.git synced 2024-12-28 00:24:18 +00:00
Code Issues Packages Projects Releases Wiki Activity
9a20d75689
nixpkgs/nixos/modules/installer/tools/nixos-build-vms/build-vms.nix

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

32 lines
971 B
Nix
Raw Normal View History

* 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 08:41:11 +00: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 15:43:44 +00: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-24 22:59:59 +00: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 15:43:44 +00:00
}) (import networkExpr);
nixos/test/test-driver: Class-ify the test driver This commit encapsulates the involved domain into classes and defines explicit and typed arguments where untyped dicts where used. It preserves backwards compatibility through legacy wrappers.
2021-06-12 22:47:25 +00:00
nixos/build-vms: fix eval
2021-08-20 09:48:15 +00:00
pkgs = import ../../../../.. { inherit system config; };
nixos/test/test-driver: Class-ify the test driver This commit encapsulates the involved domain into classes and defines explicit and typed arguments where untyped dicts where used. It preserves backwards compatibility through legacy wrappers.
2021-06-12 22:47:25 +00:00
testing = import ../../../../lib/testing-python.nix {
nixos/build-vms: fix eval
2021-08-20 09:48:15 +00:00
inherit system pkgs;
nixos/test/test-driver: Class-ify the test driver This commit encapsulates the involved domain into classes and defines explicit and typed arguments where untyped dicts where used. It preserves backwards compatibility through legacy wrappers.
2021-06-12 22:47:25 +00:00
};
interactiveDriver = (testing.makeTest { inherit nodes; testScript = "start_all(); join_all();"; }).driverInteractive;
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 15:43:44 +00:00
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
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: fix eval
2021-08-20 09:48:15 +00:00
pkgs.runCommand "nixos-build-vms" { nativeBuildInputs = [ pkgs.makeWrapper ]; } ''
nixos/test/test-driver: Class-ify the test driver This commit encapsulates the involved domain into classes and defines explicit and typed arguments where untyped dicts where used. It preserves backwards compatibility through legacy wrappers.
2021-06-12 22:47:25 +00:00
mkdir -p $out/bin
ln -s ${interactiveDriver}/bin/nixos-test-driver $out/bin/nixos-test-driver
ln -s ${interactiveDriver}/bin/nixos-test-driver $out/bin/nixos-run-vms
wrapProgram $out/bin/nixos-test-driver \
--add-flags "--interactive"
nixos-build-vms(8): `$out/bin/nixos-run-vms` should non-interactively start VMs Not entirely sure when it got broken this time, but when creating a VM network with `nixos-build-vms(8)`, there are should be the following scripts: * `$out/bin/nixos-test-driver` which drops into an interactive shell to interactively perform test steps. * `$out/bin/nixos-run-vms` which non-interactively starts the VMs from the network so that one can manually play around in the VM. The latter also starts an interactive shell for a while now which means that it does the exact same thing as `nixos-test-driver` which is not its purpose.
2022-02-19 18:35:40 +00:00
wrapProgram $out/bin/nixos-run-vms \
--set testScript "${pkgs.writeText "start-all" "start_all(); join_all();"}" \
--add-flags "--no-interactive"
nixos/test/test-driver: Class-ify the test driver This commit encapsulates the involved domain into classes and defines explicit and typed arguments where untyped dicts where used. It preserves backwards compatibility through legacy wrappers.
2021-06-12 22:47:25 +00:00
''
Reference in New Issue Copy Permalink