First off, I need to shake the hands of the support folks at DCC. They have been responsive, and helpful - even to a hobbyist.
I got Debian 4.0 (etch) installed, and started to configure it to use the DCC packages, things were not going as smoothly as they could have. I emailed support at DCC, and the next day had some decent email from the support folks there. Apparently DCC is meant to run on Debian 3.1 (sarge).
So, i’ve been playing the install-the-distro game since then. At this time, sarge is installed. I did build it with the 2.6 kernel, and after initial configuration everything was working well. But there was no X server.
As of now, I’ve decided against completing an X install at this point. It’s just not working well - esp. under Sarge (Debian 3.1). I’m using the distro’s shell.
I have to give gereat credit to the folks at DCC. I’ve submitted 3 different helpdesk tickets, all of them have been answered within the week. Very responsive folks.
The big problem that i’m having at this point is to get the boot image for the worker nodes built. It seems like dcc_buildimage is having problems doing the final installation in the /var/lib/systemimager directory.
So, I’m in a rut right now, trying to understand what is happening.
The steps taht you must use once you get Debian Sarge installed is:
Update your system.
Run the dcc_buildimage. This will create a directory /var/lib/systemimagers/images/node where it will store the boot image.
After that is successful, you try to have the system discover a new node by running dcc_discovernode. I cant do this yet, because the dcc_buildimage is not returning with success.
At any rate, I highly recommend DCC, and the technical support they provide.

0 Responses to “Cluster pt 5. Next steps & challenges…”