| 1 |
M. Edward (Ed) Borasky wrote: |
| 2 |
|
| 3 |
>Thierry Carrez wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
> |
| 7 |
>>Hi folks, |
| 8 |
>> |
| 9 |
>>I would like to get your opinion on Enterprise-oriented desktop |
| 10 |
>>deployment tools for Gentoo Linux (or the lack of). |
| 11 |
>> |
| 12 |
>>As a small company CIO, I deployed Gentoo on a small scale here but |
| 13 |
>>quickly ran into scaling problems and the lack of tools to help. |
| 14 |
>> |
| 15 |
>> |
| 16 |
I have deployed gentoo on openmosix for the reason of scale, where only |
| 17 |
one machine was the subject of configuration and point of access, while |
| 18 |
all neighbor nodes were less specific in configuration but all shared |
| 19 |
kernel. |
| 20 |
|
| 21 |
openmosix is more secure than plain old IP, given its custom marked |
| 22 |
packets (or something keen like that) and is well suited to LAMP which |
| 23 |
can occasionally expect a cgi process to take a dump or hang or freeze, |
| 24 |
upon the loss of a node holding its virtual process. open source |
| 25 |
databases have lousy replicatoin, or at least did when i was undertaking |
| 26 |
this. its unlikely the IO-bound processes will migrate, but the |
| 27 |
linked-list traversals deservedly take a hike(ie migrate) when the app |
| 28 |
design falls short. |
| 29 |
|
| 30 |
so the question of how to begin locking down packages, etc for HA, |
| 31 |
that's where staging and testing plans are of key importance. |
| 32 |
|
| 33 |
this is where my own syadmin handywork started with a cloning system: |
| 34 |
the mothership on one side, and a rescue disc, gig-e hub, and a |
| 35 |
nc/gnutar combo to clone and stage mutations/development. |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives