Re: Shared DASD across multiple VM lpars
I would like thank everyone for the informative responses. I am in the process of implementing Dirmaint, and will begin researching CSE requirements. Bob
Re: Shared DASD across multiple VM lpars
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is exactly what CSE is meant for. Yes, we use it. CSE + Dirmaint shared directory + Shared disk == not quite a cluster. (I'm still holding on for cluster level split brain protection, as well as the nifty live migration in the someday SSI) - -- Pat Feller, Paul wrote: > We do that across several lpars. We run with a shared directory (DIRMAINT). > We have put code in place to verify that the Linux guest is not running on > another lpar. > > Paul Feller > AIT Mainframe Technical Support > > -Original Message- > From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On > Behalf Of Robert J McCarthy > Sent: Monday, November 16, 2009 3:08 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Shared DASD across multiple VM lpars > > We have a growing VM/Linux environment with currently about 75 linux guests > spread across three VM lpars. All DASD is defined as shared. All of the > linux guests have been defined as TCPIP Layer 2; so that we can easily move > guests between lpars for performance/maintenance reasons. Each guests has > unique mini-disks for the linux 191 and DASD swap spaces. Is it advisable > to share the full volumes that these mini-disks reside on, across VM lpars; > assuming of course, that a linux guest is completely shutdown and logged > off of one lpar before it is restarted on another ? > Bob -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksCDVMACgkQNObCqA8uBswUKwCgnIji3CF6qc1Wa+CPVF0DluJZ 3FUAn1nOzGRObXt/SAZZ7sG0OXBW4fWW =Em78 -END PGP SIGNATURE-
Re: Shared DASD across multiple VM lpars
We do that across several lpars. We run with a shared directory (DIRMAINT). We have put code in place to verify that the Linux guest is not running on another lpar. Paul Feller AIT Mainframe Technical Support -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Monday, November 16, 2009 3:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Shared DASD across multiple VM lpars We have a growing VM/Linux environment with currently about 75 linux guests spread across three VM lpars. All DASD is defined as shared. All of the linux guests have been defined as TCPIP Layer 2; so that we can easily move guests between lpars for performance/maintenance reasons. Each guests has unique mini-disks for the linux 191 and DASD swap spaces. Is it advisable to share the full volumes that these mini-disks reside on, across VM lpars; assuming of course, that a linux guest is completely shutdown and logged off of one lpar before it is restarted on another ? Bob
Re: Shared DASD across multiple VM lpars
You're not really specifying the requirements.. but reading between the lines - you want to be able to bring up the guest on one LPAR or the other.. so you will have to share the full volumes. You don't necessarily need unique minidisks for the 191 or swap, though... What 'is' the requirement? ;-) You can set things up to actually be live on both systems if you want - Scott On Mon, Nov 16, 2009 at 2:08 PM, Robert J McCarthy < bob.mccar...@custserv.com> wrote: > We have a growing VM/Linux environment with currently about 75 linux guests > spread across three VM lpars. All DASD is defined as shared. All of the > linux guests have been defined as TCPIP Layer 2; so that we can easily move > guests between lpars for performance/maintenance reasons. Each guests has > unique mini-disks for the linux 191 and DASD swap spaces. Is it advisable > to share the full volumes that these mini-disks reside on, across VM lpars; > assuming of course, that a linux guest is completely shutdown and logged > off of one lpar before it is restarted on another ? > Bob > >
Re: Shared DASD across multiple VM lpars
We share DASD between two z/VM LPAR's, and have guests set up so they can log on to either one. We use the Cross-System Link (XLINK) feature of CSE to make sure that they don't try to run on both LPAR's at once. Dennis "Of all tyrannies, a tyranny exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than omnipotent moral busybodies. The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for our own good will torment us without end, for they do so with the approval of their own conscience." -- C.S. Lewis -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Monday, November 16, 2009 13:34 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Shared DASD across multiple VM lpars It's the "assuming of course" part that will bite you :) One false move and wham, all is gone. And how to keep the directory in sync is another bit of the fun. The future promises to solve this for us. In the meantime, you can use CSE. Or wait... Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Monday, November 16, 2009 1:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Shared DASD across multiple VM lpars We have a growing VM/Linux environment with currently about 75 linux gues= ts spread across three VM lpars. All DASD is defined as shared. All of the = linux guests have been defined as TCPIP Layer 2; so that we can easily mo= ve guests between lpars for performance/maintenance reasons. Each guests has= unique mini-disks for the linux 191 and DASD swap spaces. Is it advisable= to share the full volumes that these mini-disks reside on, across VM lpar= s; assuming of course, that a linux guest is completely shutdown and logged = off of one lpar before it is restarted on another ? Bob
Re: Shared DASD across multiple VM lpars
It's the "assuming of course" part that will bite you :) One false move and wham, all is gone. And how to keep the directory in sync is another bit of the fun. The future promises to solve this for us. In the meantime, you can use CSE. Or wait... Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Monday, November 16, 2009 1:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Shared DASD across multiple VM lpars We have a growing VM/Linux environment with currently about 75 linux gues= ts spread across three VM lpars. All DASD is defined as shared. All of the = linux guests have been defined as TCPIP Layer 2; so that we can easily mo= ve guests between lpars for performance/maintenance reasons. Each guests has= unique mini-disks for the linux 191 and DASD swap spaces. Is it advisable= to share the full volumes that these mini-disks reside on, across VM lpar= s; assuming of course, that a linux guest is completely shutdown and logged = off of one lpar before it is restarted on another ? Bob
Re: Shared DASD across multiple VM lpars
Not in 6.1, but the future one. Not sure if it has a number or not yet. Many of us will be dancing in the streets when it shows up. Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Davis, Larry (National VM/VSE Capability) Sent: Monday, November 16, 2009 1:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Shared DASD across multiple VM lpars I bet you will be happy when z/VM 6.1 is installed and the Single image facility is ready for production. Larry Davis
Re: Shared DASD across multiple VM lpars
Single System Image is not in z/VM 6.1. It's a Statement of Direction, which means IBM intends to put it in a future release, but isn't promising anything. Dennis "Of all tyrannies, a tyranny exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than omnipotent moral busybodies. The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for our own good will torment us without end, for they do so with the approval of their own conscience." -- C.S. Lewis -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Davis, Larry (National VM/VSE Capability) Sent: Monday, November 16, 2009 13:21 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Shared DASD across multiple VM lpars I bet you will be happy when z/VM 6.1 is installed and the Single image facility is ready for production. Larry Davis -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Monday, November 16, 2009 4:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Shared DASD across multiple VM lpars We have a growing VM/Linux environment with currently about 75 linux guests spread across three VM lpars. All DASD is defined as shared. All of the linux guests have been defined as TCPIP Layer 2; so that we can easily move guests between lpars for performance/maintenance reasons. Each guests has unique mini-disks for the linux 191 and DASD swap spaces. Is it advisable to share the full volumes that these mini-disks reside on, across VM lpars; assuming of course, that a linux guest is completely shutdown and logged off of one lpar before it is restarted on another ? Bob
Re: Shared DASD across multiple VM lpars
I bet you will be happy when z/VM 6.1 is installed and the Single image facility is ready for production. Larry Davis -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Monday, November 16, 2009 4:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Shared DASD across multiple VM lpars We have a growing VM/Linux environment with currently about 75 linux guests spread across three VM lpars. All DASD is defined as shared. All of the linux guests have been defined as TCPIP Layer 2; so that we can easily move guests between lpars for performance/maintenance reasons. Each guests has unique mini-disks for the linux 191 and DASD swap spaces. Is it advisable to share the full volumes that these mini-disks reside on, across VM lpars; assuming of course, that a linux guest is completely shutdown and logged off of one lpar before it is restarted on another ? Bob
Shared DASD across multiple VM lpars
We have a growing VM/Linux environment with currently about 75 linux gues ts spread across three VM lpars. All DASD is defined as shared. All of the linux guests have been defined as TCPIP Layer 2; so that we can easily mo ve guests between lpars for performance/maintenance reasons. Each guests has unique mini-disks for the linux 191 and DASD swap spaces. Is it advisable to share the full volumes that these mini-disks reside on, across VM lpar s; assuming of course, that a linux guest is completely shutdown and logged off of one lpar before it is restarted on another ? Bob
