X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8645F.4DED85D9@onstor-exch02.onstor.net>; Thu, 31 Jan 2008 16:16:27 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Bobcat to Cougar migration document for review
Date: Thu, 31 Jan 2008 16:16:26 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08058C57@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E08058C2D@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Bobcat to Cougar migration document for review
Thread-Index: AchkWc6L3L8QCP1dTCKQg6qwA8nKBAAATKQAAAEGOiA=
From: "Tim Gardner" <tim.gardner@onstor.com>
To: "Narain Ramadass" <narain.ramadass@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>
Cc: "Sripal Surendiran (HCL)" <sripal.surendiran@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>,
	"Jonathan Goldick" <jonathan.goldick@onstor.com>,
	"Sudharsan Srinivasan" <sudharsan@onstor.com>,
	"Deepak Veliath" <deepak.veliath@onstor.com>

Thanks Narian. Nice piece of work by Deepak.
One of the listed requirements is that we only support migration from
R98 based systems. This means we will not have to worry about more than
one
flash filesystem layout.

> -----Original Message-----
> From: Narain Ramadass
> Sent: Thursday, January 31, 2008 2:58 PM
> To: Andy Sharp
> Cc: Sripal Surendiran (HCL); Brian DeForest; Tim Gardner; Jonathan
> Goldick; Sudharsan Srinivasan; Deepak Veliath
> Subject: RE: Bobcat to Cougar migration document for review
>=20
> Andy,
>=20
> PFA the mail from DeepakV regarding the BSD disklabels being read from
> Linux. This is an initial finding and we will be attempting to script
this
> to work for both - the old as well as the new CF layout.
>=20
> As for the FTI related content in the document:
>=20
> 1. The migration strategy is assumed to be a variant of "system config
> copy". Our thinking was on the lines of this being included with
Cougar
> for sometime and dropped thereafter. "System Config Copy" would
therefore
> recognize the BSD disklabels on the secondary flash and copy the files
> appropriately in case a migration were required.
>=20
> 2. In general FTI and "system config copy" work independently of each
> other - but are "aware" of each other and share a lot of code - that
is
> the purpose of bringing them together in the document.
>=20
> HTH,
> Narain.
>=20
> -----Original Message-----
> From: Andy Sharp
> Sent: Thursday, January 31, 2008 2:37 PM
> To: Sripal Surendiran (HCL)
> Cc: Brian DeForest; Tim Gardner; Jonathan Goldick; Sudharsan
Srinivasan;
> Narain Ramadass
> Subject: Re: Bobcat to Cougar migration document for review
>=20
> On Thu, 31 Jan 2008 05:46:25 -0800 "Sripal Surendiran (HCL)"
> <sripal.surendiran@onstor.com> wrote:
>=20
> > Hi All,
> >
> > PFA document that contains strategy for migrating from Bobcat to
> > Cougar system. Please look into the document and let me know your
> > thoughts. Regards Sripal.
>=20
> Page 1
>=20
> +  I haven't been able to read a bobcat compact flash in a linux
system.
>    Have you?
>=20
> Page 2
>=20
> +  Section 1, Line #11: the directory is the same -- it's the same
code,
>    after all.
>=20
> +  Section 2, Assumptions and dependencies.  I don't agree with a lot
of
>    these assumptions and dependencies, like #2, #3, #4, #7, and #9.
>    There is no reason why a migration should be dependent on FTI.  FTI
>    can use it or whatever, but it should be modular, separate,
>    preferably something that can be run from a bash prompt or nfxsh
>    prompt.  A shell script would be fine in my opinion.
>=20
>=20
> I agree with Tim, a proper func-spec document is most likely warranted
> here.
