Changes between Version 6 and Version 7 of ContainerFilesDoc

Timestamp:

Feb 15, 2015 10:50:01 AM (9 years ago)

Author:

Geoff Lawler

Comment:

--

ContainerFilesDoc

@@ -222 +222 @@
 **/var/containers/setup/hv/hv** - This script is invoked by the start_cmd script on the pnode after the node has booted and before the containers are up. It untars the ${EXP}/containers dir into {{{/var/containers/config}}} and writes the /etc/{init,init.d} containers control/start/stop script. It then reads the {{{children}}} file. It then calls the per-child setup script ({{/setup/hv/*}}} (although I don't see these). Finally it invokes the /etc/init/containers platform script. (On Ubuntu it uses "start containers".) This maps to /var/containers/launch/hv/hv, described below.
 
-**/var/containers/launch/hv/hv** - The script invoked by {{./setup/hv/hv}} on the pnode. It sets up tap pipes and bridges for connecting VDE switches between pnodes. It creates the vde switches. It then calls {{{/var/containers/launch/%s/hv}}} %s=child name for all existing files. There is one of these files for each type of container supported, embedded_pnode, qemu, openvz, and process. The qemu version is explained below.
+**/var/containers/launch/hv/hv** - The script invoked by {{{./setup/hv/hv}}} on the pnode. It sets up tap pipes and bridges for connecting VDE switches between pnodes. It creates the vde switches. It then calls {{{/var/containers/launch/%s/hv}}} %s=child name for all existing files. There is one of these files for each type of container supported, embedded_pnode, qemu, openvz, and process. The qemu version is explained below.
 
 **/var/containers/launch/qemu/hv** - this file is invoked at the end of the launch sequence on a pnode to spawn the qemu containers that will run on that pnode. (The VDE networking is setup before this script is invoked.) Log is written to {{{/var/containers/log/hv_qemu.log}}}. Builds something called "vncboot" (don't know why this is needed). The script then reads the per-experiment YAML config files, mounts the qemu image on the phost (via qemu-nbd), then writes the config information to the qemu disk. This assumes an Ubuntu image, which is bad. There doesn't seem to be any OS/platform checking here at all. (This file writes rc.local to the qemu image.) Then it starts up some IRC-based control channel with a server running on boss. ??? There is no ircd running on boss now, so is this some sort of legacy command/control channel for containers?