X-Git-Url: http://git.onelab.eu/?p=build.git;a=blobdiff_plain;f=README-pldistros.txt;h=284cf0dbdf149852cff98457ecf45f6768e0e2bd;hp=5d00617a5656846a7a23a00c38d5a1f7fd4cb7d2;hb=HEAD;hpb=6a284adbacec8ff3e57728f8223b79f1fe54ff53 diff --git a/README-pldistros.txt b/README-pldistros.txt index 5d00617a..284cf0db 100644 --- a/README-pldistros.txt +++ b/README-pldistros.txt @@ -1,22 +1,50 @@ -we've tried to isolate the distro-dependent configurations from the code -the places where these distro-dependent config files lie are +We've tried to isolate the distro-dependent configurations from the code -./build/groups/.xml - that is used as the yumgroups.xml +Most of the .pgks files are optional to define a new distro: +missing files are searched in the planetlab distro + +========== build environment ./build/.mk - that defines the contents of the build + that defines the contents of the build -- see Makefile ./build/-tags.mk that defines the svn locations of the various modules ./build/-install.mk optional make file to define the install target -./build/-devel.lst + +========== kernel config +./Linux-2.6/configs/kernel-2.6.--.config + (subject to change location in the future) + +========== various system images +./build/config./devel.pkgs set of packages required for building +./build/config./bootcd.pkgs + contents of the bootcd image +./build/config./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./nodeimage-*.pkgs + each of these files results in an extension tarball +./build/config./sliceimage.pkgs + the contents of the standard vserver reference image +./build/config./sliceimage-*.pkgs + all *.pkgs files here - produce additional vserver images +./build/config./vtest.pkgs + used to create test vservers for myplc-native +./build/config./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 -./bootcd/-bootcd.lst -./bootstrapfs/-base.lst -./bootstrapfs/-filesystems - all *.lst files here - produce tar.bz2 images -./myplc/-plc.lst -./vserver/-vserver.lst -./vserver/-vservers - all *.lst files here - produce vserver images