This script creates a new virtual machine using `virt-install`. It then starts
an HTTP server to serve a kickstart configuration file to the new VM, which is
used to automatically install CentOS.
Using the `socket.create_connection` function to attempt to connect to the
network service allows both IPv4 and IPv6 support, as the function tries both
families internally and returns the first socket to succeed.
--HG--
extra : amend_source : 6a0e3b9c90f6caff94290125072d50fe97aa312e
The `-a` switch to `rsync` causes it to copy extra information that may be
incompatible with the destination if it uses a non-native filesystem (such as
FAT or NTFS). Since most of this additional information is not necessary in a
backup and can cause copy errors, it should be excluded by default. Instead,
the `-r` flag is used to enable recursive copies, and the `-t` flag to
preserve file timestamps.
This script waits for a network service on a remote host (default LDAP on
Arcturus) to become available and then starts one or more virtual machines. It
is used on Atria to start Bellatrix and Rigel, since they need Active
Directory to be up in order to boot correctly.
This PowerShell script starts KVM virtual machines on a remote host by
connecting to the libvirt daemon over SSH (using plink from the PuTTY suite).
The original intent for this script was to run as a scheduled task, triggered
by the event indicating that Active Directory had started, however, for
unknown reasons, this did not end up working. As such, this script remains
unused, but I am committing it anyway for reference.
If not specified, a file named `backups.ini` in the directory specified by the
`XDG_CONFIG_DIR` environment variable (or `~/.config` if it is not set).
To ensure that output is generated, even when no errors occur, and thus cron
sends an email message, we'll print some informational messages before and
after running the backup. These can be switched off with the `-q`/`--quiet`
argument.
By moving the domain definition task earlier in the provisioning process, it
allows the administrator the option of opening the virtual console in
preparation for the virtual machine's first boot. This may be necessary if,
for example, the boot needs to be closely monitored, as there may not be
enough time to launch the console before the machine starts.
Recently, using LABEL= instead of the actual block device path in /etc/fstab
has caused errors in init.d/localmount because it tries to mount stuff that's
already mounted. Don't really know or care why.
Dustin
Dustin C. Hatch