From: Thierry Parmentelat <thierry.parmentelat@sophia.inria.fr>
Date: Fri, 11 Jan 2008 17:11:34 +0000 (+0000)
Subject: First draft of a dual method for installing extensions
X-Git-Tag: 4.2-rc2~264
X-Git-Url: http://git.onelab.eu/?p=build.git;a=commitdiff_plain;h=622541b84ce8280183701c35ae22572ecb8f72d4

First draft of a dual method for installing extensions
- core tarball always installed through the tarball
- extensions (nodegroups) are then attempted by the same method
  i.e. by fetching PlanetLab-Bootstrap-%s.tar.bz2
- if that fails, then we try via
  yum groupinstall extension<nodegroup>

NOTE.
due to a bug with GetNodes that causes the nodegroups fetching part to fail
I could not have the tests completed yet
However nodes should correctly install the core software
---

diff --git a/README-pldistros.txt b/README-pldistros.txt
index 513fedb4..cdb3fee9 100644
--- a/README-pldistros.txt
+++ b/README-pldistros.txt
@@ -23,8 +23,12 @@ missing files are searched in the planetlab distro
 ./build/config.<pldistro>/bootstrapfs.pkgs
 	the standard contents of the node root 
 	used to generate yumgroups.xml
+./build/config.<pldistro>/bootstrapfs.pkgs
+	specification for the contents of the core for the node
+	software
+        this results in a tarball (tar.bz2) 
 ./build/config.<pldistro>/bootstrapfs-*.pkgs
-	all *.pkgs files here - produce additional node root images (tar.bz2)
+	each of these files results in an extension tarball
 ./build/config.<pldistro>/myplc.pkgs
 	contents of the myplc image
 ./build/config.<pldistro>/vserver.pkgs
@@ -33,3 +37,16 @@ missing files are searched in the planetlab distro
 	all *.pkgs files here - produce additional vserver images
 ./build/config.<pldistro>/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<nodegroup>
+
diff --git a/config.onelab/extension-umts.pkgs b/config.onelab/extension-umts.pkgs
new file mode 100644
index 00000000..bb63b376
--- /dev/null
+++ b/config.onelab/extension-umts.pkgs
@@ -0,0 +1,5 @@
+# $Id$
+groupname : extensionumts
+groupdesc : planetlab node umts extensions
+package: nozomi
+package: comgt
diff --git a/config.onelab/extension-wifi.pkgs b/config.onelab/extension-wifi.pkgs
new file mode 100644
index 00000000..aa95c390
--- /dev/null
+++ b/config.onelab/extension-wifi.pkgs
@@ -0,0 +1,18 @@
+# $Id$
+#
+# first attempt for an extensible bootstrapfs contents
+#
+# the groupname should start with extension as the bootmanager 
+# computes it as extension<nodegroup>
+# the present file's name can be either
+# (*) bootstrapfs-something.pkgs
+# in which case the tarball will be elaborated at build-time
+# (*) anything else otherwise
+# 
+# at runtime, the choice between tarball-install or yum install
+# depends on whether the tarball can be downloaded or not
+#
+groupname : extensionwifi
+groupdesc : planetlab node wifi extensions
+package: madwifi
+package: wireless-tools