refine strategy to spot ip address, keep on calling guest_ipv4

[build.git] / README-pldistros.txt

diff --git a/README-pldistros.txt b/README-pldistros.txt
index 513fedb..284cf0d 100644 (file)
--- a/README-pldistros.txt
+++ b/README-pldistros.txt
@@ -20,16 +20,31 @@ missing files are searched in the planetlab distro
        set of packages required for building
 ./build/config.<pldistro>/bootcd.pkgs
        contents of the bootcd image
-./build/config.<pldistro>/bootstrapfs.pkgs
-       the standard contents of the node root 
-       used to generate yumgroups.xml
-./build/config.<pldistro>/bootstrapfs-*.pkgs
-       all *.pkgs files here - produce additional node root images (tar.bz2)
-./build/config.<pldistro>/myplc.pkgs
-       contents of the myplc image
-./build/config.<pldistro>/vserver.pkgs
+./build/config.<pldistro>/nodeimage.pkgs
+       the standard contents of the node software
+        this results in a tarball (tar.bz2) 
+       also used to generate yumgroups.xml on the plc side
+./build/config.<pldistro>/nodeimage-*.pkgs
+       each of these files results in an extension tarball
+./build/config.<pldistro>/sliceimage.pkgs
        the contents of the standard vserver reference image
-./build/config.<pldistro>/vserver-*.pkgs
+./build/config.<pldistro>/sliceimage-*.pkgs
        all *.pkgs files here - produce additional vserver images
 ./build/config.<pldistro>/vtest.pkgs
        used to create test vservers for myplc-native
+./build/config.<pldistro>/yumexclude.pkgs
+       describe the set of node packages that are produced by the myplc build
+       and thus should be excluded from the stock fedora repos
+
+=== extensions
+as of this writing extensions are managed as follows:
+- at node installation, the tarball produced from nodeimage.pkgs is
+downloaded and untared to produce the node root filesystem
+- then we attempt to install an extension corresponding to each of the
+extensions that the node has in its 'extensions' tag
+- the first method is to try and download a tarball named after the
+extension. such tarballs are produced by the build from a .pkgs file,
+see above
+- if that fails, then the extension install is attempted through a
+ yum groupinstall extension<nodegroup>
+