Yes, you're right, I posted this a little quick...
What I was thinking was more like :
All of your machines share the same /usr disk, then you take the
master down, clone his /usr disk, apply patches to the new disk and
then do a little testing on the results.
If everything goes right, your take down a bunch of other machines
(lab machines), modify their profile so they point to the new /usr
disk with maintenance, and bring them back on.
As I wanted to say, your other machine are not aware of the changes
until you re-mount the NEWLY UPDATED filesystem on them...
I think it makes more sense like this...
You can always go back to the old /usr if needed.
I was thinking of creating a custom RPM file for the maintenance to
apply to the other filesystems (config files, doc, etc). I don't
know if it makes sense, but by that mean, you could deploy some
files, execute some scripts and know the actual version of
maintenance applied to your systems.
Does it makes sense ?
On 27-Jul-2006, at 19:52, John Summerfied wrote:
Dominic Coulombe wrote:
For an example, you can share RO the /usr filesystem. When you
apply a
patch on the main system which owns the disk in RW, your other
machines ARE
NOT aware of the changes until you re-mount the filesystem on each
Linux
machine.
I will put that a little more strongly: as soon as you update the
master
copy, _all_ the guests have entirely the wrong idea of where files are
and what's in them: it's perfectly possible for space a client
believes
is used by one file to be replaced with data from another.
I'd be planning on shutting down all the ro clients while the updates
are done.
I _think_ I'd have two masters, one to practice on and get right
before
going live, and at least one test guest in which to test it's
right. Do
you have a separate QA function to vet this?
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Tourist pics http://
portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
----------------------------------------------------------------------
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
