Re: BaseVol/GuestVol server for SLES9
Susan, I'd like to save disk storage as well as simplify maintenance so thought the concept of a basevol/guestvol penguin colony sounded perfect. Some shops have used it and are using it, I believe. Some have backed away from it. Are people still using basevol/guestvol? I'm a relative newbie, so what might be obvious to most administrators is lost on me. Then perhaps you want to start with a simpler approach. I've had discussions about this with Mike before. We don't agree much. I recall one discussion, and yes we agreed to disagree. I believe the main reason Mike does it the way he does is that it simplifies the cloning process/scripts. Simplify, yes, but not really for the cloning script. Cloning 6 file systems instead of 1 should only require an additional 5 function calls to copy_disk(). The main reason we used just a single root file system is because there doesn't seem to be a one size fits all when trying to decide which file systems to break out and how much space to give them. This book was written to get shops going with z/VM and Linux. I know people who have used the books then modified the master (golden) image in a number of different ways. One just went to a single 3390-9 over / (to give 6.9GB of space instead of 2.3GB) and no modification to the clone script was needed. Another added more file systems per Mark's suggestion and modified the cloning process accordingly. The book quotes Albert Einstein: Everything should be made as simple as possible, but not simpler. Perhaps a single file system is too simpler I know some shops are using a number o 3390-3s or maybe a single 3390-9 to create a single volume group. Perhaps 1/2 to 2/3 of that volume group is carved into logical volumes for file systems as Mark suggests. Then if any of the file systems start to fill up, the logical volumes can be dynamically extended. For a while on this list, there was a recommendation to keep the root file system on a conventional file system, not a logical volume. That can still be done while using logical volumes for all other non-root file systems. This is another, more flexible approach, that probably comes under the clause but not simpler. I have been doing work with IBM middleware and find that /opt often needs to be large. I've modifed the cloning process to clone a two volume system: 100 minidisk over / and a 103 over /opt (101 and 102 are VDISK swap spaces). I wrote up that process in cookbook-style steps if anyone is interested. The only way I've built a Linux system is outlined in the Redbook z/VM and Linux on zSeries: From LPAR to Virtual Servers in Two Days There are updated books - see the top three entries on linuxvm.org/present - but they still use just a single root file system. What are other people using for the layout of their master/golden image? Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- 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
BaseVol/GuestVol server for SLES9
Hi Mark, thanks for replying. In my mind, the basevol/guestvol concept replaces the whole cloning philosophy... so laying out the file system now is crucial. Since cloning the basevol won't be necessary, I'd imagine breaking these out into their own file systems may not be an issue...as long as they are R/O. Please bear with me (this is still very new to me), but do you put your file systems on their own minidisks and then group them together as one logical volume? Since the file systems will be R/O, is there any harm in placing these into an LVM (in the basevol/guestvol scheme)? Is there a way to easily determine the amount to allocate to each file system? thanks again... Susan -- Date:Wed, 20 Jun 2007 16:19:36 -0600 From:Mark Post [EMAIL PROTECTED] Subject: Re: BaseVol/GuestVol server for SLES9 On Wed, Jun 20, 2007 at 4:50 PM, in message OF8382A14B.6368F7C0-ON85257300.0070757D-85257300.00727751 @navyfederal.org= , Susan Zimmerman [EMAIL PROTECTED] wrote:=20 -snip- The only way I've built a Linux system is outlined in the Redbook z/VM and Linux on zSeries: From LPAR to Virtual Servers in Two Days. Everything gets installed in / (root)... that is the only mount point (aside from swap) defined. I've had discussions about this with Mike before. We don't agree much. = From my perspective building a system with everything in one file system = is just asking for trouble later on. My standard build breaks out the = following into their own file system: /home /opt /srv (If you're going to be actually putting anything in there. = Alternately you can make /srv/ftp or /srv/www the mount points, but then = you're hiding the stuff that might have gotten installed into the = directories underneath /srv/www) /tmp /usr /var I believe the main reason Mike does it the way he does is that it = simplifies the cloning process/scripts. For this basevol/guestvol setup, do I still only set up one partition on the base volume with the mount point of /?Do I set up any mount point on the guest volume? See above. I presume everything gets installed on the base volume...just not sure about the directories.The HOWTO documents the different directories...but doesn't outline different mount points so I'm not sure how to proceed. The doc instructs to conduct a completely normal installation, following SUSE's instruction. YaST makes it really easy to break out the various file systems, so I = would do that. I normally make my non-root file systems LVM logical = volumes. I'm not sure if that would mess up Bill's basevol/guestvol = scheme or not. (I haven't ever played with it, and I haven't re-read it = in quite a while.) Mark Post -- 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
Re: How to add Layer2 network device to linux guest machine
How do I need to define the NICDEF definition. I looked up the manual and there was not any ETHERNET option for TYPE on NICDEF statement. I tried NICDEF 0700 TYPE ETHERNET LAN SYSTEM VSWITCHE and tried to save the profile and the VM complained about TYPE ETHERNET with the following DVHREQ2288I Your REPLACE request for LINDFLT at * has been accepted. DVHBXX6213E z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 1.0 DVHBXX6213E HCPDIR750I RESTRICTED PASSWORD FILE NOT FOUND DVHBXX6213E NICDEF 0700 TYPE ETHERNET LAN SYSTEM VSWITCHE DVHBXX6213E LIN00110 DVHBXX6213E HCPDIR751E INVALID OPERAND - ETHERNET FOLLOWING PROFILE DVHBXX6213E LINDFLT DVHBXX6213E HCPDIR1775E PROFILE DEFINITION LINDFLT IS INVALID AND WILL DVHBXX6213E NOT BE PROCESSED FOR ANY USER DEFINITIONS THAT INCLUDE IT. DVHBXX6213E EOJ DIRECTORY NOT UPDATED DVHREP3212E Unexpected RC= 2, from: EXEC DVHBBXXA P DVHREQ2289E Your REPLACE request for LINDFLT at * has failed; with RC DVHREQ2289E = 3212. Thanks, Ashwin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Wednesday, June 20, 2007 3:27 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: How to add Layer2 network device to linux guest machine On Wed, Jun 20, 2007 at 3:24 PM, in message [EMAIL PROTECTED], Bhemidhi, Ashwin [EMAIL PROTECTED] wrote: We defined NICDEF statements in the VM profile. Please see below VM guest profile contains the following: -- NICDEF 0600 TYPE QDIO LAN SYSTEM VSWITCH1 NICDEF 0700 TYPE QDIO LAN SYSTEM VSWITCHE From an Alan Altmark posting on this list back in August 2006: 1. Don't forget to change the NICDEF / DEFINE NIC to have a TYPE ETHERNET also. Mark Post -- 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
Re: mod_dav_svn on s390x
Not sure what distro you're using, but here's the versions available in RHEL 5: # rpm -q mod_dav_svn subversion httpd mod_dav_svn-1.4.2-2.el5 subversion-1.4.2-2.el5 httpd-2.2.3-6.el5 -Brad On Wed, 2007-06-20 at 16:36 -0400, Jon Brock wrote: Does anyone out there have a mod_dav_svn.so for zlinux that is later than 1.1.4? I have run into version problems trying to get WebSphere/HATS to work correctly with Subversion. I have Subversion 1.4.3 and Apache 2.0.52, but when I access our repository via Firefox it says Powered by Subversion version 1.1.4. I think it is due to an old mod_dav_svn.so module, but it looks like I would have to recompile Apache in order to get an updated one. I can't find a later RPM for Apache, or I would just use that. Thanks, Jon -- 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
Re: How to add Layer2 network device to linux guest machine
Exactly what errors are you getting from Linux? Did you have any luck echoing 1 to .../layer2 before echoing 1 to .../online and/or specifying OPTIONS='layer2=1' in /etc/sysconfig/network-scripts/ifcfg-ethN? On Thu, 2007-06-21 at 10:25 -0500, Bhemidhi, Ashwin wrote: How do I need to define the NICDEF definition. I looked up the manual and there was not any ETHERNET option for TYPE on NICDEF statement. I tried NICDEF 0700 TYPE ETHERNET LAN SYSTEM VSWITCHE and tried to save the profile and the VM complained about TYPE ETHERNET with the following DVHREQ2288I Your REPLACE request for LINDFLT at * has been accepted. DVHBXX6213E z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 1.0 DVHBXX6213E HCPDIR750I RESTRICTED PASSWORD FILE NOT FOUND DVHBXX6213E NICDEF 0700 TYPE ETHERNET LAN SYSTEM VSWITCHE DVHBXX6213E LIN00110 DVHBXX6213E HCPDIR751E INVALID OPERAND - ETHERNET FOLLOWING PROFILE DVHBXX6213E LINDFLT DVHBXX6213E HCPDIR1775E PROFILE DEFINITION LINDFLT IS INVALID AND WILL DVHBXX6213E NOT BE PROCESSED FOR ANY USER DEFINITIONS THAT INCLUDE IT. DVHBXX6213E EOJ DIRECTORY NOT UPDATED DVHREP3212E Unexpected RC= 2, from: EXEC DVHBBXXA P DVHREQ2289E Your REPLACE request for LINDFLT at * has failed; with RC DVHREQ2289E = 3212. Thanks, Ashwin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Wednesday, June 20, 2007 3:27 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: How to add Layer2 network device to linux guest machine On Wed, Jun 20, 2007 at 3:24 PM, in message [EMAIL PROTECTED], Bhemidhi, Ashwin [EMAIL PROTECTED] wrote: We defined NICDEF statements in the VM profile. Please see below VM guest profile contains the following: -- NICDEF 0600 TYPE QDIO LAN SYSTEM VSWITCH1 NICDEF 0700 TYPE QDIO LAN SYSTEM VSWITCHE From an Alan Altmark posting on this list back in August 2006: 1. Don't forget to change the NICDEF / DEFINE NIC to have a TYPE ETHERNET also. Mark Post -- 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 -- 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
Re: How to add Layer2 network device to linux guest machine
See below [EMAIL PROTECTED] 0.0.0700]# echo 1 /sys/bus/ccwgroup/drivers/qeth/0.0.0700/layer2 bash: /sys/bus/ccwgroup/drivers/qeth/0.0.0700/layer2: No such file or directory [EMAIL PROTECTED] 0.0.0700]# cd /sys/bus/ccwgroup/drivers/qeth/0.0.0700/ [EMAIL PROTECTED] 0.0.0700]# touch layer2 touch: cannot touch `layer2': Permission denied I also tried the following [EMAIL PROTECTED] 0.0.0700]# echo 1 /sys/bus/ccwgroup/drivers/qeth/0.0.0700/online [EMAIL PROTECTED] 0.0.0700]# cat /sys/bus/ccwgroup/drivers/qeth/0.0.0700/online 0 I get a response 0 which according to the manual it says that the interface is offline I have not tried the ifcfg-ethN option thinking that it will not work if the device itself is not seen online. Thanks, Ashwin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Thursday, June 21, 2007 11:24 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: How to add Layer2 network device to linux guest machine Exactly what errors are you getting from Linux? Did you have any luck echoing 1 to .../layer2 before echoing 1 to .../online and/or specifying OPTIONS='layer2=1' in /etc/sysconfig/network-scripts/ifcfg-ethN? On Thu, 2007-06-21 at 10:25 -0500, Bhemidhi, Ashwin wrote: How do I need to define the NICDEF definition. I looked up the manual and there was not any ETHERNET option for TYPE on NICDEF statement. I tried NICDEF 0700 TYPE ETHERNET LAN SYSTEM VSWITCHE and tried to save the profile and the VM complained about TYPE ETHERNET with the following DVHREQ2288I Your REPLACE request for LINDFLT at * has been accepted. DVHBXX6213E z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 1.0 DVHBXX6213E HCPDIR750I RESTRICTED PASSWORD FILE NOT FOUND DVHBXX6213E NICDEF 0700 TYPE ETHERNET LAN SYSTEM VSWITCHE DVHBXX6213E LIN00110 DVHBXX6213E HCPDIR751E INVALID OPERAND - ETHERNET FOLLOWING PROFILE DVHBXX6213E LINDFLT DVHBXX6213E HCPDIR1775E PROFILE DEFINITION LINDFLT IS INVALID AND WILL DVHBXX6213E NOT BE PROCESSED FOR ANY USER DEFINITIONS THAT INCLUDE IT. DVHBXX6213E EOJ DIRECTORY NOT UPDATED DVHREP3212E Unexpected RC= 2, from: EXEC DVHBBXXA P DVHREQ2289E Your REPLACE request for LINDFLT at * has failed; with RC DVHREQ2289E = 3212. Thanks, Ashwin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Wednesday, June 20, 2007 3:27 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: How to add Layer2 network device to linux guest machine On Wed, Jun 20, 2007 at 3:24 PM, in message [EMAIL PROTECTED], Bhemidhi, Ashwin [EMAIL PROTECTED] wrote: We defined NICDEF statements in the VM profile. Please see below VM guest profile contains the following: -- NICDEF 0600 TYPE QDIO LAN SYSTEM VSWITCH1 NICDEF 0700 TYPE QDIO LAN SYSTEM VSWITCHE From an Alan Altmark posting on this list back in August 2006: 1. Don't forget to change the NICDEF / DEFINE NIC to have a TYPE ETHERNET also. Mark Post -- 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 -- 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
Re: YaST2/YUP and/or rug problems
Thanks so much. That took care of my Linux Yum Server. Everything else slipped into place after that. One follow up question. What is the official SLES10 update server? It was https://update.novell.com and now a patch called switch-update-server changes it to https://nu.novell.com . Also, should YUP be syncing with this new server as well? Peter Mark Post [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 06/20/2007 10:56 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: YaST2/YUP and/or rug problems On Wed, Jun 20, 2007 at 6:36 PM, in message [EMAIL PROTECTED], Peter E. Abresch Jr. - at Pepco [EMAIL PROTECTED] wrote: All my updating stopped working for all my SLES10x guests. I have a YUM server that mirrors novell.update.com and it seems to have been working fine. I see updates every now and then. However, using YaST2 online updates shows me no new updates. When entering YaST2?s ?installation source? I get an error and YaST2 removes my YUM server. I don't know what the root cause is, but if you see an error like Can't provide /repodata/product.xml in /var/log/YaST2/y2log, then I have a workaround for you. This will be specific to your server, based on what you put in your email. Anyone else having this problem should adjust accordingly. cd /var/SLES10-YUP/SLES10/s390x/repodata/ ls -l product.xml If the file doesn't exist, download it: curl --digest --remote-time --fail \ 'https://youzmddevice:[EMAIL PROTECTED]/repo/$RCE/SLES10-Updates/sles-10-s390x/repodata/product.xml' -o product.xml yourzmddevice should be the contents of /etc/zmd/deviceid. yourzmdsecret should be the contents of /etc/zmd/secret. Make sure you put single-quotes around the URL, or escape the $ in $RCE with a backslash. Then try re-adding your YUM server back with rug. It should work now. At least, it worked for me, using update.novell.com. Mark Post -- 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 This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. -- 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
Re: mod_dav_svn on s390x
Those are the versions I need. Unfortunately, that's the problem. We let our maintenance agreement lapse, so I can't get RHEL 5; that would allow me to circumvent the whole dilemma. RHEL 4 has an old version of mod_dav_svn.so. I eventually recompiled Apache to regen the mod_dav_svn module, but that resulted in other compatibility challenges. The project for which I need the newer module continues apace, so it looks like I'm going to have to have the programmers move to CVS until we can get the contractual swamp drained. At that time, I can perhaps move them back to subversion. Thanks, Jon snip Not sure what distro you're using, but here's the versions available in RHEL 5: # rpm -q mod_dav_svn subversion httpd mod_dav_svn-1.4.2-2.el5 subversion-1.4.2-2.el5 httpd-2.2.3-6.el5 /snip -- 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
