In concept it's very attractive. In reality, maintenance sometimes has to be applied to read/write directories. Then you get into all kinds of complex scenarios keeping everything at the same patch level. I'm looking at keeping just a gold image current with patches and software packages, and then essentially recreating the associated cloned instances via selective disk copy and scripts upon reboot. No shared disks in the plan, but I think the ideal solution is still evolving...
Ray Mrohs Energy Information Administration U.S. Department of Energy -----Original Message----- From: Biggs, Eric J [IT] [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 06, 2005 12:58 PM To: [email protected] Subject: Shared maintenance disks Has anyone on the list implemented a shared Linux volume scenario where you put maintenance on one guest and then share it amongst all the guests in a read only fashion? Something like that is described in this Redbook: http://www.redbooks.ibm.com/redbooks/pdfs/sg246824.pdf (Part 3). If you have, how does RPM handle things? If you really trusted your own methods and procedures, could you just keep RPM updated on one guest and remove the actual rpm software from all the other ones? This assumes that you would have every guest identical, which may or may not be practical. Just some thoughts... Eric Biggs Sprint Nextel ---------------------------------------------------------------------- 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
