| 1 |
> > For this reason I way prefer Rocks Cluster |
| 2 |
> > that is really a breeze to install, but they do not have the bootp |
| 3 |
> > paradigm... |
| 4 |
> |
| 5 |
> Which comes back to my original post that started the thred. I wat to make an |
| 6 |
> entirely _Gentoo_ based cluster. A good reason for this is that Gentoo |
| 7 |
> well...is Gentoo, don't want/need to start the philosophical debate on why |
| 8 |
> Gentoo is better than RHE(WS), CentOS and all on which Rocks is based... |
| 9 |
> |
| 10 |
Hey, if you can create a Gentoo base cluster that is as easy to install |
| 11 |
and maintain than Rocks Cluster is, you have my support. Being using |
| 12 |
Gentoo for 3 years, the benefit is obvious to me ;) |
| 13 |
|
| 14 |
> > each node is a full image on it's own, but managmenet is |
| 15 |
> > centralized thrue the headnode. |
| 16 |
> |
| 17 |
> O_o.... now _that_ is something I would call inefficient. I can't immagine a |
| 18 |
> 1024 node cluster running off 1024 images stored on one server. |
| 19 |
|
| 20 |
In fact, there are no images. Each node is a full system on the hard |
| 21 |
drive. The head node can "order" the nodes to updates it's softwares, |
| 22 |
so updating the headnode will take care to also update the nodes |
| 23 |
automaticaly. |
| 24 |
|
| 25 |
Like you said, it's beside the point, but I think you could take a look |
| 26 |
at their design and draw some inpirations from it. An easy install like |
| 27 |
Rock Cluster but instead of using Kickstart(tm) files, would use the |
| 28 |
emerge system + distcc + quickpkg. |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-cluster@g.o mailing list |
Archives