Most definitely #1 option. The biggest obstacle for a Unix admin person is
to loose all control of whatever he/she is administrating. Mainframers keep
control of the box and anything that spills into VM, images, performance of
VM, capacity planning, software upgrades of VM, VM's TCPIP stack, guest
lans .... and let the application people administer their own servers. This
usually is the most amicable solution and spawns friendly interaction
between the two groups, which I think helps in skills transfer. Carlos :-)
Carlos A. Ordonez
IBM Corporation
Server Consolidation
|---------+--------------------------->
| | Rich Blair |
| | <RichB@allensysg|
| | roup.com> |
| | Sent by: Linux |
| | on 390 Port |
| | <[EMAIL PROTECTED]|
| | RIST.EDU> |
| | |
| | |
| | 05/03/2002 02:30|
| | PM |
| | Please respond |
| | to Linux on 390 |
| | Port |
| | |
|---------+--------------------------->
>-------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| From:
|
| Subject: many Linux guests under vm. how to manage.
|
|
|
>-------------------------------------------------------------------------------------------------------------------------------|
We're a Software company and have many products and many developers.
We'd be interested in hearing your thoughts on ways to manage many Linux
guests in a development environment.
Options we've considered:
1. Give each development group their own Linux. Possibly a couple of
members of the group serve as admins and have root authority. They would
be
responsible for the care and feeding of their respective Linux system. We
only get involved if requirements extend to VM admin tasks.
2. We (IBM syprogs) micromanage each Linux - retaining complete control of
each system - never divulging the root password etc. We do all Linux
upgrades, vm work, etc...
Thanks.
