Changes between Version 24 and Version 25 of ChefNotes

Timestamp:

Feb 18, 2015 10:36:17 AM (10 years ago)

Author:

Geoff Lawler

Comment:

--

ChefNotes

@@ -21 +21 @@
 3. ---
    a. data map to file/script
-      * user accounts: A file named {{{accounts.yaml}}} is created by {{{setup/qemu/30_accounts_to_yaml.py}}} during node setup. This script calls out to the tmcd system to get the account information. So this information is retrieved on the pnode at swap in. It is not static. See [wiki:ContainerFilesDoc#bootstrap_call_tree this section of the Containers Files Wiki page] for information about where and when that happens. The {{{accounts.yaml}}} file is then read by {{{setup/qemu/35_yaml_to_passwd.py}}} which converts the yaml into /etc/passwd format. Then setup/qemu/50_root_fs.py}}}, a script which mounts the qemu node disc and configures the qemu instance by writing to the disc image, copies the gnerated {{{/etc/passwd}}} to {{{/etc/passwd}}} in the qemu image's file system. 
+      * user accounts: A file named {{{accounts.yaml}}} is created by {{{setup/qemu/30_accounts_to_yaml.py}}} during node setup. This script parses the file {{{/var/emulab/boot/tmcc/accounts}}} the account information. (Where does this file come from?) So this information is retrieved on the pnode at swap in. It is not static. See [wiki:ContainerFilesDoc#bootstrap_call_tree this section of the Containers Files Wiki page] for information about where and when that happens. The {{{accounts.yaml}}} file is then read by {{{setup/qemu/35_yaml_to_passwd.py}}} which converts the yaml into /etc/passwd format. Then setup/qemu/50_root_fs.py}}}, a script which mounts the qemu node disc and configures the qemu instance by writing to the disc image, copies the gnerated {{{/etc/passwd}}} to {{{/etc/passwd}}} in the qemu image's file system. 
       * local mounts (including user:~): A file named {{{file_system.yaml}}} is created by {{{setup/qemu/40_file_systems.py}}} just after node swapin (on the pnodes). This file looks a the locally mounted file systems put there by DETER via  a call to {{{mount -a}}}. It parses the output looking for hardcoded strings "users", "/proj", "/share", and "/groups". So it leverages existing DETER mechanisms that configure the pnode. No static information.