aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEric Thibodeau <kyron@neuralbs.com>2008-08-17 16:19:49 -0400
committerEric Thibodeau <kyron@neuralbs.com>2008-08-17 16:19:49 -0400
commit41a9ffbf4988db8fe6500af8ed3f642c4cd7a73c (patch)
tree879d55b95a7fd2fc9d267c45739f38daaf625f69
parentAdding infrastructure for node management automation (diff)
downloadclustering-livecd-41a9ffbf4988db8fe6500af8ed3f642c4cd7a73c.tar.gz
clustering-livecd-41a9ffbf4988db8fe6500af8ed3f642c4cd7a73c.tar.bz2
clustering-livecd-41a9ffbf4988db8fe6500af8ed3f642c4cd7a73c.zip
Adding a FAQ (anticipated questions)
-rw-r--r--FAQ19
1 files changed, 19 insertions, 0 deletions
diff --git a/FAQ b/FAQ
new file mode 100644
index 0000000..c1ba76d
--- /dev/null
+++ b/FAQ
@@ -0,0 +1,19 @@
+Q: The CD is booted...what do I do now.
+A: Well, the MOTD does tell you to edit some files and run 'cluster-setup'. If you're impatient and just want the script to configure eth0 as your outside NIC and eth1 as your clustering nic, you can always try 'cluster-setup --test', which is used by the devs to setup the system quickly. If it fails, just reboot and follow the real instructions ;)
+
+Q: Can we change the nodes names to something else...say potato01 to potato64.
+A: The node names are auto-generated by the nfsroot's stateless.sh init script. You can edit that file to your leasure but it's not guaranteed that there aren't other scripts that make assumptions on the fact that the nodes are named "nodeXX". Most of the important scripts are the onces called by dnsmasq's dhcp-script= directive (/etc/dnsmasq.conf). Follow that trail to know more.
+
+Q: Can the livecd be installed onto the system in a more permanant manner?
+A: Yes and no. It hasn't been tested but the livecd is essentially Gentoo's livecd with the installer and the clustering packages. If you do a diff on the official spec files and you won't see much difference apart from the added packages and the local folders for overlaying. As any live medium would recommend, you might get better results by installing a clean Gentoo stage3 system and using the overlays and ebuilds used by the livecd. They were written with the intent that they would also be used to kickstart a cluster installation from a stage3 so everything should work but _do_ read the informative messages and warnings.
+
+Q: Does the livecd have OpenMOSIX (or a similar pseudo-SMP-machine emulator)?
+A: No.
+
+Q: How do I know which packages are provided on the livecd?
+A: Until catalyst auto-generates a nice lising of the provided packages :), simply look at the spec files under catalyst/*/2008.0/specs/amd64/.
+
+Q: How do I add packages to the NFSroot, and can I do this from the livecd?
+A1: Use catalyst and the nfsroot spec files to generate a new image. The process is actually quite rapid once you have the basic environment set up as described in the HOWTOs. If this is not a critical running environment, you could even modify catalyst to dump the resulting image directly into /tftpboot/nfsroot/$ARCH to your likings (see catalyst's config for that).
+A2: No...you're just being silly now.
+