@@ -1,173 +1,3 @@

-# Getting Started With XenServer and Devstack

-

-The purpose of the code in this directory it to help developers bootstrap a

-XenServer 6.2 (older versions may also work) + OpenStack development

-environment. This file gives some pointers on how to get started.

-

-Xenserver is a Type 1 hypervisor, so it is best installed on bare metal.  The

-OpenStack services are configured to run within a virtual machine (called OS

-domU) on the XenServer host. The VM uses the XAPI toolstack to communicate with

-the host over a network connection (see `MGT_BRIDGE_OR_NET_NAME`).

-

-The provided localrc helps to build a basic environment.

-

-## Introduction

-

-### Requirements

-

- - An internet-enabled network with a DHCP server on it

- - XenServer box plugged in to the same network

-This network will be used as the OpenStack management network. The VM Network

-and the Public Network will not be connected to any physical interfaces, only

-new virtual networks will be created by the `install_os_domU.sh` script.

-

-### Steps to follow

-

- - Install XenServer

- - Download Devstack to XenServer

- - Customise `localrc`

- - Start `install_os_domU.sh` script

-

-### Brief explanation

-

-The `install_os_domU.sh` script will:

- - Setup XenAPI plugins

- - Create the named networks, if they don't exist

- - Preseed-Netinstall an Ubuntu Virtual Machine (NOTE: you can save and reuse

-   it, see [Reuse the Ubuntu VM](#reuse-the-ubuntu-vm)), with 1 network

-   interface:

-   - `eth0` - Connected to `UBUNTU_INST_BRIDGE_OR_NET_NAME`, defaults to

-     `MGT_BRIDGE_OR_NET_NAME`

- - After the Ubuntu install process finished, the network configuration is

- modified to:

-   - `eth0` - Management interface, connected to `MGT_BRIDGE_OR_NET_NAME`. Xapi

-     must be accessible through this network.

-   - `eth1` - VM interface, connected to `VM_BRIDGE_OR_NET_NAME`

-   - `eth2` - Public interface, connected to `PUB_BRIDGE_OR_NET_NAME`

- - Start devstack inside the created OpenStack VM

-

-## Step 1: Install Xenserver

-Install XenServer on a clean box. You can download the latest XenServer for

-free from: http://www.xenserver.org/

-

-The XenServer IP configuration depends on your local network setup. If you are

-using dhcp, make a reservation for XenServer, so its IP address won't change

-over time. Make a note of the XenServer's IP address, as it has to be specified

-in `localrc`. The other option is to manually specify the IP setup for the

-XenServer box. Please make sure, that a gateway and a nameserver is configured,

-as `install_os_domU.sh` will connect to github.com to get source-code snapshots.

-

-## Step 2: Download devstack

-On your XenServer host, run the following commands as root:

-

-    wget --no-check-certificate https://github.com/openstack-dev/devstack/zipball/master

-    unzip -o master -d ./devstack

-    cd devstack/*/

-

-## Step 3: Configure your localrc inside the devstack directory

-Devstack uses a localrc for user-specific configuration.  Note that

-the `XENAPI_PASSWORD` must be your dom0 root password.

-Of course, use real passwords if this machine is exposed.

-

-    cat > ./localrc <<EOF

-    # At the moment, we depend on github's snapshot function.

-    GIT_BASE="http://github.com"

-

-    # Passwords

-    # NOTE: these need to be specified, otherwise devstack will try

-    # to prompt for these passwords, blocking the install process.

-

-    DATABASE_PASSWORD=my_super_secret

-    ADMIN_PASSWORD=my_super_secret

-    SERVICE_PASSWORD=my_super_secret

-    RABBIT_PASSWORD=my_super_secret

-    SWIFT_HASH="66a3d6b56c1f479c8b4e70ab5c2000f5"

-    # This will be the password for the OpenStack VM (both stack and root users)

-    GUEST_PASSWORD=my_super_secret

-

-    # XenAPI parameters

-    # NOTE: The following must be set to your XenServer root password!

-

-    XENAPI_PASSWORD=my_xenserver_root_password

-

-    XENAPI_CONNECTION_URL="http://address_of_your_xenserver"

-    VNCSERVER_PROXYCLIENT_ADDRESS=address_of_your_xenserver

-

-    # Explicitly set virt driver

-    VIRT_DRIVER=xenserver

-

-    # Explicitly enable multi-host for nova-network HA

-    MULTI_HOST=1

-

-    # Give extra time for boot

-    ACTIVE_TIMEOUT=45

-

-    EOF

-

-## Step 4: Run `./install_os_domU.sh` from the `tools/xen` directory

-

-    cd tools/xen

-    ./install_os_domU.sh

-

-Once this script finishes executing, log into the VM (openstack domU) that it

-installed and tail the run.sh.log file. You will need to wait until it run.sh

-has finished executing.

-

-# Appendix

-

-This section contains useful information for running devstack in CI

-environments / using ubuntu network mirrors.

-

-## Use a specific Ubuntu mirror for installation

-

-To speed up the Ubuntu installation, you can use a specific mirror. To specify

-a mirror explicitly, include the following settings in your `localrc` file:

-

-    UBUNTU_INST_HTTP_HOSTNAME="archive.ubuntu.com"

-    UBUNTU_INST_HTTP_DIRECTORY="/ubuntu"

-

-These variables set the `mirror/http/hostname` and `mirror/http/directory`

-settings in the ubuntu preseed file. The minimal ubuntu VM will use the

-specified parameters.

-

-## Use an http proxy to speed up Ubuntu installation

-

-To further speed up the Ubuntu VM and package installation, an internal http

-proxy could be used. `squid-deb-proxy` has prooven to be stable. To use an http

-proxy, specify:

-

-    UBUNTU_INST_HTTP_PROXY="http://ubuntu-proxy.somedomain.com:8000"

-

-in your `localrc` file.

-

-## Reuse the Ubuntu VM

-

-Performing a minimal ubuntu installation could take a lot of time, depending on

-your mirror/network speed. If you run `install_os_domU.sh` script on a clean

-hypervisor, you can speed up the installation, by re-using the ubuntu vm from

-a previous installation.

-

-### Export the Ubuntu VM to an XVA

-

-Given you have an nfs export `TEMPLATE_NFS_DIR`:

-

-    TEMPLATE_FILENAME=devstack-jeos.xva

-    TEMPLATE_NAME=jeos_template_for_devstack

-    mountdir=$(mktemp -d)

-    mount -t nfs "$TEMPLATE_NFS_DIR" "$mountdir"

-    VM="$(xe template-list name-label="$TEMPLATE_NAME" --minimal)"

-    xe template-export template-uuid=$VM filename="$mountdir/$TEMPLATE_FILENAME"

-    umount "$mountdir"

-    rm -rf "$mountdir"

-

-### Import the Ubuntu VM

-

-Given you have an nfs export `TEMPLATE_NFS_DIR` where you exported the Ubuntu

-VM as `TEMPLATE_FILENAME`:

-

-    mountdir=$(mktemp -d)

-    mount -t nfs "$TEMPLATE_NFS_DIR" "$mountdir"

-    xe vm-import filename="$mountdir/$TEMPLATE_FILENAME"

-    umount "$mountdir"

-    rm -rf "$mountdir"

+Note: XenServer relative tools have been moved to `os-xenapi`_ and be maintained there.

+.. _os-xenapi: https://github.com/openstack/os-xenapi/

deleted file mode 100755

@@ -1,191 +0,0 @@

-#!/bin/bash

-

-# This script is run by install_os_domU.sh

-#

-# It modifies the ubuntu image created by install_os_domU.sh

-# and previously moodified by prepare_guest_template.sh

-#

-# This script is responsible for:

-# - pushing in the DevStack code

-# - creating run.sh, to run the code on boot

-# It does this by mounting the disk image of the VM.

-#

-# The resultant image is then templated and started

-# by install_os_domU.sh

-

-# Exit on errors

-set -o errexit

-# Echo commands

-set -o xtrace

-

-# This directory

-TOP_DIR=$(cd $(dirname "$0") && pwd)

-

-# Include onexit commands

-. $TOP_DIR/scripts/on_exit.sh

-

-# xapi functions

-. $TOP_DIR/functions

-

-# Source params - override xenrc params in your localrc to suite your taste

-source xenrc

-

-#

-# Parameters

-#

-GUEST_NAME="$1"

-

-function _print_interface_config {

-    local device_nr

-    local ip_address

-    local netmask

-

-    device_nr="$1"

-    ip_address="$2"

-    netmask="$3"

-

-    local device

-

-    device="eth${device_nr}"

-

-    echo "auto $device"

-    if [ $ip_address == "dhcp" ]; then

-        echo "iface $device inet dhcp"

-    else

-        echo "iface $device inet static"

-        echo "  address $ip_address"

-        echo "  netmask $netmask"

-    fi

-

-    # Turn off tx checksumming for better performance

-    echo "  post-up ethtool -K $device tx off"

-}

-

-function print_interfaces_config {

-    echo "auto lo"

-    echo "iface lo inet loopback"

-

-    _print_interface_config $PUB_DEV_NR $PUB_IP $PUB_NETMASK

-    _print_interface_config $VM_DEV_NR $VM_IP $VM_NETMASK

-    _print_interface_config $MGT_DEV_NR $MGT_IP $MGT_NETMASK

-}

-

-#

-# Mount the VDI

-#

-STAGING_DIR=$($TOP_DIR/scripts/manage-vdi open $GUEST_NAME 0 1 | grep -o "/tmp/tmp.[[:alnum:]]*")

-add_on_exit "$TOP_DIR/scripts/manage-vdi close $GUEST_NAME 0 1"

-

-# Make sure we have a stage

-if [ ! -d $STAGING_DIR/etc ]; then

-    echo "Stage is not properly set up!"

-    exit 1

-fi

-

-# Only support DHCP for now - don't support how different versions of Ubuntu handle resolv.conf

-if [ "$MGT_IP" != "dhcp" ] && [ "$PUB_IP" != "dhcp" ]; then

-    echo "Configuration without DHCP not supported"

-    exit 1

-fi

-

-# Copy over devstack

-rm -f /tmp/devstack.tar

-cd $TOP_DIR/../../

-tar --exclude='stage' --exclude='xen/xvas' --exclude='xen/nova' -cvf /tmp/devstack.tar .

-mkdir -p $STAGING_DIR/opt/stack/devstack

-tar xf /tmp/devstack.tar -C $STAGING_DIR/opt/stack/devstack

-cd $TOP_DIR

-

-# Create an systemd task for devstack

-cat >$STAGING_DIR/etc/systemd/system/devstack.service << EOF

-[Unit]

-Description=Install OpenStack by DevStack

-

-[Service]

-Type=oneshot

-RemainAfterExit=yes

-ExecStartPre=/bin/rm -f /opt/stack/runsh.succeeded

-ExecStart=/bin/su -c "/opt/stack/run.sh" stack

-StandardOutput=tty

-StandardError=tty

-

-[Install]

-WantedBy=multi-user.target

-

-EOF

-

-# enable this service

-ln -s $STAGING_DIR/etc/systemd/system/devstack.service $STAGING_DIR/etc/systemd/system/multi-user.target.wants/devstack.service

-

-# Configure the hostname

-echo $GUEST_NAME > $STAGING_DIR/etc/hostname

-

-# Hostname must resolve for rabbit

-HOSTS_FILE_IP=$PUB_IP

-if [ $MGT_IP != "dhcp" ]; then

-    HOSTS_FILE_IP=$MGT_IP

-fi

-cat <<EOF >$STAGING_DIR/etc/hosts

-$HOSTS_FILE_IP $GUEST_NAME

-127.0.0.1 localhost localhost.localdomain

-EOF

-

-# Configure the network

-print_interfaces_config > $STAGING_DIR/etc/network/interfaces

-

-# Gracefully cp only if source file/dir exists

-function cp_it {

-    if [ -e $1 ] || [ -d $1 ]; then

-        cp -pRL $1 $2

-    fi

-}

-

-# Copy over your ssh keys and env if desired

-COPYENV=${COPYENV:-1}

-if [ "$COPYENV" = "1" ]; then

-    cp_it ~/.ssh $STAGING_DIR/opt/stack/.ssh

-    cp_it ~/.ssh/id_rsa.pub $STAGING_DIR/opt/stack/.ssh/authorized_keys

-    cp_it ~/.gitconfig $STAGING_DIR/opt/stack/.gitconfig

-    cp_it ~/.vimrc $STAGING_DIR/opt/stack/.vimrc

-    cp_it ~/.bashrc $STAGING_DIR/opt/stack/.bashrc

-fi

-

-# Configure run.sh

-cat <<EOF >$STAGING_DIR/opt/stack/run.sh

-#!/bin/bash

-set -eux

-(

-  flock -n 9 || exit 1

-

-  sudo chown -R stack /opt/stack

-

-  [ -e /opt/stack/runsh.succeeded ] && rm /opt/stack/runsh.succeeded

-  echo \$\$ >> /opt/stack/run_sh.pid

-

-  cd /opt/stack/devstack

-  ./unstack.sh || true

-  ./stack.sh

-

-  # Got to the end - success

-  touch /opt/stack/runsh.succeeded

-

-  # Update /etc/issue

-  (

-      echo "OpenStack VM - Installed by DevStack"

-      IPADDR=$(ip -4 address show eth0 | sed -n 's/.*inet \([0-9\.]\+\).*/\1/p')

-      echo "  Management IP:   $IPADDR"

-      echo -n "  Devstack run:    "

-      if [ -e /opt/stack/runsh.succeeded ]; then

-          echo "SUCCEEDED"

-      else

-          echo "FAILED"

-      fi

-      echo ""

-  ) > /opt/stack/issue

-  sudo cp /opt/stack/issue /etc/issue

-

-  rm /opt/stack/run_sh.pid

-) 9> /opt/stack/.runsh_lock

-EOF

-

-chmod 755 $STAGING_DIR/opt/stack/run.sh

deleted file mode 100644

@@ -1,14 +0,0 @@

-#!/bin/bash

-set -eux

-

-# Need to set barrier=0 to avoid a Xen bug

-# https://bugs.launchpad.net/ubuntu/+source/linux/+bug/824089

-sed -i -e 's/errors=/barrier=0,errors=/' /etc/fstab

-

-# Allow root to login with a password

-sed -i -e 's/.*PermitRootLogin.*/PermitRootLogin yes/g' /etc/ssh/sshd_config

-

-# Install the XenServer tools so IP addresses are reported

-wget --no-proxy @XS_TOOLS_URL@ -O /root/tools.deb

-dpkg -i /root/tools.deb

-rm /root/tools.deb

deleted file mode 100644

@@ -1,471 +0,0 @@

-### Contents of the preconfiguration file (for squeeze)

-### Localization

-# Preseeding only locale sets language, country and locale.

-d-i debian-installer/locale string en_US

-

-# The values can also be preseeded individually for greater flexibility.

-#d-i debian-installer/language string en

-#d-i debian-installer/country string NL

-#d-i debian-installer/locale string en_GB.UTF-8

-# Optionally specify additional locales to be generated.

-#d-i localechooser/supported-locales en_US.UTF-8, nl_NL.UTF-8

-

-# Keyboard selection.

-# Disable automatic (interactive) keymap detection.

-d-i console-setup/ask_detect boolean false

-#d-i keyboard-configuration/modelcode string pc105

-d-i keyboard-configuration/layoutcode string us

-# To select a variant of the selected layout (if you leave this out, the

-# basic form of the layout will be used):

-#d-i keyboard-configuration/variantcode string dvorak

-

-### Network configuration

-# Disable network configuration entirely. This is useful for cdrom

-# installations on non-networked devices where the network questions,

-# warning and long timeouts are a nuisance.

-#d-i netcfg/enable boolean false

-

-# netcfg will choose an interface that has link if possible. This makes it

-# skip displaying a list if there is more than one interface.

-d-i netcfg/choose_interface select auto

-

-# To pick a particular interface instead:

-#d-i netcfg/choose_interface select eth1

-

-# If you have a slow dhcp server and the installer times out waiting for

-# it, this might be useful.

-d-i netcfg/dhcp_timeout string 120

-

-# If you prefer to configure the network manually, uncomment this line and

-# the static network configuration below.

-#d-i netcfg/disable_autoconfig boolean true

-

-# If you want the preconfiguration file to work on systems both with and

-# without a dhcp server, uncomment these lines and the static network

-# configuration below.

-#d-i netcfg/dhcp_failed note

-#d-i netcfg/dhcp_options select Configure network manually

-

-# Static network configuration.

-#d-i netcfg/get_nameservers string 192.168.1.1

-#d-i netcfg/get_ipaddress string 192.168.1.42

-#d-i netcfg/get_netmask string 255.255.255.0

-#d-i netcfg/get_gateway string 192.168.1.1

-#d-i netcfg/confirm_static boolean true

-

-# Any hostname and domain names assigned from dhcp take precedence over

-# values set here. However, setting the values still prevents the questions

-# from being shown, even if values come from dhcp.

-d-i netcfg/get_hostname string stack

-d-i netcfg/get_domain string stackpass

-

-# Disable that annoying WEP key dialog.

-d-i netcfg/wireless_wep string

-# The wacky dhcp hostname that some ISPs use as a password of sorts.

-#d-i netcfg/dhcp_hostname string radish

-

-# If non-free firmware is needed for the network or other hardware, you can

-# configure the installer to always try to load it, without prompting. Or

-# change to false to disable asking.

-#d-i hw-detect/load_firmware boolean true

-

-### Network console

-# Use the following settings if you wish to make use of the network-console

-# component for remote installation over SSH. This only makes sense if you

-# intend to perform the remainder of the installation manually.

-#d-i anna/choose_modules string network-console

-#d-i network-console/password password r00tme

-#d-i network-console/password-again password r00tme

-

-### Mirror settings

-# If you select ftp, the mirror/country string does not need to be set.

-#d-i mirror/protocol string ftp

-d-i mirror/country string manual

-d-i mirror/http/hostname string archive.ubuntu.com

-d-i mirror/http/directory string /ubuntu

-d-i mirror/http/proxy string

-

-# Alternatively: by default, the installer uses CC.archive.ubuntu.com where

-# CC is the ISO-3166-2 code for the selected country. You can preseed this

-# so that it does so without asking.

-#d-i mirror/http/mirror select CC.archive.ubuntu.com

-

-# Suite to install.

-#d-i mirror/suite string squeeze

-# Suite to use for loading installer components (optional).

-#d-i mirror/udeb/suite string squeeze

-# Components to use for loading installer components (optional).

-#d-i mirror/udeb/components multiselect main, restricted

-

-### Clock and time zone setup

-# Controls whether or not the hardware clock is set to UTC.

-d-i clock-setup/utc boolean true

-

-# You may set this to any valid setting for $TZ; see the contents of

-# /usr/share/zoneinfo/ for valid values.

-d-i time/zone string US/Pacific

-

-# Controls whether to use NTP to set the clock during the install

-d-i clock-setup/ntp boolean true

-# NTP server to use. The default is almost always fine here.

-d-i clock-setup/ntp-server string 0.us.pool.ntp.org

-

-### Partitioning

-## Partitioning example

-# If the system has free space you can choose to only partition that space.

-# This is only honoured if partman-auto/method (below) is not set.

-# Alternatives: custom, some_device, some_device_crypto, some_device_lvm.

-#d-i partman-auto/init_automatically_partition select biggest_free

-

-# Alternatively, you may specify a disk to partition. If the system has only

-# one disk the installer will default to using that, but otherwise the device

-# name must be given in traditional, non-devfs format (so e.g. /dev/hda or

-# /dev/sda, and not e.g. /dev/discs/disc0/disc).

-# For example, to use the first SCSI/SATA hard disk:

-#d-i partman-auto/disk string /dev/sda

-# In addition, you'll need to specify the method to use.

-# The presently available methods are:

-# - regular: use the usual partition types for your architecture

-# - lvm:     use LVM to partition the disk

-# - crypto:  use LVM within an encrypted partition

-d-i partman-auto/method string regular

-

-# If one of the disks that are going to be automatically partitioned

-# contains an old LVM configuration, the user will normally receive a

-# warning. This can be preseeded away...

-d-i partman-lvm/device_remove_lvm boolean true

-# The same applies to pre-existing software RAID array:

-d-i partman-md/device_remove_md boolean true

-# And the same goes for the confirmation to write the lvm partitions.

-d-i partman-lvm/confirm boolean true

-

-# For LVM partitioning, you can select how much of the volume group to use

-# for logical volumes.

-#d-i partman-auto-lvm/guided_size string max

-#d-i partman-auto-lvm/guided_size string 10GB

-#d-i partman-auto-lvm/guided_size string 50%

-

-# You can choose one of the three predefined partitioning recipes:

-# - atomic: all files in one partition

-# - home:   separate /home partition

-# - multi:  separate /home, /usr, /var, and /tmp partitions

-d-i partman-auto/choose_recipe select atomic

-

-# Or provide a recipe of your own...

-# If you have a way to get a recipe file into the d-i environment, you can

-# just point at it.

-#d-i partman-auto/expert_recipe_file string /hd-media/recipe

-

-# If not, you can put an entire recipe into the preconfiguration file in one

-# (logical) line. This example creates a small /boot partition, suitable

-# swap, and uses the rest of the space for the root partition:

-#d-i partman-auto/expert_recipe string                         \

-#      boot-root ::                                            \

-#              40 50 100 ext3                                  \

-#                      $primary{ } $bootable{ }                \

-#                      method{ format } format{ }              \

-#                      use_filesystem{ } filesystem{ ext3 }    \

-#                      mountpoint{ /boot }                     \

-#              .                                               \

-#              500 10000 1000000000 ext3                       \

-#                      method{ format } format{ }              \

-#                      use_filesystem{ } filesystem{ ext3 }    \

-#                      mountpoint{ / }                         \

-#              .                                               \

-#              64 512 300% linux-swap                          \

-#                      method{ swap } format{ }                \

-#              .

-

-# If you just want to change the default filesystem from ext3 to something

-# else, you can do that without providing a full recipe.

-d-i partman/default_filesystem string ext3

-

-# The full recipe format is documented in the file partman-auto-recipe.txt

-# included in the 'debian-installer' package or available from D-I source

-# repository. This also documents how to specify settings such as file

-# system labels, volume group names and which physical devices to include

-# in a volume group.

-

-# This makes partman automatically partition without confirmation, provided

-# that you told it what to do using one of the methods above.

-d-i partman-partitioning/confirm_write_new_label boolean true

-d-i partman/choose_partition select finish

-d-i partman/confirm boolean true

-d-i partman/confirm_nooverwrite boolean true

-

-## Partitioning using RAID

-# The method should be set to "raid".

-#d-i partman-auto/method string raid

-# Specify the disks to be partitioned. They will all get the same layout,

-# so this will only work if the disks are the same size.

-#d-i partman-auto/disk string /dev/sda /dev/sdb

-

-# Next you need to specify the physical partitions that will be used. 

-#d-i partman-auto/expert_recipe string \

-#      multiraid ::                                         \

-#              1000 5000 4000 raid                          \

-#                      $primary{ } method{ raid }           \

-#              .                                            \

-#              64 512 300% raid                             \

-#                      method{ raid }                       \

-#              .                                            \

-#              500 10000 1000000000 raid                    \

-#                      method{ raid }                       \

-#              .

-

-# Last you need to specify how the previously defined partitions will be

-# used in the RAID setup. Remember to use the correct partition numbers

-# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported;

-# devices are separated using "#".

-# Parameters are:

-# <raidtype> <devcount> <sparecount> <fstype> <mountpoint> \

-#          <devices> <sparedevices>

-

-#d-i partman-auto-raid/recipe string \

-#    1 2 0 ext3 /                    \

-#          /dev/sda1#/dev/sdb1       \

-#    .                               \

-#    1 2 0 swap -                    \

-#          /dev/sda5#/dev/sdb5       \

-#    .                               \

-#    0 2 0 ext3 /home                \

-#          /dev/sda6#/dev/sdb6       \

-#    .

-

-# For additional information see the file partman-auto-raid-recipe.txt

-# included in the 'debian-installer' package or available from D-I source

-# repository.

-

-# This makes partman automatically partition without confirmation.

-d-i partman-md/confirm boolean true

-d-i partman-partitioning/confirm_write_new_label boolean true

-d-i partman/choose_partition select finish

-d-i partman/confirm boolean true

-d-i partman/confirm_nooverwrite boolean true

-

-## Controlling how partitions are mounted

-# The default is to mount by UUID, but you can also choose "traditional" to

-# use traditional device names, or "label" to try filesystem labels before

-# falling back to UUIDs.

-#d-i partman/mount_style select uuid

-

-### Base system installation

-# Configure APT to not install recommended packages by default. Use of this

-# option can result in an incomplete system and should only be used by very

-# experienced users.

-#d-i base-installer/install-recommends boolean false

-

-# The kernel image (meta) package to be installed; "none" can be used if no

-# kernel is to be installed.

-d-i base-installer/kernel/image string linux-virtual

-

-### Account setup

-# Skip creation of a root account (normal user account will be able to

-# use sudo). The default is false; preseed this to true if you want to set

-# a root password.

-d-i passwd/root-login boolean true

-# Alternatively, to skip creation of a normal user account.

-d-i passwd/make-user boolean false

-

-# Root password, either in clear text

-d-i passwd/root-password password stackpass

-d-i passwd/root-password-again password stackpass

-# or encrypted using an MD5 hash.

-#d-i passwd/root-password-crypted password [MD5 hash]

-

-# To create a normal user account.

-#d-i passwd/user-fullname string Ubuntu User

-#d-i passwd/username string ubuntu

-# Normal user's password, either in clear text

-#d-i passwd/user-password password insecure

-#d-i passwd/user-password-again password insecure

-# or encrypted using an MD5 hash.

-#d-i passwd/user-password-crypted password [MD5 hash]

-# Create the first user with the specified UID instead of the default.

-#d-i passwd/user-uid string 1010

-# The installer will warn about weak passwords. If you are sure you know

-# what you're doing and want to override it, uncomment this.

-d-i user-setup/allow-password-weak boolean true

-

-# The user account will be added to some standard initial groups. To

-# override that, use this.

-#d-i passwd/user-default-groups string audio cdrom video

-

-# Set to true if you want to encrypt the first user's home directory.

-d-i user-setup/encrypt-home boolean false

-

-### Apt setup

-# You can choose to install restricted and universe software, or to install

-# software from the backports repository.

-d-i apt-setup/restricted boolean true

-d-i apt-setup/universe boolean true

-d-i apt-setup/backports boolean true

-# Uncomment this if you don't want to use a network mirror.

-#d-i apt-setup/use_mirror boolean false

-# Select which update services to use; define the mirrors to be used.

-# Values shown below are the normal defaults.

-#d-i apt-setup/services-select multiselect security

-#d-i apt-setup/security_host string security.ubuntu.com

-#d-i apt-setup/security_path string /ubuntu

-

-# Additional repositories, local[0-9] available

-#d-i apt-setup/local0/repository string \

-#       http://local.server/ubuntu squeeze main

-#d-i apt-setup/local0/comment string local server

-# Enable deb-src lines

-#d-i apt-setup/local0/source boolean true

-# URL to the public key of the local repository; you must provide a key or

-# apt will complain about the unauthenticated repository and so the

-# sources.list line will be left commented out

-#d-i apt-setup/local0/key string http://local.server/key

-

-# By default the installer requires that repositories be authenticated

-# using a known gpg key. This setting can be used to disable that

-# authentication. Warning: Insecure, not recommended.

-#d-i debian-installer/allow_unauthenticated boolean true

-

-### Package selection

-#tasksel tasksel/first multiselect ubuntu-desktop

-#tasksel tasksel/first multiselect lamp-server, print-server

-#tasksel tasksel/first multiselect kubuntu-desktop

-tasksel tasksel/first multiselect openssh-server

-

-# Individual additional packages to install

-d-i pkgsel/include string cracklib-runtime curl wget ssh openssh-server tcpdump ethtool git sudo python-netaddr coreutils

-

-# Whether to upgrade packages after debootstrap.

-# Allowed values: none, safe-upgrade, full-upgrade

-d-i pkgsel/upgrade select safe-upgrade

-

-# Language pack selection

-#d-i pkgsel/language-packs multiselect de, en, zh

-

-# Policy for applying updates. May be "none" (no automatic updates),

-# "unattended-upgrades" (install security updates automatically), or

-# "landscape" (manage system with Landscape).

-d-i pkgsel/update-policy select unattended-upgrades

-

-# Some versions of the installer can report back on what software you have

-# installed, and what software you use. The default is not to report back,

-# but sending reports helps the project determine what software is most

-# popular and include it on CDs.

-#popularity-contest popularity-contest/participate boolean false

-

-# By default, the system's locate database will be updated after the

-# installer has finished installing most packages. This may take a while, so

-# if you don't want it, you can set this to "false" to turn it off.

-d-i pkgsel/updatedb boolean false

-

-### Boot loader installation

-# Grub is the default boot loader (for x86). If you want lilo installed

-# instead, uncomment this:

-#d-i grub-installer/skip boolean true

-# To also skip installing lilo, and install no bootloader, uncomment this

-# too:

-#d-i lilo-installer/skip boolean true

-

-# With a few exceptions for unusual partitioning setups, GRUB 2 is now the

-# default. If you need GRUB Legacy for some particular reason, then

-# uncomment this:

-d-i grub-installer/grub2_instead_of_grub_legacy boolean false

-

-# This is fairly safe to set, it makes grub install automatically to the MBR

-# if no other operating system is detected on the machine.

-d-i grub-installer/only_debian boolean true

-

-# This one makes grub-installer install to the MBR if it also finds some other

-# OS, which is less safe as it might not be able to boot that other OS.

-d-i grub-installer/with_other_os boolean true

-

-# Alternatively, if you want to install to a location other than the mbr,

-# uncomment and edit these lines:

-#d-i grub-installer/only_debian boolean false

-#d-i grub-installer/with_other_os boolean false

-#d-i grub-installer/bootdev  string (hd0,0)

-# To install grub to multiple disks:

-#d-i grub-installer/bootdev  string (hd0,0) (hd1,0) (hd2,0)

-

-# Optional password for grub, either in clear text

-#d-i grub-installer/password password r00tme

-#d-i grub-installer/password-again password r00tme

-# or encrypted using an MD5 hash, see grub-md5-crypt(8).

-#d-i grub-installer/password-crypted password [MD5 hash]

-

-# Use the following option to add additional boot parameters for the

-# installed system (if supported by the bootloader installer).

-# Note: options passed to the installer will be added automatically.

-#d-i debian-installer/add-kernel-opts string nousb

-

-### Finishing up the installation

-# During installations from serial console, the regular virtual consoles

-# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next

-# line to prevent this.

-d-i finish-install/keep-consoles boolean true

-

-# Avoid that last message about the install being complete.

-d-i finish-install/reboot_in_progress note

-

-# This will prevent the installer from ejecting the CD during the reboot,

-# which is useful in some situations.

-#d-i cdrom-detect/eject boolean false

-

-# This is how to make the installer shutdown when finished, but not

-# reboot into the installed system.

-#d-i debian-installer/exit/halt boolean true

-# This will power off the machine instead of just halting it.

-#d-i debian-installer/exit/poweroff boolean true

-

-### X configuration

-# X can detect the right driver for some cards, but if you're preseeding,

-# you override whatever it chooses. Still, vesa will work most places.

-#xserver-xorg xserver-xorg/config/device/driver select vesa

-

-# A caveat with mouse autodetection is that if it fails, X will retry it

-# over and over. So if it's preseeded to be done, there is a possibility of

-# an infinite loop if the mouse is not autodetected.

-#xserver-xorg xserver-xorg/autodetect_mouse boolean true

-

-# Monitor autodetection is recommended.

-xserver-xorg xserver-xorg/autodetect_monitor boolean true

-# Uncomment if you have an LCD display.

-#xserver-xorg xserver-xorg/config/monitor/lcd boolean true

-# X has three configuration paths for the monitor. Here's how to preseed

-# the "medium" path, which is always available. The "simple" path may not

-# be available, and the "advanced" path asks too many questions.

-xserver-xorg xserver-xorg/config/monitor/selection-method \

-       select medium

-xserver-xorg xserver-xorg/config/monitor/mode-list \

-       select 1024x768 @ 60 Hz

-

-### Preseeding other packages

-# Depending on what software you choose to install, or if things go wrong

-# during the installation process, it's possible that other questions may

-# be asked. You can preseed those too, of course. To get a list of every

-# possible question that could be asked during an install, do an

-# installation, and then run these commands:

-#   debconf-get-selections --installer > file

-#   debconf-get-selections >> file

-

-

-#### Advanced options

-### Running custom commands during the installation

-# d-i preseeding is inherently not secure. Nothing in the installer checks

-# for attempts at buffer overflows or other exploits of the values of a

-# preconfiguration file like this one. Only use preconfiguration files from

-# trusted locations! To drive that home, and because it's generally useful,

-# here's a way to run any shell command you'd like inside the installer,

-# automatically.

-

-# This first command is run as early as possible, just after

-# preseeding is read.

-#d-i preseed/early_command string anna-install some-udeb

-# This command is run immediately before the partitioner starts. It may be

-# useful to apply dynamic partitioner preseeding that depends on the state

-# of the disks (which may not be visible when preseed/early_command runs).

-#d-i partman/early_command \

-#       string debconf-set partman-auto/disk "$(list-devices disk | head -n1)"

-# This command is run just before the install finishes, but when there is

-# still a usable /target directory. You can chroot to /target and use it

-# directly, or use the apt-install and in-target commands to easily install

-# packages and run commands in the target system.

-d-i preseed/late_command string

deleted file mode 100644

@@ -1,341 +0,0 @@

-#!/bin/bash

-

-function die_with_error {

-    local err_msg

-

-    err_msg="$1"

-

-    echo "$err_msg" >&2

-    exit 1

-}

-

-function xapi_plugin_location {