X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=README-pldistros.txt;h=cdb3fee94fc0390e8e84ad39f2fe52ebaf668f32;hb=refs%2Fheads%2Fcoblitz;hp=e68c449ee107690e999c0fce81346a5a63216349;hpb=a14676427a1e9c5c3c444e3f7689f928c8a85ba8;p=build.git diff --git a/README-pldistros.txt b/README-pldistros.txt index e68c449e..cdb3fee9 100644 --- a/README-pldistros.txt +++ b/README-pldistros.txt @@ -23,13 +23,30 @@ missing files are searched in the planetlab distro ./build/config./bootstrapfs.pkgs the standard contents of the node root used to generate yumgroups.xml +./build/config./bootstrapfs.pkgs + specification for the contents of the core for the node + software + this results in a tarball (tar.bz2) ./build/config./bootstrapfs-*.pkgs - all *.pkgs files here - produce additional node root images (tar.bz2) + each of these files results in an extension tarball ./build/config./myplc.pkgs contents of the myplc image ./build/config./vserver.pkgs the contents of the standard vserver reference image ./build/config./vserver-*.pkgs all *.pkgs files here - produce additional vserver images -./build/config./native-shell.pkgs +./build/config./vtest.pkgs used to create test vservers for myplc-native + +=== extensions +as of this writing extensions are managed as follows: +- at node installation, the tarball produced from bootstrapfs.pkgs is +downloaded and untared to produce the core node setup +- then we attempt to install an extension corresponding to each of the +nodegroups that the node is part of +- 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 +