In all the places I have worked VM has been the poor step-child that got the 
least amount of resources. I have always used a 2nd level VM system for testing 
fixes, new releases, mods, or just trying to do something stupid that I didn't 
want to take a chance of knocking out my production system with. 

I think there was one situation I ran into where the problem appeared once I 
moved it to 1st level. My first install was VM/SP 1.0 so I've gone through a 
few.

Depending on your shop, getting LPAR loaded may not be a problem, but having it 
2nd level makes it easier to do it whenever you need. 

On the other hand, having a 2nd VM LPAR could give an environment closer to 
what your production environment is.

I think it really depends on the resources you have available.

Bob   

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Moeur Tim C
Sent: Friday, January 19, 2007 10:03 AM
To: [email protected]
Subject: VM test platforms


Good morning List,

I have a question of general test and production architecture.   We
currently have some production zLinux guests running under z/VM 5.1.
z/VM is installed as an LPAR on our single Z9 server.   We had, until
recently, a second Z9 on which I was running a test VM which I could use
to apply and verify maintenance and program fixes.  After those fixes
have been deemed OK, we'd move them to the production VM system
(VMPROD).    Now,  The VMTEST Z9 has gone away and now I'm faced with a
choice of creating a second LPAR for VMTEST, or to run VMTEST as a guest
under VMPROD.

So the question is - is running my VMTEST as a guest of VMPROD good
practice?  Are there exposures to flawed maintenance or program fixes
that wouldn't surface when the platform is running as a VM Guest?   How
are those of you with current production and test VM systems doing this?

Tim
[EMAIL PROTECTED]



----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to