[reprotest] 01/02: Remove autopkgtest manpages and other unused files
Ximin Luo
infinity0 at debian.org
Mon Nov 28 19:15:28 UTC 2016
This is an automated email from the git hooks/post-receive script.
infinity0 pushed a commit to branch master
in repository reprotest.
commit b5bc0cb9fed36412ca5ae4a3b8e6196004bf1c47
Author: Ximin Luo <infinity0 at debian.org>
Date: Mon Nov 28 20:00:14 2016 +0100
Remove autopkgtest manpages and other unused files
---
debian/changelog | 1 +
reprotest/tools/README.running-tests.rst | 279 ------------------------
reprotest/tools/adt-build-lxc | 134 ------------
reprotest/tools/adt-build-lxc.1 | 74 -------
reprotest/tools/adt-build-lxd | 103 ---------
reprotest/tools/adt-build-lxd.1 | 48 -----
reprotest/tools/adt-buildvm-ubuntu-cloud | 329 -----------------------------
reprotest/tools/adt-buildvm-ubuntu-cloud.1 | 146 -------------
reprotest/virt/autopkgtest-chroot.1 | 65 ------
reprotest/virt/autopkgtest-lxc.1 | 133 ------------
reprotest/virt/autopkgtest-lxd.1 | 134 ------------
reprotest/virt/autopkgtest-null.1 | 42 ----
reprotest/virt/autopkgtest-qemu.1 | 252 ----------------------
reprotest/virt/autopkgtest-schroot.1 | 76 -------
reprotest/virt/autopkgtest-ssh.1 | 278 ------------------------
15 files changed, 1 insertion(+), 2093 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 0585814..5d0cb24 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -7,6 +7,7 @@ reprotest (0.4) UNRELEASED; urgency=medium
are needed to make the variations in the first place.
* Add an "auto" feature to the CLI, plus a presets module so it's easier to
use, and other non-Debian systems can start populating this too.
+ * Remove autopkgtest manpages and other unused files. (Closes: #834300)
-- Ximin Luo <infinity0 at debian.org> Fri, 18 Nov 2016 17:13:49 +0100
diff --git a/reprotest/tools/README.running-tests.rst b/reprotest/tools/README.running-tests.rst
deleted file mode 100644
index f30629e..0000000
--- a/reprotest/tools/README.running-tests.rst
+++ /dev/null
@@ -1,279 +0,0 @@
-Autopkgtest - Running tests
-===========================
-
-This document gives an overview how to run tests with autopkgtest. It
-does not cover each detail, please consult the individual manpages like
-adt-run(1), adt-virt-schroot(1), etc. for all available options.
-
-Ingredients for Debian packages:
-
-- A source package which defines tests in ``debian/tests/``. See
- README.package-tests for how to define them.
-
- There are plenty of existing package tests in Debian/Ubuntu which you
- can use as examples and inspiration, just look for a source package
- with a ``Testsuite: autopkgtest`` header, or the automatic test
- running services `in Debian <http://ci.debian.net/>`_ and Ubuntu (e.
- g. for `14.04 LTS <https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/>`_).
-
-- A location for the source/tests: This can be a local source tree, a
- local .dsc, or "download with apt-get source".
-
-- Optionally some pre-built binary packages which should be tested.
-
-Ingredients for Click packages:
-
-- A binary .click package (local ``*.click`` file or already installed)
- whose manifest specifies tests and their metadata. See
- README.click-tests.rst for details.
-
-- The corresponding click source package which contains the tests
- defined in the manifest.
-
-Finally you need a virtualization server, which creates the environment
-in which the test runs. Depending on how intrusive the test is this can
-provide various degrees of isolation, from "run on my local system"
-(fastest, but unsafe) to "run in a temporary virtual machine" (slowest,
-but highest possible isolation). These are described in detail below.
-
-adt-run
--------
-The ``adt-run`` program is the main program to run tests which gets all
-these ingredients as arguments, in the following form:
-
-::
-
- adt-run [options] <source package> --- <virt-server> [<virt-server options>]
-
-Specifying tests and packages
------------------------------
-
-All possible options are explained in the adt-run(1) manpage. This
-section shows the most common scenarios, with using "mysrc" as source
-package name. Note that specifying the virtualization server and its
-options is handled in the following section, and it is independent of
-specifying tests and packages, so it is merely abbreviated as
-*virt-server* here.
-
-- Run tests from the Debian source package in the distribution. This
- calls ``apt-get source mysrc`` in the virt-server, thus will use
- whichever distribution/release that ``/etc/apt/sources.list``
- configures:
-
- ``adt-run mysrc ---`` *virt-server*
-
-- Run tests from a local unbuilt source tree, using the binary packages
- from the distribution. This is useful if you are creating or fixing
- tests, but the actual binary packages are fine:
-
- ``adt-run -B --unbuilt-tree=packages/mysrc ---`` *virt-server*
-
- Note that you can abbreviate ``--unbuilt-tree=`` with just the
- directory with two(!) trailing slashes, i. e.
-
- ``adt-run -B packages/mysrc// ---`` *virt-server*
-
-- Run tests from a local built source tree, using the binary packages
- from the distribution:
-
- ``adt-run -B --built-tree=packages/mysrc ---`` *virt-server*
-
- Note that you can abbreviate ``--built-tree=`` with just the
- directory with one(!) trailing slash, i. e.
-
- ``adt-run -B packages/mysrc/ ---`` *virt-server*
-
- Built vs. unbuilt only makes a difference for tests which declare the
- ``build-needed`` restriction (see README.package-tests), in which
- case ``--built-tree`` avoids having to re-build the source in the
- virt-server.
-
-- Build a local source package in the virt-server, then run its tests
- against the built binaries. This is useful if you need to fix a bug
- in the actual packages to make the tests succeed:
-
- ``adt-run packages/mysrc// ---`` *virt-server*
-
-- Same as above, but with specifying a built source package instead of
- a source tree:
-
- ``adt-run packages/mysrc_*.dsc ---`` *virt-server*
-
-- Test new built binaries with a new source and avoid rebuilding them
- in virt-server. This is useful if you e. g. update a package to a new
- version and now want to check whether its tests still succeed:
-
- ``adt-run -B packages/*.deb packages/mysrc_*.dsc ---`` *virt-server*
-
-- The previous case can be simplified if you have a binary .changes
- from a previous build:
-
-
- ``adt-run packages/*.changes ---`` *virt-server*
-
-- Run tests for a locally built click package:
-
- ``adt-run myclickapp/ myclickapp_0.1_all.click ---`` *virt-server*
-
- Note that for this you need to specify a virt-server which has
- "click" itself and the click app's required framework already
- installed. To run this on an actual Ubuntu phone, you can use the SSH
- testbed server:
-
- ::
-
- adt-run ubuntu-calculator-app/ com.ubuntu.calculator_1.3.283_all.click --- ssh -s adb
-
- (This is using the shipped ``adb`` setup script in
- ``/usr/share/autopkgtest/ssh-setup/``.)
-
- If you aren't running the test on an Ubuntu touch device, you can
- approximate the environment in a normal schroot/LXC/QEMU testbed with
- the ``--setup-commands`` scripts that autopkgtest provides (note that
- you do not need to specify the full
- ``/usr/share/autopkgtest/setup-commands/`` path for shipped scripts):
-
- ::
-
- adt-run --setup-commands ubuntu-touch-session \
- --setup-commands ro-apt \
- myclickapp/ myclickapp_0.1_all.click --- lxc adt-utopic
-
- See the comments in the setup-commands scripts for details.
-
-- Run tests for an already installed click package:
-
- ``adt-run --click=com.example.myapp ---`` *virt-server*
-
- This will work for click apps which have an ``x-source/vcs-bzr`` entry
- in their manifest. If that's not the case, you will need to explicitly
- specify the click source directory as above.
-
-Output
-------
-
-Unless you specify some options, adt-run just writes the logging, test
-outputs, and test results to stdout/stderr and exits with code 0 on
-success, or some non-zero code if there were skipped or failed tests or
-problems with the virt-server. (See adt-run(1) for defined codes).
-
-For getting output files you have three choices:
-
-- If you just want the "testname: PASS/FAIL" results, use
-
- ``--summary-file=/path/to/summary.txt``.
-
-- If you want the complete output of adt-run in a file, use
-
- ``-l /path/to/test.log`` (or the long option ``--log-file``)
-
-- If you want the log file, the individual test stdout and stderr
- output, and built binaries (if any) in a directory, use
-
- ``-o /path/to/test-output/`` (or the long option ``--output-dir``).
-
-You can also combine these.
-
-Virtualization server
----------------------
-
-schroot
-~~~~~~~
-::
-
- adt-run ... --- schroot schroot-name
-
-Run tests in the specified schroot. You can use mk-sbuild(1) to
-conveniently create schroots, and run this as normal user if you
-configured schroot accordingly.
-
-This server is the fastest available that provides "proper" file system
-isolation and revert, but it does not provide enough isolation for tests
-that need to start services, reconfigure the network, or open TCP ports
-which are already open at the host. If your test does not need to do
-these things this is the recommended server, as schroots are also useful
-for other tasks like building packages with sbuild.
-
-See adt-virt-schroot(1) manpage.
-
-LXC
-~~~
-::
-
- adt-run ... --- lxc container-name
-
-Run tests in the specified LXC container. Containers provide full
-service and network isolation, but tests or packages cannot change the
-kernel or hardware configuration. If your test does not need that, this
-is the recommended server as it is faster than QEMU and works on all
-Linux architectures.
-
-``container-name`` will be cloned or be called with a temporary overlay
-file system if you specify the ``-e`` (``--ephemeral``) option, thus it
-will never be modified and you can run several tests in parallel safely.
-Unless your test or architecture or RAM availability doesn't work with
-overlayfs, using -e is highly recommended for better performance.
-
-If your user can get root privileges with sudo, you can call adt-run as
-your normal user and specify ``-s`` (``--sudo``) so that the container
-can be started as root.
-
-See adt-virt-lxc(1) manpage. This also explains how to build containers.
-
-QEMU
-~~~~
-::
-
- adt-run ... --- qemu path/to/image
-
-Run tests with QEMU/KVM using the specified image. The image will be run
-with a temporary overlay file system, thus it will never be modified and
-you can run several tests in parallel safely.
-
-If your test needs a full machine including kernel/hardware access, this
-is the recommended runner; it provides complete system isolation, revert
-and breaks-testbed capabilities. But it is also the one with the biggest
-overhead and only works well on architectures with KVM acceleration (i.
-e. mostly x86).
-
-See adt-virt-qemu(1) manpage. This also explains how to build suitable
-images, and the requirements of the guest.
-
-null
-~~~~
-::
-
- adt-run ... --- null
-
-This does not do any virtualization, but runs tests straight on the
-host. Beware that this will leave some clutter on your system (installed
-test or build dependency packages, configuration changes that the tests
-might make, etc.). It is not able to run tests with the "breaks-testbed"
-restriction. See adt-virt-null(1) manpage.
-
-chroot
-~~~~~~
-::
-
- adt-run ... --- chroot /path/to/chroot
-
-Run tests in the specified chroot. You need to call adt-run as root for
-this. There is no automatic cleanup or revert for the chroot, so unless
-you can provide this by some other means, don't use this.
-
-ssh
-~~~
-::
-
- adt-run ... --- ssh -l joe -h testhost.example.com
-
-This is a generic runner for an externally set up testbed which assumes
-nothing else than a working ssh connection. This can call a "setup
-script" to create/configure a testbed (such as spinning up a cloud VM
-with nova or setting up SSH on a phone through ADB). See the manpage for
-details. autopkgtest ships setup scripts for an adb host (mostly for
-Ubuntu Touch), for nova (for cloud instances) and for Ubuntu Snappy
-currently; see their comment headers in
-``/usr/share/autopkgtest/ssh-setup/``.
-
-.. vim: ft=rst tw=72
diff --git a/reprotest/tools/adt-build-lxc b/reprotest/tools/adt-build-lxc
deleted file mode 100755
index a64edc2..0000000
--- a/reprotest/tools/adt-build-lxc
+++ /dev/null
@@ -1,134 +0,0 @@
-#!/bin/sh
-# Licensed under the GPL: https://www.gnu.org/licenses/gpl-3.0.en.html
-# For details: reprotest/debian/copyright
-set -e
-
-DISTRO="$1"
-RELEASE="$2"
-if [ -z "$1" ] || [ -z "$2" ]; then
- echo "Usage: $0 debian|ubuntu <release> [arch]" >&2
- exit 1
-fi
-
-# check that LXC config has networking
-if grep -q 'lxc.network.type *= *empty' /etc/lxc/default.conf; then
- cat <<EOF >&2
-ERROR: autopkgtest containers need networking; please set it up and adjust
-lxc.network.type in /etc/lxc/default.conf
-EOF
- exit 1
-fi
-
-ARCH=${3:-}
-NAME="adt-${RELEASE}${ARCH:+-$ARCH}"
-
-# fall back for older LXC option name
-LXCDIR=`lxc-config lxc.lxcpath` || LXCDIR=`lxc-config lxcpath` || LXCDIR=/var/lib/lxc
-
-LXC_ARGS="-t $DISTRO -- -r $RELEASE ${ARCH:+-a $ARCH}"
-
-# packages_template defaults to "ssh,vim" in Ubuntu; don't install those
-export packages_template=eatmydata
-if type eatmydata >/dev/null 2>&1; then
- LXC_CREATE_PREFIX="eatmydata"
-fi
-
-# detect apt proxy
-proxy_detect() {
- if [ -z "$ADT_APT_PROXY" ]; then
- RES=`apt-config shell proxy Acquire::http::Proxy`
- eval $RES
- if echo "${proxy:-}" | egrep -q '(localhost|127\.0\.0\.[0-9]*)'; then
- # set http_proxy for the initial debootstrap
- export http_proxy="$proxy"
-
- # translate proxy address to one that can be accessed from the
- # running container
- local bridge_interface=$(awk '{ if ($1 == "lxc.network.link") print($3)}' /etc/lxc/default.conf)
- if [ -n "$bridge_interface" ]; then
- local bridge_ip=$(ip -4 a show dev "$bridge_interface" | awk '/ inet / {sub(/\/.*$/, "", $2); print $2}') || true
- if [ -n "$bridge_ip" ]; then
- ADT_APT_PROXY=$(echo "$proxy" | sed -r "s#localhost|127\.0\.0\.[0-9]*#$bridge_ip#")
- fi
- fi
- if [ -n "$ADT_APT_PROXY" ]; then
- echo "Detected local apt proxy, using $ADT_APT_PROXY as container proxy"
- fi
- elif [ -n "${proxy:-}" ]; then
- ADT_APT_PROXY="$proxy"
- echo "Using $ADT_APT_PROXY as container proxy"
- # set http_proxy for the initial debootstrap
- export http_proxy="$proxy"
- fi
- fi
-}
-
-setup() {
- # a host's http_proxy for localhost does not work in the guest, apt proxy
- # needs to be set up separately there
- if [ "$http_proxy" != "${http_proxy#*localhost*}" ] || \
- [ "$http_proxy" != "${http_proxy#*127.0.0.*}" ]; then
- unset http_proxy
- unset https_proxy
- fi
-
- # set up apt proxy for the container
- if [ -n "$ADT_APT_PROXY" ]; then
- echo "Acquire::http { Proxy \"$ADT_APT_PROXY\"; };" > $LXCDIR/$1/rootfs/etc/apt/apt.conf.d/01proxy
- fi
-
- lxc-start --daemon --name=$1
- # wait until it is booted: lxc-attach works and we get a numeric runlevel
- timeout=60
- while [ $timeout -ge 0 ]; do
- timeout=$((timeout - 1))
- sleep 1
- O=`lxc-attach --name=$1 runlevel 2>/dev/null` || continue
- [ "$O" = "${O%[0-9]}" ] || break
- done
- [ $timeout -ge 0 ] || {
- echo "Timed out waiting for container to boot" >&2
- lxc-stop --kill --name=$1 || true
- lxc-destroy --name=$1 || true
- exit 1
- }
-
- # find setup-testbed script
- for script in $(dirname $(dirname "$0"))/setup-commands/setup-testbed \
- /usr/share/autopkgtest/setup-commands/setup-testbed; do
- if [ -r "$script" ]; then
- echo "Running setup script $script..."
- cat "$script" | lxc-attach --name=$1 sh
- break
- fi
- done
- lxc-stop --name=$1
-}
-
-proxy_detect
-
-if [ ! -e $LXCDIR/$NAME ]; then
- # first-time run: just create the container
- $LXC_CREATE_PREFIX lxc-create -B best --name=$NAME $LXC_ARGS
- setup $NAME
-else
- # remove LXC rootfs caches; on btrfs this might be a subvolume, otherwise
- # rm it
- btrfs subvolume delete /var/cache/lxc/$RELEASE/rootfs-* 2>/dev/null || rm -rf /var/cache/lxc/$RELEASE/rootfs-*
- # create a new rootfs in a temp container
- $LXC_CREATE_PREFIX lxc-create -B best --name=${NAME}.new $LXC_ARGS
- setup ${NAME}.new
- sed -i "s/${NAME}.new/${NAME}/" $LXCDIR/${NAME}.new/rootfs/etc/hostname $LXCDIR/${NAME}.new/rootfs/etc/hosts
- # replace the original rootfs; can't make this more atomic unfortunately
- mv $LXCDIR/${NAME}.new/rootfs $LXCDIR/${NAME}/rootfs.new
- mv $LXCDIR/${NAME}/rootfs $LXCDIR/${NAME}/rootfs.old
- mv $LXCDIR/${NAME}/rootfs.new $LXCDIR/${NAME}/rootfs
- # old rootfs might contain btrfs subvolumes, remove them
- subvols=$(btrfs subvolume list -o $LXCDIR/${NAME}/rootfs.old 2>/dev/null | awk "/\/rootfs.old/ {print \$(NF)}") || true
- for vol in $subvols; do
- btrfs subvolume delete "/${vol#@}"
- done
- btrfs subvolume delete $LXCDIR/${NAME}/rootfs.old 2>/dev/null || rm -rf $LXCDIR/${NAME}/rootfs.old
- mkdir $LXCDIR/${NAME}.new/rootfs
- lxc-destroy --name=${NAME}.new
-fi
diff --git a/reprotest/tools/adt-build-lxc.1 b/reprotest/tools/adt-build-lxc.1
deleted file mode 100644
index 8ef8868..0000000
--- a/reprotest/tools/adt-build-lxc.1
+++ /dev/null
@@ -1,74 +0,0 @@
-.TH adt-build-lxc 1 2014 "Linux Programmer's Manual"
-.SH NAME
-adt-build-lxc \- Create or update autopkgtest container for adt\-virt-lxc
-
-.SH SYNOPSIS
-.B adt-build-lxc
-.I distribution release
-.RI [ architecture ]
-
-.SH DESCRIPTION
-.B adt-build-lxc
-creates or updates an LXC container \fBadt-\fIrelease\fR which is suitable for
-autopkgtest's LXC runner \fBadt-virt-lxc\fR(1).
-
-It calls
-.B lxc-create
-with the
-.I distribution
-template (which can currently be
-.B debian
-or
-.B ubuntu) and
-.BI -r release
-to build a debootstrap-like container, then enables
-.B deb-src
-apt sources, and runs
-.B apt-get update\fR.
-
-It defaults to the native architecture, but you can specify a different one as
-third parameter.
-
-If the container already exists, it updates it as unintrusively as possible by
-first creating a new temporary container \fBadt-\fIrelease\fB.new\fR, and then
-rsyncing its root file system back to the existing \fBadt-\fIrelease\fR. Note
-that this could cause some side-effects and breakage if you have running
-containers with ephemeral overlays (i. e. using the
-.B --ephemeral
-option), but it does work in general. This update process does not interfere at
-all if you use
-.B adt-virt-lxc
-with cloning.
-
-Note that you need to call this as root, unless you set up LXC to allow
-per-user containers. But user containers will not work with many or even most
-autopkgtests.
-
-You can specify an apt proxy to use in the container in the
-.B $ADT_APT_PROXY
-environment variable. If you have an apt proxy configured on the host,
-the container will automatically use this, otherwise there is no default.
-
-
-.SH EXAMPLES
-
-# adt-build-lxc debian sid
-
-.PP
-$ sudo adt-build-lxc ubuntu trusty i386
-
-.SH SEE ALSO
-\fBadt\-virt-lxc\fR(1),
-\fBadt\-run\fR(1),
-\fBlxc-create\fR(1),
-\fB/usr/share/doc/autopkgtest/\fR.
-
-.SH AUTHORS AND COPYRIGHT
-.B adt-build-lxc
-was written by Martin Pitt <martin.pitt at ubuntu.com>
-
-This manpage is part of autopkgtest, a tool for testing Debian binary
-packages. autopkgtest is Copyright (C) 2006-2014 Canonical Ltd and others.
-
-See \fB/usr/share/doc/autopkgtest/CREDITS\fR for the list of
-contributors and full copying conditions.
diff --git a/reprotest/tools/adt-build-lxd b/reprotest/tools/adt-build-lxd
deleted file mode 100755
index 6ea6cef..0000000
--- a/reprotest/tools/adt-build-lxd
+++ /dev/null
@@ -1,103 +0,0 @@
-#!/bin/sh
-# Licensed under the GPL: https://www.gnu.org/licenses/gpl-3.0.en.html
-# For details: reprotest/debian/copyright
-set -eu
-
-# generate temporary container name
-generate_container_name() {
- while true; do
- CONTAINER=$(mktemp adt-prepare-XXX -u)
- lxc info "$CONTAINER" >/dev/null 2>&1 || break
- done
-}
-
-# detect apt proxy
-proxy_detect() {
- if [ -z "${ADT_APT_PROXY:-}" ]; then
- RES=`apt-config shell proxy Acquire::http::Proxy`
- eval $RES
- if echo "${proxy:-}" | egrep -q '(localhost|127\.0\.0\.[0-9]*)'; then
- # translate proxy address to one that can be accessed from the
- # running container
- local bridge_ip=$(sh -c '. /etc/default/lxd-bridge; echo $LXD_IPV4_ADDR' 2>/dev/null)
- if [ -n "$bridge_ip" ]; then
- ADT_APT_PROXY=$(echo "$proxy" | sed -r "s#localhost|127\.0\.0\.[0-9]*#$bridge_ip#")
- fi
- if [ -n "${ADT_APT_PROXY:-}" ]; then
- echo "Detected local apt proxy, using $ADT_APT_PROXY as container proxy"
- fi
- elif [ -n "${proxy:-}" ]; then
- echo "Using $ADT_APT_PROXY as container proxy"
- ADT_APT_PROXY="$proxy"
- fi
- fi
-}
-
-setup() {
- # set up apt proxy for the container
- if [ -n "${ADT_APT_PROXY:-}" ] && [ "$ADT_APT_PROXY" != "none" ]; then
- echo "Acquire::http::Proxy \"$ADT_APT_PROXY\";" | lxc file push - "$CONTAINER/etc/apt/apt.conf.d/01proxy"
- # work around LP#1548878
- lxc exec "$CONTAINER" -- chmod 644 /etc/apt/apt.conf.d/01proxy
- fi
-
- # wait until it is booted: lxc exec works and we get a numeric runlevel
- timeout=60
- while [ $timeout -ge 0 ]; do
- timeout=$((timeout - 1))
- sleep 1
- O=`lxc exec "$CONTAINER" runlevel 2>/dev/null </dev/null` || continue
- [ "$O" = "${O%[0-9]}" ] || break
- done
- [ $timeout -ge 0 ] || {
- echo "Timed out waiting for container to boot" >&2
- exit 1
- }
-
- ARCH=$(lxc exec "$CONTAINER" -- dpkg --print-architecture </dev/null)
- DISTRO=$(lxc exec "$CONTAINER" -- sh -ec 'lsb_release -si 2>/dev/null || . /etc/os-release; echo "${NAME% *}"' </dev/null)
- RELEASE=$(lxc exec "$CONTAINER" -- sh -ec 'lsb_release -sc 2>/dev/null || awk "/^deb/ {sub(/\\[.*\\]/, \"\", \$0); print \$3; quit}" /etc/apt/sources.list' </dev/null)
- echo "Container finished booting. Distribution $DISTRO, release $RELEASE, architecture $ARCH"
-
- # find setup-testbed script
- for script in $(dirname $(dirname "$0"))/setup-commands/setup-testbed \
- /usr/share/autopkgtest/setup-commands/setup-testbed; do
- if [ -r "$script" ]; then
- echo "Running setup script $script..."
- lxc exec "$CONTAINER" -- sh < "$script"
- break
- fi
- done
- lxc stop "$CONTAINER"
-}
-
-#
-# main
-#
-
-if [ -z "${1:-}" ]; then
- echo "Usage: $0 <image>" >&2
- exit 1
-fi
-IMAGE="$1"
-CONTAINER=''
-trap '[ -z "$CONTAINER" ] || lxc delete -f "$CONTAINER"' EXIT INT QUIT PIPE
-
-proxy_detect
-generate_container_name
-lxc launch "$IMAGE" "$CONTAINER"
-setup
-
-# if there already is a published image, get its fingerprint to clean it up
-# afterwards
-DISTROLC=$(echo "$DISTRO" | tr '[:upper:]' '[:lower:]')
-ALIAS="adt/$DISTROLC/$RELEASE/$ARCH"
-DESCRIPTION="autopkgtest $DISTRO $RELEASE $ARCH"
-
-lxc publish "$CONTAINER" --alias "$ALIAS" --public description="$DESCRIPTION" distribution="$DISTROLC" release="$RELEASE" architecture="$ARCH"
-
-# clean up old images
-for i in $(lxc image list | grep "$DESCRIPTION" | grep -v "$ALIAS" | cut -d'|' -f3); do
- echo "Removing previous image $i"
- lxc image delete "$i"
-done
diff --git a/reprotest/tools/adt-build-lxd.1 b/reprotest/tools/adt-build-lxd.1
deleted file mode 100644
index 05491d3..0000000
--- a/reprotest/tools/adt-build-lxd.1
+++ /dev/null
@@ -1,48 +0,0 @@
-.TH adt-build-lxd 1 2015 "Linux Programmer's Manual"
-.SH NAME
-adt-build-lxd \- Create or update autopkgtest container for adt\-virt-lxd
-
-.SH SYNOPSIS
-.B adt-build-lxd
-.I image
-
-.SH DESCRIPTION
-.B adt-build-lxd
-creates or updates an LXD image which is optimized for autopkgtest's LXD runner
-.BR adt-virt-lxd (1).
-
-It builds a temporary container from an existing given image, runs
-autopkgtest's standard
-.B setup-commands/setup-testbed
-script, and publishes it as a new image with the alias
-\fBadt-\fIdistro\fR-\fIrelease\fR-\fIarchitecture\fR.
-
-You can specify an apt proxy to use in the container in the
-.B $ADT_APT_PROXY
-environment variable. If you have an apt proxy configured on the host, the
-container will automatically use this, otherwise there is no default.
-
-.SH EXAMPLE
-
-Build a local autopkgtest container image for Debian sid i386, based on the
-stock Debian image from the public
-.B images.linuxcontainers.org
-remote:
-
-$ adt-build-lxd images:debian/sid/i386
-
-.SH SEE ALSO
-\fBadt\-virt-lxd\fR(1),
-\fBadt\-run\fR(1),
-\fBlxc\fR(1),
-\fB/usr/share/doc/autopkgtest/\fR.
-
-.SH AUTHORS AND COPYRIGHT
-.B adt-build-lxd
-was written by Martin Pitt <martin.pitt at ubuntu.com>
-
-This manpage is part of autopkgtest, a tool for testing Debian binary
-packages. autopkgtest is Copyright (C) 2006-2015 Canonical Ltd and others.
-
-See \fB/usr/share/doc/autopkgtest/CREDITS\fR for the list of
-contributors and full copying conditions.
diff --git a/reprotest/tools/adt-buildvm-ubuntu-cloud b/reprotest/tools/adt-buildvm-ubuntu-cloud
deleted file mode 100755
index 26dea71..0000000
--- a/reprotest/tools/adt-buildvm-ubuntu-cloud
+++ /dev/null
@@ -1,329 +0,0 @@
-#!/usr/bin/python3
-#
-# Licensed under the GPL: https://www.gnu.org/licenses/gpl-3.0.en.html
-# For details: reprotest/debian/copyright
-
-import argparse
-import tempfile
-import sys
-import subprocess
-import shutil
-import atexit
-import urllib.request
-import os
-import time
-import re
-
-sys.path.insert(0, '/usr/share/autopkgtest/python')
-sys.path.insert(0, os.path.join(os.path.dirname(os.path.dirname(
- os.path.abspath(__file__))), 'lib'))
-
-import VirtSubproc
-
-workdir = tempfile.mkdtemp(prefix='adt-buildvm-ubuntu-cloud')
-atexit.register(shutil.rmtree, workdir)
-
-
-def get_default_release():
- try:
- import distro_info
- try:
- return distro_info.UbuntuDistroInfo().devel()
- except distro_info.DistroDataOutdated:
- # right after a release there is no devel series, fall back to
- # stable
- sys.stderr.write('WARNING: cannot determine development release, '
- 'falling back to latest stable\n')
- return distro_info.UbuntuDistroInfo().stable()
- except ImportError:
- sys.stderr.write('WARNING: python-distro-info not installed, falling '
- 'back to determining default release from currently '
- 'installed release\n')
- if subprocess.call(['which', 'lsb_release'], stdout=subprocess.PIPE) == 0:
- return subprocess.check_output(['lsb_release', '-cs'],
- universal_newlines=True).strip()
-
-
-def parse_args():
- '''Parse CLI args'''
-
- # use host's apt proxy
- default_proxy = ''
- try:
- p = subprocess.check_output(
- 'eval `apt-config shell p Acquire::http::Proxy`; echo $p',
- shell=True, universal_newlines=True).strip()
- if p:
- # translate proxy on localhost to QEMU IP
- default_proxy = re.sub('localhost|127\.0\.0\.[0-9]*', '10.0.2.2', p)
- except subprocess.CalledProcessError:
- pass
-
- parser = argparse.ArgumentParser(fromfile_prefix_chars='@')
-
- default_arch = subprocess.check_output(['dpkg', '--print-architecture'],
- universal_newlines=True).strip()
- uname_to_qemu_suffix = {'i[3456]86$': 'i386'}
- arch = os.uname()[4]
- for pattern, suffix in uname_to_qemu_suffix.items():
- if re.match(pattern, arch):
- qemu_cmd_default = 'qemu-system-' + suffix
- break
- else:
- qemu_cmd_default = 'qemu-system-' + arch
-
- parser.add_argument('-a', '--arch', default=default_arch,
- help='Ubuntu architecture (default: %(default)s)')
- parser.add_argument('-r', '--release', metavar='CODENAME',
- default=get_default_release(),
- help='Ubuntu release code name (default: %(default)s)')
- parser.add_argument('-m', '--mirror', metavar='URL',
- default='http://archive.ubuntu.com/ubuntu',
- help='Use this mirror for apt (default: %(default)s)')
- parser.add_argument('-p', '--proxy', metavar='URL', default=default_proxy,
- help='Use a proxy for apt (default: %s)' % (
- default_proxy or 'none'))
- parser.add_argument('-s', '--disk-size', default='20G',
- help='grow image by this size (default: %(default)s)')
- parser.add_argument('-o', '--output-dir', metavar='DIR', default='.',
- help='output directory for generated image (default: '
- 'current directory)')
- parser.add_argument('-q', '--qemu-command',
- default=qemu_cmd_default,
- help='qemu command (default: %(default)s)')
- parser.add_argument('-v', '--verbose', action='store_true', default=False,
- help='Show VM guest and cloud-init output')
- parser.add_argument('--cloud-image-url', metavar='URL',
- default='https://cloud-images.ubuntu.com',
- help='cloud images URL (default: %(default)s)')
- parser.add_argument('--no-apt-upgrade', action='store_true',
- help='Do not run apt-get dist-upgrade')
- parser.add_argument('--post-command',
- help='Run shell command in VM after setup')
- parser.add_argument('--metadata', metavar='METADATA_FILE',
- help='Custom metadata file for cloud-init.')
- parser.add_argument('--userdata', metavar='USERDATA_FILE',
- help='Custom userdata file for cloud-init.')
- parser.add_argument('--timeout', metavar='SECONDS', default=3600, type=int,
- help='Timeout for cloud-init (default: %(default)i s)')
-
- args = parser.parse_args()
-
- # check our dependencies
- if subprocess.call(['which', args.qemu_command], stdout=subprocess.PIPE,
- stderr=subprocess.STDOUT) != 0:
- sys.stderr.write('ERROR: QEMU command %s not found\n' %
- args.qemu_command)
- sys.exit(1)
- if subprocess.call(['which', 'genisoimage'], stdout=subprocess.PIPE,
- stderr=subprocess.STDOUT) != 0:
- sys.stderr.write('ERROR: genisoimage not found\n')
- sys.exit(1)
- if os.path.exists('/dev/kvm') and not os.access('/dev/kvm', os.W_OK):
- sys.stderr.write('ERROR: no permission to write /dev/kvm\n')
- sys.exit(1)
-
- return args
-
-
-def download_image(cloud_img_url, release, arch):
- diskname = '%s-server-cloudimg-%s-disk1.img' % (release, arch)
- image_url = '%s/%s/current/%s' % (cloud_img_url, release, diskname)
- local_image = os.path.join(workdir, diskname)
-
- print('Downloading %s...' % image_url)
-
- is_tty = os.isatty(sys.stdout.fileno())
- download_image.lastpercent = 0
-
- def report(numblocks, blocksize, totalsize):
- cur_bytes = numblocks * blocksize
- if totalsize > 0:
- percent = int(cur_bytes * 100. / totalsize + .5)
- else:
- percent = 0
- if is_tty:
- if percent > download_image.lastpercent:
- download_image.lastpercent = percent
- sys.stdout.write('\r%.1f/%.1f MB (%i%%) ' % (
- cur_bytes / 1000000.,
- totalsize / 1000000.,
- percent))
- sys.stdout.flush()
- else:
- if percent >= download_image.lastpercent + 10:
- download_image.lastpercent = percent
- sys.stdout.write('%i%% ' % percent)
- sys.stdout.flush()
-
- headers = urllib.request.urlretrieve(image_url, local_image, report)[1]
- if headers['content-type'] not in ('application/octet-stream',
- 'text/plain'):
- sys.stderr.write('\nDownload failed!\n')
- sys.exit(1)
- print('\nDownload successful.')
-
- return local_image
-
-
-def resize_image(image, size):
- print('Resizing image, adding %s...' % size)
- subprocess.check_call(['qemu-img', 'resize', image, '+' + size])
-
-
-DEFAULT_METADATA = 'instance-id: nocloud\nlocal-hostname: autopkgtest\n'
-
-
-DEFAULT_USERDATA = """#cloud-config
-locale: en_US.UTF-8
-timezone: %(tz)s
-password: ubuntu
-chpasswd: { expire: False }
-ssh_pwauth: True
-manage_etc_hosts: True
-apt_proxy: %(proxy)s
-apt_mirror: %(mirror)s
-runcmd:
- - sed -i 's/deb-systemd-invoke/true/' /var/lib/dpkg/info/cloud-init.prerm
- - mount -r /dev/vdb /mnt
- - env ADT_SETUP_VM_UPGRADE=%(upgr)s ADT_SETUP_VM_POST_COMMAND='%(postcmd)s'
- sh /mnt/setup-testbed
- - if grep -q 'net.ifnames=0' /proc/cmdline; then ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules; update-initramfs -u; fi
- - umount /mnt
- - (while [ ! -e /var/lib/cloud/instance/boot-finished ]; do sleep 1; done;
- apt-get -y purge cloud-init; shutdown -P now) &
-"""
-
-
-def build_seed(mirror, proxy, no_apt_upgrade, metadata_file=None,
- userdata_file=None, post_command=None):
- print('Building seed image...')
- if metadata_file:
- metadata = open(metadata_file).read()
- else:
- metadata = DEFAULT_METADATA
- with open(os.path.join(workdir, 'meta-data'), 'w') as f:
- f.write(metadata)
-
- upgr = no_apt_upgrade and 'false' or 'true'
- if userdata_file:
- userdata = open(userdata_file).read()
- else:
- userdata = DEFAULT_USERDATA % {'proxy': proxy or '', 'mirror': mirror,
- 'upgr': upgr, 'tz': host_tz(),
- 'postcmd': post_command or ''}
-
- # preserve proxy from host
- for v in ['http_proxy', 'https_proxy', 'no_proxy']:
- if v not in os.environ:
- continue
- val = os.environ[v]
- if v != 'no_proxy':
- # translate localhost addresses
- val = val.replace('localhost', '10.0.2.2').replace(
- '127.0.0.1', '10.0.2.2')
- userdata += ''' - [ sh, -c, 'echo "%s=%s" >> /etc/environment' ]\n''' \
- % (v, val)
-
- with open(os.path.join(workdir, 'user-data'), 'w') as f:
- f.write(userdata)
-
- # find setup-testbed, copy it into the VM via the cloud-init seed iso
- for script in [os.path.join(os.path.dirname(os.path.abspath(os.path.dirname(__file__))),
- 'setup-commands', 'setup-testbed'),
- '/usr/share/autopkgtest/setup-commands/setup-testbed']:
- if os.path.exists(script):
- shutil.copy(script, workdir)
- break
- else:
- sys.stderr.write('\nCould not find setup-testbed script\n')
- sys.exit(1)
-
- genisoimage = subprocess.Popen(['genisoimage', '-output', 'adt.seed',
- '-volid', 'cidata', '-joliet', '-rock',
- '-quiet', 'user-data', 'meta-data',
- 'setup-testbed'],
- cwd=workdir)
- genisoimage.communicate()
- if genisoimage.returncode != 0:
- sys.exit(1)
-
- return os.path.join(workdir, 'adt.seed')
-
-
-def host_tz():
- '''Return host timezone.
-
- Defaults to Etc/UTC if it cannot be determined
- '''
- if os.path.exists('/etc/timezone'):
- with open('/etc/timezone', 'rb') as f:
- for l in f:
- if l.startswith(b'#'):
- continue
- l = l.strip()
- if l:
- return l.decode()
-
- return 'Etc/UTC'
-
-
-def boot_image(image, seed, qemu_command, verbose, timeout):
- print('Booting image to run cloud-init...')
-
- tty_sock = os.path.join(workdir, 'ttyS0')
-
- argv = [qemu_command, '-m', '512',
- '-nographic',
- '-monitor', 'null',
- '-net', 'user',
- '-net', 'nic,model=virtio',
- '-serial', 'unix:%s,server,nowait' % tty_sock,
- '-drive', 'file=%s,if=virtio' % image,
- '-drive', 'file=%s,if=virtio,readonly' % seed]
-
- if os.path.exists('/dev/kvm'):
- argv.append('-enable-kvm')
-
- qemu = subprocess.Popen(argv)
- try:
- if verbose:
- tty = VirtSubproc.get_unix_socket(tty_sock)
-
- # wait for cloud-init to finish and VM to shutdown
- with VirtSubproc.timeout(timeout, 'timed out on cloud-init'):
- while qemu.poll() is None:
- if verbose:
- sys.stdout.buffer.raw.write(tty.recv(4096))
- else:
- time.sleep(1)
- finally:
- if qemu.poll() is None:
- qemu.terminate()
- if qemu.wait() != 0:
- sys.stderr.write('qemu failed with status %i\n' % qemu.returncode)
- sys.exit(1)
-
-
-def install_image(src, dest):
- # We want to atomically update dest, and in case multiple instances are
- # running the last one should win. So we first copy/move it to
- # dest.<currenttime> (which might take a while for crossing file systems),
- # then atomically rename to dest.
- print('Moving image into final destination %s' % dest)
- desttmp = dest + str(time.time())
- shutil.move(image, desttmp)
- os.rename(desttmp, dest)
-
-#
-# main
-#
-
-args = parse_args()
-image = download_image(args.cloud_image_url, args.release, args.arch)
-resize_image(image, args.disk_size)
-seed = build_seed(args.mirror, args.proxy, args.no_apt_upgrade,
- args.metadata, args.userdata, args.post_command)
-boot_image(image, seed, args.qemu_command, args.verbose, args.timeout)
-install_image(image, os.path.join(args.output_dir, 'adt-%s-%s-cloud.img' %
- (args.release, args.arch)))
diff --git a/reprotest/tools/adt-buildvm-ubuntu-cloud.1 b/reprotest/tools/adt-buildvm-ubuntu-cloud.1
deleted file mode 100644
index 1d0dde3..0000000
--- a/reprotest/tools/adt-buildvm-ubuntu-cloud.1
+++ /dev/null
@@ -1,146 +0,0 @@
-.TH adt-buildvm-ubuntu-cloud 1 2014 "Linux Programmer's Manual"
-.SH NAME
-adt-buildvm-ubuntu-cloud \- Create Ubuntu cloud image based VM for adt\-virt-qemu
-
-.SH SYNOPSIS
-.B adt-buildvm-ubuntu-cloud
-.RI [ options ]
-
-.SH DESCRIPTION
-.B adt-buildvm-ubuntu-cloud
-downloads an Ubuntu cloud image and configures it for autopkgtest's QEMU runner
-(\fBadt-virt-qemu\fR):
-
-.IP * 4
-Resize the image to 6 GB (by default, you can change this with an option),
-which ought to be sufficient for most tests.
-
-.IP * 4
-Create an user "ubuntu" with password "ubuntu".
-
-.IP * 4
-Add apt sources for "restricted" and "multiverse" components.
-
-.IP * 4
-Create an init.d script to start a root shell on ttyS1 at boot, so that
-.B adt-virt-qemu
-can be used without additional arguments or logging in through ttyS0.
-
-You can select release, architecture, apt proxy, etc. with options. The
-defaults are aimed at testing the development series of the architecture of
-your host system.
-
-.SH OPTIONS
-
-.TP
-.BI -a " arch" " | --arch=" arch
-Ubuntu architecture name, e. g. "i386" or "amd64". Default is the host system
-architecture.
-
-.TP
-.BI -r " codename" " | --release=" codename
-Ubuntu release code name, e. g. "trusty". Default is the current development
-series (this needs
-.B python-distro-info
-installed).
-
-.TP
-.BI -m " URL" " | --mirror=" URL
-Mirror for apt (default:
-.B http://archive.ubuntu.com/ubuntu\fR).
-
-.TP
-.BI -p " URL" " | --proxy=" URL
-Proxy for apt. If you have an apt proxy configured on the local host, the VM
-will automatically use this; otherwise there is no default.
-
-
-.TP
-.BI --cloud-image-url= URL
-URL from where to download the cloud images (default:
-http://cloud-images.ubuntu.com).
-
-.TP
-.BI -s " DISK_SIZE" " | --disk-size=" DISK_SIZE
-Grow downloaded image (which have a default size of 2GB) by this size (default:
-.B 4G\fR, i. e. the image will be 6GB big in total).
-
-.TP
-.BI -o " DIR" " | --output-dir=" DIR
-Output directory for generated image (default: current directory).
-
-.TP
-.BI -q " command" " | --qemu-command=" command
-QEMU command to run. This defaults to the
-.B qemu-system-*
-that matches your system architecture.
-
-.TP
-.BR \-v " | " \-\-verbose
-Show VM guest and cloud-init output.
-
-.TP
-.B --no-apt-upgrade
-Do not run apt-get dist-upgrade during initialization.
-
-.TP
-.BI "--post-command=" COMMAND
-Run shell command in the VM after the setup.
-
-.TP
-.BI "--metadata=" METADATA_FILE
-Use a custom cloud-init metadata file to initialize the cloud image VM.
-
-.TP
-.BI "--userdata=" USERDATA_FILE
-Use a custom cloud-init userdata file to initialize the cloud image VM.
-
-.TP
-.BI "--timeout=" SECONDS
-Timeout for cloud-init. Default is 3600 s.
-
-.SH CONFIGURATION FILES
-If you use lots of options, you can put parts of, or the whole
-command line into a text file, with one line per option. E. g. you can create a
-file
-.I trusty-i386.cfg
-with contents like
-
-.RS
-.EX
--rtrusty
--ai386
---proxy=http://mysquid.mynetwork
--v
-.EE
-.RE
-
-and then run
-
-.RS
-.EX
-adt-buildvm-ubuntu-cloud @trusty-i386.cfg
-.EE
-.RE
-
-The contents of the configuration file will be expanded in-place as if you
-would have given its contents on the command line. Please ensure that you
-.B don't place spaces
-between short options and their values, they would become a part of the
-argument value.
-
-.SH SEE ALSO
-\fBadt\-virt-qemu\fR(1),
-\fBadt\-run\fR(1),
-\fBhttp://cloud-images.ubuntu.com\fR,
-\fB/usr/share/doc/autopkgtest/\fR.
-
-.SH AUTHORS AND COPYRIGHT
-.B adt-buildvm-ubuntu-cloud
-was written by Martin Pitt <martin.pitt at ubuntu.com>
-
-This manpage is part of autopkgtest, a tool for testing Debian binary
-packages. autopkgtest is Copyright (C) 2006-2014 Canonical Ltd and others.
-
-See \fB/usr/share/doc/autopkgtest/CREDITS\fR for the list of
-contributors and full copying conditions.
diff --git a/reprotest/virt/autopkgtest-chroot.1 b/reprotest/virt/autopkgtest-chroot.1
deleted file mode 100644
index 28840a0..0000000
--- a/reprotest/virt/autopkgtest-chroot.1
+++ /dev/null
@@ -1,65 +0,0 @@
-.TH adt\-virt\-chroot 1 2007 autopkgtest "Linux Programmer's Manual"
-.SH NAME
-adt\-virt\-chroot \- autopkgtest virtualisation server using a chroot
-.SH SYNOPSIS
-.B adt\-virt\-chroot
-.RI [ options ]
-.RI [\fB\-r\fR gain\-root\-cmd ]
-.I /path/to/chroot
-.SH DESCRIPTION
-.B adt\-virt\-chroot
-provides an autopkgtest virtualisation server using a chroot install
-(or similar).
-
-Normally
-.B adt-virt-chroot
-will be invoked by
-.BR adt-run .
-
-The chroot directory to use must be specified.
-
-.SH OPTIONS
-.TP
-.BR \-\-gain\-root | \-r " \fIgain\-root\-cmd\fR"
-Specifies that
-.B adt-virt-chroot
-can become root (on the host) by prefixing its commands with
-.IR gain-root-cmd .
-The command may consist of several words separated by whitespace,
-in which case words other than the first are supplied as additional
-arguments to the command; other shell (or other) metacharacters in
-.IR gain-root-cmd
-are not interpreted or modified by
-.BR adt-virt-chroot .
-The actual command to be run as root, and
-its arguments, are supplied as additional (separate) arguments to
-.IR gain-root-cmd .
-
-Root privilege is needed, to successfully run
-.BR chroot (8),
-if the chroot to use is specified as an absolute path. The default is
-not to take any special action when root will be needed, in which case
-for an absolute path chroot,
-.B adt-virt-chroot
-must be started as root.
-.TP
-.BR \-d " | " \-\-debug
-Enables debugging output. Probably not hugely interesting.
-
-.SH INPUT, OUTPUT AND EXIT STATUS
-The behaviour of
-.B adt-virt-chroot
-is as described by the AutomatedTesting virtualisation regime
-specification.
-
-.SH SEE ALSO
-\fBadt\-run\fR(1),
-\fBadt\-virt-schroot\fR(1),
-\fB/usr/share/doc/autopkgtest/\fR.
-
-.SH AUTHORS AND COPYRIGHT
-This manpage is part of autopkgtest, a tool for testing Debian binary
-packages. autopkgtest is Copyright (C) 2006-2007 Canonical Ltd and others.
-
-See \fB/usr/share/doc/autopkgtest/CREDITS\fR for the list of
-contributors and full copying conditions.
diff --git a/reprotest/virt/autopkgtest-lxc.1 b/reprotest/virt/autopkgtest-lxc.1
deleted file mode 100644
index 53004b5..0000000
--- a/reprotest/virt/autopkgtest-lxc.1
+++ /dev/null
@@ -1,133 +0,0 @@
-.TH adt\-virt-lxc 1 2013 "Linux Programmer's Manual"
-.SH NAME
-adt\-virt\-lxc \- autopkgtest virtualisation server using LXC
-
-.SH SYNOPSIS
-.B adt\-virt\-lxc
-.RI [ options ]
-.I lxc\-container
-.RI [ "-- extra lxc-start args..." ]
-
-.SH DESCRIPTION
-.B adt-virt-lxc
-provides an autopkgtest virtualisation server using LXC. It adapts the raw
-functionality provided by the
-.BR lxc- *
-tools for use by autopkgtest.
-
-Normally
-.B adt-virt-lxc
-will be invoked by
-.BR adt-run .
-
-You can conveniently create a suitable container using the
-.BR adt-build-lxc (1)
-script.
-
-.SH REQUIREMENTS
-.B adt-virt-lxc
-assumes that you have already prepared a suitable Debian based LXC container.
-See
-.BR lxc-create (1)
-for how to create containers, and particularly
-.BR adt-build-lxc (1)
-for conveniently creating standard autopkgtest containers.
-
-.SH OPTIONS
-
-.TP
-.BR -e " | " \-\-ephemeral
-This option makes use of lxc-start-ephemeral to create temporary container
-overlays, instead of the default behaviour of cloning your containers.
-
-This can be used to dramatically improve performance, although you may see
-issues due to the overlayfs filesystem as used by lxc-start-ephemeral not being
-completely transparent (e. g. seen with tar failing when running LXC within
-Qemu). Before using this option in automation you should ensure that tests that
-involve large I/O work as expected.
-
-Note that ephemeral containers do not support rebooting with LXC 1.x. This does
-work with LXC >= 2.x.
-
-.TP
-.BR \-s " | " \-\-sudo
-Run lxc-* commands through sudo; use this option if you run adt-run as normal
-user, but need to run the container itself as root (if you use LXC system level
-containers).
-
-.TP
-.BI " \-\-name" " NAME
-Set a custom name for the temporary container in which to run the test. This is
-autogenerated by default (adt-virt-lxc-\fIXXXXXX\fR), but if you have a way to
-generate more expressive unique names you can use that to make it easier to map
-containers to running tests.
-
-.TP
-.BR \-d " | " \-\-debug
-Enables debugging output.
-
-.PP
-You can pass additional options to LXC: Anything after a
-.B --
-gets passed verbatim to
-.BR lxc-start / lxc-start-ephemeral .
-
-.SH INPUT, OUTPUT AND EXIT STATUS
-The behaviour of
-.B adt-virt-lxc
-is as described by the AutomatedTesting virtualisation regime
-specification.
-
-.SH NOTES
-
-\fBadt-run\fR does not run \fBapt-get update\fR at the start of a package
-build, which can cause a build failure if you are using a development release
-template. You will need to run \fBapt-get update\fR in the template yourself
-(e. g. using \fB\-\-setup\-commands\fR).
-
-.SH EXAMPLE
-
-Create a suitable debootstrap-based container for Debian or Ubuntu template, e.
-g. a Debian sid one (will be named
-.B adt-sid\fR):
-
-.RS
-.EX
-adt-build-lxc debian sid
-.EE
-.RE
-
-Or an Ubuntu one based on the cloud images (faster than adt-build-lxc's
-"ubuntu" template with debootstrap, but much bigger):
-
-.RS
-.EX
-lxc-create -t ubuntu-cloud -n \fIadt-trusty\fR -- -r trusty -d daily
-.EE
-.RE
-
-Run tests against \fIhello_2.8\-4.dsc\fR, using the LXC container \fIadt-sid\fR,
-and with an ephemeral overlay for speed:
-
-.RS
-.EX
-adt-run \fIhello_2.8\-4.dsc\fR --- adt-virt-lxc -e \fIadt-sid\fR
-.EE
-.RE
-
-.SH SEE ALSO
-\fBadt\-run\fR(1),
-\fBadt\-build-lxc\fR(1),
-\fBlxc\-create\fR(1),
-\fB/usr/share/doc/autopkgtest/\fR.
-
-.SH AUTHORS AND COPYRIGHT
-.B adt-virt-lxc
-was written by Robie Basak <robie.basak at canonical.com> and Martin Pitt
-<martin.pitt at ubuntu.com>.
-
-This manpage is part of autopkgtest, a tool for testing Debian binary
-packages. autopkgtest is Copyright (C) 2006-2013 Canonical Ltd and others.
-
-See \fB/usr/share/doc/autopkgtest/CREDITS\fR for the list of
-contributors and full copying conditions.
diff --git a/reprotest/virt/autopkgtest-lxd.1 b/reprotest/virt/autopkgtest-lxd.1
deleted file mode 100644
index d81928b..0000000
--- a/reprotest/virt/autopkgtest-lxd.1
+++ /dev/null
@@ -1,134 +0,0 @@
-.TH adt\-virt-lxd 1 2013 "Linux Programmer's Manual"
-.SH NAME
-adt\-virt\-lxd \- autopkgtest virtualisation server using LXD
-
-.SH SYNOPSIS
-.B adt\-virt\-lxd
-.RI [ options ]
-.I image
-.RI [ "-- extra lxc launch args..." ]
-
-.SH DESCRIPTION
-.B adt-virt-lxd
-provides an autopkgtest virtualisation server using LXD. It creates temporary
-containers from the given LXD image name.
-
-Normally
-.B adt-virt-lxd
-will be invoked by
-.BR adt-run .
-
-.SH REQUIREMENTS
-.B adt-virt-lxd
-makes no strict assumptions about the image. However, it is highly
-recommended that the image has eatmydata installed, or at least that gets
-installed via setup commands.
-
-For production use, it is recommended to use
-.BR adt-build-lxd (1)
-to generate an optimized image with autopkgtest's standard setup commands
-applied. Then these setup commands don't need to be applied for every test.
-This is particularly necessary if you want to use
-.B --apt-source
-tests, i. e. use
-.B apt-get source
-in the test bed to download the package to test. Standard images from
-.B linuxcontainers.org
-do not have "deb-src" apt sources by default.
-
-.SH OPTIONS
-
-.TP
-.BI -r " remote" " | --remote=" remote
-Run container on given remote host instead of locally. See
-.B lxc remote list
-for available remotes.
-
-.TP
-.BR \-d " | " \-\-debug
-Enables debugging output.
-
-.PP
-You can pass additional options to
-.B lxd launch\fR:
-Anything after a
-.B --
-gets appended verbatim to
-.BI "lxc launch " image\fR.
-
-.SH INPUT, OUTPUT AND EXIT STATUS
-The behaviour of
-.B adt-virt-lxd
-is as described by the AutomatedTesting virtualisation regime
-specification.
-
-.SH EXAMPLE
-
-Show available images on the standard
-.B linuxcontainers.org
-remote image server:
-
-.RS
-.EX
-lxc image list images:
-.EE
-.RE
-
-Run the tests of a local built directory tree on the current Debian sid
-image from the above
-.B images:
-remote:
-
-.RS
-.EX
-adt-run my-package/ --- lxd images:debian/sid/amd64
-.EE
-.RE
-
-Run the tests in a local built directory tree from a local LXD image
-.B desktop/i386\fR,
-ensuring that eatmydata is installed:
-
-.RS
-.EX
-adt-run --setup-commands 'apt-get install -y eatmydata' dir/to/test/ \\
- --- lxd desktop/i386
-.EE
-.RE
-
-Run the tests of the
-.B libpng
-package on the current Debian sid image from the
-.B images:
-remote on a remote armhf host:
-
-.RS
-.EX
-lxc remote add armhf-test http://armhf.testlab.example.com:8443
-adt-run --setup-commands=setup-testbed libpng --- \\
- lxd --remote armhf-test images:debian/sid/armhf
-.EE
-.RE
-
-Build a local image with standard setup commands pre-applied from a remote
-standard image, and run libpng test in it:
-
-.RS
-.EX
-adt-build-lxd images:ubuntu/xenial/amd64
-adt-run libpng --- lxd adt/ubuntu/xenial/amd64
-
-.SH SEE ALSO
-\fBadt\-run\fR(1),
-\fBadt\-build-lxd\fR(1),
-\fB/usr/share/doc/autopkgtest/\fR.
-
-.SH AUTHORS AND COPYRIGHT
-.B adt-virt-lxd
-was written by Martin Pitt <martin.pitt at ubuntu.com>.
-
-This manpage is part of autopkgtest, a tool for testing Debian binary
-packages. autopkgtest is Copyright (C) 2006-2015 Canonical Ltd and others.
-
-See \fB/usr/share/doc/autopkgtest/CREDITS\fR for the list of
-contributors and full copying conditions.
diff --git a/reprotest/virt/autopkgtest-null.1 b/reprotest/virt/autopkgtest-null.1
deleted file mode 100644
index f7197a6..0000000
--- a/reprotest/virt/autopkgtest-null.1
+++ /dev/null
@@ -1,42 +0,0 @@
-.TH adt\-virt\-null 1 2007 autopkgtest "Linux Programmer's Manual"
-.SH NAME
-adt\-virt\-null \- autopkgtest null virtualisation server
-.SH SYNOPSIS
-.B adt\-virt\-null
-.RI [ options ]
-.br
-.SH DESCRIPTION
-.B adt\-virt\-null
-provides a dummy autopkgtest virtualisation server which does not
-actually offer any kind of separation between host and testbed.
-
-Normally
-.B adt-virt-null
-will be invoked by
-.BR adt-run .
-
-There is of course no locking; nothing prevents multiple simultaneous
-programs from invoking
-.B adt-virt-null
-so as to reuse the same system as a testbed.
-.SH OPTIONS
-.TP
-.BR \-d " | " \-\-debug
-Enables debugging output. Probably not hugely interesting.
-
-.SH INPUT, OUTPUT AND EXIT STATUS
-The behaviour of
-.B adt-virt-null
-is as described by the AutomatedTesting virtualisation regime
-specification.
-
-.SH SEE ALSO
-\fBadt\-run\fR(1),
-\fB/usr/share/doc/autopkgtest/\fR.
-
-.SH AUTHORS AND COPYRIGHT
-This manpage is part of autopkgtest, a tool for testing Debian binary
-packages. autopkgtest is Copyright (C) 2006-2007 Canonical Ltd and others.
-
-See \fB/usr/share/doc/autopkgtest/CREDITS\fR for the list of
-contributors and full copying conditions.
diff --git a/reprotest/virt/autopkgtest-qemu.1 b/reprotest/virt/autopkgtest-qemu.1
deleted file mode 100644
index 1f6878b..0000000
--- a/reprotest/virt/autopkgtest-qemu.1
+++ /dev/null
@@ -1,252 +0,0 @@
-.TH adt\-virt-qemu 1 2014 "Linux Programmer's Manual"
-.SH NAME
-adt\-virt\-qemu \- autopkgtest virtualisation server using QEMU
-
-.SH SYNOPSIS
-.B adt\-virt\-qemu
-.RI [ options ]
-.I image \fR[\fIro-image\fR ...]
-
-.SH DESCRIPTION
-.B adt-virt-qemu
-provides an autopkgtest virtualisation server using QEMU.
-
-Normally
-.B adt-virt-qemu
-will be invoked by
-.BR adt-run .
-
-You always need to specify at least one QEMU VM image. If your VM needs
-more disks, you can specify arbitrarily many additional images which will
-be added in order.
-
-.B adt-virt-qemu
-does
-.B not modify
-the given images, but will instead create a temporary overlay for the
-primary image, and add all other images as read-only.
-
-The first image without the overlay is always added as an additional
-read-only hard drive, which will be available for tests as
-.IR /dev/baseimage .
-This allows tests that require nested VMs to reuse the same image. Be
-aware that
-.I /dev/baseimage
-will not be accessible between calling
-.B adt-reboot-prepare
-and the next boot, thus make sure to stop accessing it before.
-
-.SH REQUIREMENTS
-.B adt-virt-qemu
-assumes that you have already prepared a suitable Debian based QEMU image (see
-.B BUILDING IMAGES
-below for how to create them). But you can use any VM which has
-.B python3
-or
-.B python
-installed and either
-
-.IP * 4
-opens a root shell on ttyS1, or
-
-.IP * 4
-has a serial console on ttyS0 where you can log in (getty or similar)
-with specified user and password. This will then be used to start a root
-shell on ttyS1, to reduce this to the first case and to not assume that
-ttyS0 stays operational throughout the whole test.
-
-.SH OPTIONS
-
-.TP
-.BI -u " user" " | --user=" user
-
-User name for running tests that don't require root privileges.
-
-If the VM is not already prepared to start a root shell on ttyS1 this will be
-also used for logging in on ttyS0. If this is not root, it must be able to run
-sudo without a password to become root for that purpose.
-
-.TP
-.BI -p " password" " | --password=" password
-Password for above user for logging into the VM on ttyS0. This is necessary
-if the VM is not already prepared to start a root shell on ttyS1.
-
-.TP
-.BI -q " command" " | --qemu-command=" command
-QEMU command to run. This defaults to the
-.B qemu-system-*
-that matches your system architecture.
-
-.TP
-.BI -o " dir" " | --overlay-dir=" dir
-Directory where the temporary image overlay for the primary image is
-created. By default this will happen in a work directory in
-.I /tmp
-(or \fI$TMPDIR\fR), but you can use this to e. g. ensure that the overlay
-is placed on a tmpfs if your
-.I /tmp
-directory is not on tmpfs. This will greatly increase the speed.
-
-.TP
-.BI -c " num" " | --cpus=" num"
-Number of (virtual) CPUs in the VM. Default is 1.
-
-.TP
-.BI "--ram-size=" MiB
-VM RAM size in MiB. Default is 1024, i. e. 1 GiB.
-
-.TP
-.B \-\-show\-boot
-Show boot messages from serial console.
-
-.TP
-.BR \-d " | " \-\-debug
-Enable debugging output.
-
-.TP
-.BI "--qemu-options=" arguments
-Pass through arguments to QEMU command; e. g. --qemu-options='-readconfig qemu.cfg'
-
-.SH CONFIGURATION FILES
-If you use lots of options or images, you can put parts of, or the whole
-command line into a text file, with one line per option. E. g. you can create a
-file
-.I sid-desktop.cfg
-with contents like
-
-.RS
-.EX
--utestuser
--ps3kr1t
---ram-size=4096
-/home/bob/autopkgtest/sid-desktop.img
-.EE
-.RE
-
-and then run
-
-.RS
-.EX
-adt-run [...] --- adt-virt-qemu @sid-desktop.cfg
-.EE
-.RE
-
-The contents of the configuration file will be expanded in-place as if you
-would have given its contents on the command line. Please ensure that you
-.B don't place spaces
-between short options and their values, they would become a part of the
-argument value.
-
-.SH INPUT, OUTPUT AND EXIT STATUS
-The behaviour of
-.B adt-virt-qemu
-is as described by the AutomatedTesting virtualisation regime
-specification.
-
-.SH NOTES
-
-\fBadt-run\fR does not run \fBapt-get update\fR at the start of a package
-build, which can cause a build failure if you are using a development
-series template. You will need to run \fBapt-get update\fR in the template
-yourself (e. g. using \fB\-\-setup\-commands\fR).
-
-If the
-.B --qemu-command
-option has not been specified and no custom CPU type was selected in
-.BR --qemu-options ,
-.B adt-virt-qemu
-will try to enable nested KVM support by default on x86_64 platforms
-if the hardware supports this. To fully enable this, one needs to
-additionally set some module parameters on the host, by creating a file
-.I /etc/modprobe.d/nested_kvm.conf
-with the contents
-
-.EX
-options kvm_intel nested=1
-options kvm_amd nested=1
-.EE
-
-and rebooting or reloading the KVM modules. It is still possible to use
-QEMU in tests without this, albeit without hardware acceleration. On
-Ubuntu systems these module options are typically already set.
-
-.SH BUILDING IMAGES
-
-.SS Debian
-
-For Debian you can use
-.BR vmdebootstrap(8)
-to build a suitable image. E. g. for unstable:
-
-.RS
-.EX
-vmdebootstrap --verbose --serial-console --distribution=sid \\
-.br
- --customize=/usr/share/autopkgtest/setup-commands/setup-testbed \\
-.br
- --user=adt/adt --size=10000000000 --grub --image=adt-sid.raw
-.br
-qemu-img convert -O qcow2 adt-sid.raw adt-sid.img
-.br
-rm adt-sid.raw
-.EE
-.RE
-
-.B vmdebootstrap
-can only create a raw format image; it is recommended to convert it to qcow2 as
-that is much smaller (in the order of 700 MB for qcow2 vs. the 10 GB as
-specified above) and also supports additional features such as snapshots or
-compression. You can run that command with setting the environment variable
-.B ADT_APT_PROXY
-to a proxy which will be used by apt in the VM. If you have an apt proxy
-configured on the host, this will be used automatically; otherwise you can run
-e. g.
-
-.RS
-.EX
-ADT_APT_PROXY=http://10.0.2.2:8080 vmdebootstrap [...]
-.EE
-.RE
-
-.SS Ubuntu
-
-For Ubuntu, autopkgtest provides \fBadt-buildvm-ubuntu-cloud\fR(1) to build a
-VM based on the Ubuntu cloud images. To create an image for the current
-development series and the i386 architecture:
-
-.RS
-.EX
-adt-buildvm-ubuntu-cloud -v -a i386
-.EE
-.RE
-
-This will produce e. g.
-.B adt-trusty-i386-cloud.img\fR.
-
-.SH EXAMPLE
-
-Run the tests of the libpng source package, using an Ubuntu cloud image:
-
-.RS
-.EX
-adt-run libpng --- adt-virt-qemu adt-trusty-i386-cloud.img
-.EE
-.RE
-
-.SH SEE ALSO
-\fBadt\-run\fR(1),
-\fBadt\-virt-schroot\fR(1),
-\fBadt\-virt-lxc\fR(1),
-\fBadt-buildvm-ubuntu-cloud\fR(1),
-\fBvmdebootstrap\fR(8),
-\fB/usr/share/doc/autopkgtest/\fR.
-
-.SH AUTHORS AND COPYRIGHT
-.B adt-virt-qemu
-was written by Martin Pitt <martin.pitt at ubuntu.com>
-
-This manpage is part of autopkgtest, a tool for testing Debian binary
-packages. autopkgtest is Copyright (C) 2006-2014 Canonical Ltd and others.
-
-See \fB/usr/share/doc/autopkgtest/CREDITS\fR for the list of
-contributors and full copying conditions.
diff --git a/reprotest/virt/autopkgtest-schroot.1 b/reprotest/virt/autopkgtest-schroot.1
deleted file mode 100644
index cd6fd17..0000000
--- a/reprotest/virt/autopkgtest-schroot.1
+++ /dev/null
@@ -1,76 +0,0 @@
-.TH adt\-virt\-schroot 1 2013 autopkgtest "Linux Programmer's Manual"
-
-.SH NAME
-adt\-virt\-schroot \- autopkgtest virtualisation server using a schroot
-.SH SYNOPSIS
-.B adt\-virt\-schroot
-.RI [ options ]
-.I schroot\-name
-
-.SH DESCRIPTION
-.B adt\-virt\-schroot
-provides an autopkgtest virtualisation server using a schroot.
-Normally
-.B adt\-virt\-schroot
-will be invoked by
-.BR adt\-run .
-
-The schroot name to use must be specified.
-.B Only
-use this with schroots that provide temporary sessions, i. e. with
-.B type=file
-or
-.B type=directory
-and a configured
-.BR union\-type .
-.B adt\-virt\-schroot
-will refuse to work with a static "directory" type schroot.
-
-You can use
-.BR mk-sbuild (1)
-to conveniently create schroots.
-
-.SH PERMISSIONS
-If you can access the schroot as
-your user (according to the schroot's \fBusers\fR/\fBgroups\fR configuration),
-you should run
-.B adt\-virt\-schroot (and \fBadt\-test\fR) as normal user, too.
-
-.B adt\-virt\-schroot
-reads the schroot configuration (\fBroot-users\fR/\fBroot-groups\fR) to
-determine whether it can enter the schroot as root user; if so, it sets the
-.B root\-on\-testbed
-capability and you can run tests which require building or running as root. If
-your user is not allowed to do that, you need to run
-.B adt\-run
-as root instead.
-
-.SH OPTIONS
-.TP
-.BI -s " ID" " | --session-id=" ID
-Use a custom schroot session ID. This allows the user to easily
-identify hung sessions in
-.B schroot --list --all-sessions\fR.
-
-.TP
-.BR \-d " | " \-\-debug
-Enables debugging output.
-
-.SH INPUT, OUTPUT AND EXIT STATUS
-The behaviour of
-.B adt-virt-schroot
-is as described by the AutomatedTesting virtualisation regime
-specification.
-
-.SH SEE ALSO
-.BR adt\-run (1),
-.BR adt\-virt-null (1),
-.BR schroot (1),
-.BR mk\-sbuild (1).
-
-.SH AUTHORS AND COPYRIGHT
-This manpage is part of autopkgtest, a tool for testing Debian binary
-packages. autopkgtest is Copyright (C) 2006-2013 Canonical Ltd and others.
-
-See \fB/usr/share/doc/autopkgtest/CREDITS\fR for the list of
-contributors and full copying conditions.
diff --git a/reprotest/virt/autopkgtest-ssh.1 b/reprotest/virt/autopkgtest-ssh.1
deleted file mode 100644
index b4b16dd..0000000
--- a/reprotest/virt/autopkgtest-ssh.1
+++ /dev/null
@@ -1,278 +0,0 @@
-.TH adt\-virt-ssh 1 2014 "Linux Programmer's Manual"
-.SH NAME
-adt\-virt\-ssh \- autopkgtest virtualisation server using SSH
-
-.SH SYNOPSIS
-.B adt\-virt\-ssh
-.RI [ options ]
-.I [\fI-- setup script options\fR ...]
-
-
-.SH DESCRIPTION
-.B adt-virt-ssh
-provides an autopkgtest virtualisation server using SSH.
-
-Normally
-.B adt-virt-ssh
-will be invoked by
-.BR adt-run .
-
-.B adt-virt-ssh
-
-can use an already existing ssh target, or call a setup script to create/set up
-a test bed and the ssh server.
-
-.B WARNING!
-adt-virt-ssh will modify the target system by installing packages and running
-arbitrary test code, so
-.B you are responsible for resetting the testbed youself
-especially without a setup script. So use this with care.
-
-.SH REQUIREMENTS
-.B adt-virt-ssh
-doesn't assume anything regarding the target host other than that the given ssh
-connection (and networking) stay available all the time. You can provide
-credententials on the command line for already working SSH hosts or use a
-setup script to prepare the host for the connection (see
-.B SETUP SCRIPT
-below for more information), for example to create a
-forwarding rule to access an adb host over ssh or fire-up a cloud instance.
-
-.SH OPTIONS
-
-.TP
-.BR -h | --help
-Show the help message and exit
-
-.TP
-.BR -d | --debug
-Enable debugging output
-
-.TP
-.BI -H " hostname" " | --hostname=" hostname
-Connects and logs into the specified hostname or IP address
-
-.TP
-.BI -l " user" " | --login=" user
-Specifies the user to log in as on the remote machine.
-
-.TP
-.BI -i " identity" " | --identity=" identity
-Selects a file from which the identity (private key) for public key
-authentication is read. Should usually be
-.BR ~/.ssh/id_rsa ,
-but you might consider using a different key for tests.
-
-.TP
-.BI -P " password" " | --password=" password
-Specifies the sudo password on the remote host.
-
-It can be the password in clear text or a file containing the password. This
-password will be used to setup $SUDO_ASKPASS in the case sudo requires a
-password. The runner will check if the user has sudo access with and without a
-password. If the check fails, the capability "root-on-testbed" will not be
-available. If sudo works, then tests that run as user will have
-$SUDO_ASKPASS in their environment so that they can run
-.B sudo -A
-if needed.
-
-.TP
-.BI -p " port" " | --port=" port
-ssh port to use to connect to the host
-
-.TP
-.BI -o " options" " | --options=" options
-Passed verbatim to ssh; see man ssh_config
-
-.TP
-.BR -r | --reboot
-Indicate that
-.B reboot
-can be used in the testbed. This is useful when running rebooting tests without
-a setup script (which can already declare capabilities).
-
-.TP
-.BI -s " setup_script" " | --setup-script=" setup_script
-Setup script to prepare testbed and ssh connection (See
-.B SETUP SCRIPT
-below for more information). File names
-will be searched in both the current directory and in
-.B /usr/share/autopkgtest/ssh-setup/
-so you do not need to give the full path for setup scripts shipped with
-autopkgtest.
-
-.TP
-.BI "--timeout-ssh=" secs
-Timeout for waiting for ssh connection, in seconds. Default is 300.
-
-.TP
-.BI -- " [setup script arguments] "
-All the remaining arguments following \fB--\fR will be passed verbatim to the setup
-script to configure the host.
-
-
-.SH CONFIGURATION FILES
-If you use lots of options or hosts, you can put parts of, or the whole
-command line into a text file, with one line per option. E. g. you can create a
-file
-.I testhost.cfg
-with contents like
-
-.RS
-.EX
--Htest.example.com
--ltestuser
--Ps3kr1t
-.EE
-.RE
-
-and then run
-
-.RS
-.EX
-adt-run [...] --- adt-virt-ssh @testhost.cfg
-.EE
-.RE
-
-The contents of the configuration file will be expanded in-place as if you
-would have given its contents on the command line. Please ensure that you
-.B don't place spaces
-between short options and their values, they would become a part of the
-argument value.
-
-.SH INPUT, OUTPUT AND EXIT STATUS
-The behaviour of
-.B adt-virt-ssh
-is as described by the AutomatedTesting virtualisation regime
-specification.
-
-.SH NOTES
-
-\fBadt-run\fR does not run \fBapt-get update\fR at the start of a package
-build, which can cause a build failure if you are using a development
-series template. You will need to run \fBapt-get update\fR in the template
-yourself (e. g. using \fB\-\-setup\-commands\fR).
-
-.SH SETUP SCRIPT
-
-.B adt-virt-ssh
-accepts a setup script in argument to prepare the testbed and the ssh
-connection. A setup script is an executable that gets called with a command as
-first argument, and additional options for that command.
-
-.SS command: open
-When called with "open", the script has to create a testbed (if necessary),
-configure ssh, copy ssh key into it, configure sudo, etc.
-
-It then returns the following information on standard output with the form
-\fBkey=value\fR, one line per pair. These mostly mirror the command line
-options when not using a script.
-
-Required fields:
-
-.IP * 4
-login: User name
-
-.IP * 4
-hostname: hostname or IP address
-
-.PP
-Optional fields:
-
-.IP * 4
-identity: Path to the private key
-
-.IP * 4
-password: sudo password for the user name to acquire root privileges. If not
-given, and passwordless sudo does not work, the testbed will not have root
-privileges.
-
-.IP * 4
-port: SSH port on hostname, if different than 22
-
-.IP * 4
-capabilities: extra testbed capabilities such as "isolation-machine" or
-"revert", see README.virtualisation-server.rst
-
-If the testbed can be rebooted with keeping state, the script should advertise
-"reboot".
-
-.IP * 4
-options: passed verbatim to ssh, see man ssh_config
-
-.IP * 4
-extraopts: passed verbatim to other commands; this allows extra state (such as
-temporary directory names, VM identifiers, etc.) to be passed to cleanup
-
-.SS command: cleanup
-Called when closing the testbed; should revert/remove things installed in
-open as much as possible if the testbed is not ephemeral. This gets called with
-all the options that open got called with, plus
-.BR extraopts .
-
-.SS command: revert
-If there is a way to reset the testbed to its pristine state (such as using VM
-snapshots or rebuilding ephemeral testbeds), the script should put "revert"
-(and if appropriate, "revert-full-system") into the capabilities and implement
-this command. This can optionally output some or all of the ssh config keys
-from open() to update the configuration, in case the hostname/IP changes.
-
-.SS command: wait-reboot
-This can be implemented if capabilities advertise "reboot" and you need to do
-something more elaborate than just waiting for the ssh port to go down and come
-back up after calling "reboot". This needs to wait for testbed to shut down,
-boot, and re-prepare the testbed for ssh login.
-
-.SS command: debug-failure
-
-This is called when the setup script fails with nonzero or on timeouts waiting
-for ssh or reboot. If available, this should output some debugging information,
-such as the boot log from the serial console. Implementing this is
-optional.
-
-.SS Included scripts
-
-.RE
-autopkgtest provides setup scripts for common types of testbeds in
-.BR /usr/share/autopkgtest/ssh-setup/ .
-Please see the comments in these scripts for how to use them. Also, please
-consider using
-.B /usr/share/autopkgtest/ssh-setup/SKELETON
-as a basis for writing your own.
-
-.SH EXAMPLES
-
-Run the tests of the libpng source package on an existing "mytesthost":
-
-.RS
-.EX
-adt-run libpng --- ssh -H mytesthost -l joe -P /tmp/joe_password
-.EE
-.RE
-
-Run the tests of a click package on an Ubuntu phone with an ssh connection over
-ADB, using the setup script, with specifying an option to the setup script to
-pick a particular serial ID:
-
-.RS
-.EX
-adt-run ./ubuntu-calculator-app ./com.ubuntu.calculator_1.3.283_all.click \\
- --- ssh -s /usr/share/autopkgtest/ssh-setup/adb -- -s 0123456789abcdef
-.EE
-.RE
-
-.SH SEE ALSO
-.BR adt\-run (1),
-.BR /usr/share/doc/autopkgtest/ ,
-.BR /usr/share/autopkgtest/ssh-setup/SKELETON .
-
-.SH AUTHORS AND COPYRIGHT
-.B adt-virt-ssh
-was written by Martin Pitt <martin.pitt at ubuntu.com> and Jean-Baptiste
-Lallement <jean.baptiste.lallement at ubuntu.com>.
-
-This manpage is part of autopkgtest, a tool for testing Debian binary
-packages. autopkgtest is Copyright (C) 2006-2014 Canonical Ltd and others.
-
-See \fB/usr/share/doc/autopkgtest/CREDITS\fR for the list of
-contributors and full copying conditions.
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/reprotest.git
More information about the Reproducible-commits
mailing list