X-Git-Url: http://git.onelab.eu/?p=bootmanager.git;a=blobdiff_plain;f=README;h=f86a201ea1093cb3d53929c128aade90a01ab085;hp=1826c83fe3bd7eac87c15aebd4bc654620d93110;hb=HEAD;hpb=fe094f10f0d738ab448780c3d5816717b7c54fc7 diff --git a/README b/README index 1826c83..f86a201 100644 --- a/README +++ b/README @@ -1,9 +1,10 @@ -Starting with 4.3.17 (5.0?) +Starting with 5.0 === -the entry point for the boot CD is installed in +the entry point for the boot CD is installed in the location below +this is expected to return the signed shell script that runs the bootmanager /var/www/html/boot/index.php -the bootmanager rpm installs most of its stuff in +the bootmanager rpm installs most of its stuff in /usr/share/bootmanager/regular/ and the default signed script is created as /var/www/html/boot/bootmanager_regular.sh.sgn @@ -30,15 +31,27 @@ It's also possible to attach a (signed) bm script to a unique node by renaming a /var/www/html/boot/bootmanager_.sh.sgn ======================================== bootstrapfs -right now, the actual name of the bootstrapfs('s) that need to be installed is performed in -the InstallBootstrapFS step -the logic is +the actual name of the bootstrapfs('s) that need to be installed is +computed in the PLCAPI, namely the GetNodeFlavour method + +In essence: * if the node has the 'deployment' tag set, then we fetch https://.../boot/bootstrafs-.tar.bz2 +* otherwise we get +https://.../boot/bootstrafs-.tar.bz2 -* other wise we get -https://.../boot/bootstrafs-.tar.bz2 - plus -https://.../boot/bootstrafs--.tar.bz2 +* as far as extensions, we fetch +https://.../boot/bootstrafs---.tar.bz2 for all defined extensions + +* also if the plainbootstrapfs tag is set, then the uncompressed files + are fetched + +======================================== yum repo + +* if the node has the 'deployment' tag set, then we use +http://.../install-rpms/alpha + +* otherwise +http://.../install-rpms/