AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<Chris.Vandever@lsi.com>,<Larry.Scheer@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	F9DCB1C30AC37B4EB352D0DE0AE18E5F011A732DED@cosmail02.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 27 Oct 2009 14:05:08 -0700
From: Andrew Sharp <andy.sharp@lsi.com>
To: "Vandever, Chris" <Chris.Vandever@lsi.com>
Cc: "Scheer, Larry" <Larry.Scheer@lsi.com>
Subject: Re: Node-specific and cluster-specific config files
Message-ID: <20091027140508.6b6617c9@ripper.onstor.net>
In-Reply-To: <F9DCB1C30AC37B4EB352D0DE0AE18E5F011A732DED@cosmail02.lsi.com>
References: <F9DCB1C30AC37B4EB352D0DE0AE18E5F011A732DEC@cosmail02.lsi.com>
	<20091027132404.0d076221@ripper.onstor.net>
	<DEC609CD0E54B2448DAF023C89AE9755E9275A47@cosmail02.lsi.com>
	<F9DCB1C30AC37B4EB352D0DE0AE18E5F011A732DED@cosmail02.lsi.com>
Organization: LSI
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

OK, I thought you wanted just node-specific, but now that I re-read your
email, you want all config files, which this list is.

On Tue, 27 Oct 2009 14:55:46 -0600 "Vandever, Chris"
<Chris.Vandever@lsi.com> wrote:

> Yes, this is exactly what I need.  Thanks.
> 
> ChrisV
> 
> ________________________________________
> From: Scheer, Larry
> Sent: Tuesday, October 27, 2009 1:51 PM
> To: Sharp, Andy; Vandever, Chris
> Subject: RE: Node-specific and cluster-specific config files
> 
> Andy, Chris,
> 
> I believe what you are asking for Chis is the list of files that are
> copied/preserved whenever a system config copy or a system upgrade is
> run correct?
> 
> If so here is the list:
> 
> etc/hosts
> etc/hosts.user
> etc/hosts.org
> etc/passwd
> etc/routes.ssc
> onstor/conf/cluster.conf
> onstor/conf/cluster.db.DB0
> onstor/conf/cluster.db.DBSYS1
> etc/resolv.conf
> etc/ssh/ssh_host_dsa_key.pub
> etc/ssh/ssh_host_dsa_key
> etc/ssh/ssh_host_key.pub
> etc/ssh/ssh_host_key
> etc/ssh/ssh_host_rsa_key
> etc/ssh/ssh_host_rsa_key.pub
> etc/localtime
> etc/syslog.conf
> etc/ntp.conf
> etc/ntp/step-tickers
> onstor/etc/snmpd.conf
> onstor/conf/stand_cluster
> etc/network/interfaces
> etc/defaultroute
> etc/shadow
> etc/gshadow
> etc/hostname
> var/spool/cron/crontabs/root
> etc/mailname
> etc/timezone
> 
> I hope this list is complete. I will need to check an upgrade log to
> see if anything is missing from this list. This is from the files:
> nfx-tree/Tools/config-files  and nfx-tree/Tools/Linux-config-files
> 
> Larry
> ________________________________________
> From: Andrew Sharp [andy.sharp@lsi.com]
> Sent: Tuesday, October 27, 2009 1:24 PM
> To: Vandever, Chris
> Cc: Scheer, Larry
> Subject: Re: Node-specific and cluster-specific config files
> 
> On Tue, 27 Oct 2009 13:49:41 -0600 "Vandever, Chris"
> <Chris.Vandever@lsi.com> wrote:
> 
> > I need to get a list of all of the files that contain either
> > node-specific or cluster-specific configuration.  The context is for
> > replacing a controller and having it essentially get its flash
> > contents from the other node of the cluster, rather than swapping in
> > the flash from the original controller as cougar/bobcat do.  I think
> > the list is probably buried in the "system upgrade" code.  I vaguely
> > remember seeing such a list in the linux/bsd specific files for
> > upgrade, but it's a vague memory.
> 
> I'm not aware of any list sorted by such a constraint.  I can think of
> several files right off that have a mixture of both in them: things
> like cron and syslog and so forth.
> 
> Perhaps Larry can come up with the first pass at such a list.  But
> let's say we had the exact list/info right now, what would we do with
> it at this moment?  Or, to put it another way, let's pretend we have
> such a list, now what?