X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C86F6F.6DA6531A@onstor-exch02.onstor.net>; Thu, 14 Feb 2008 18:09:35 -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: Cougar to Bobcat migration strategy document for review
Date: Thu, 14 Feb 2008 18:09:35 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0856E7F2@onstor-exch02.onstor.net>
In-Reply-To: <20080214170406.1fa857f7@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cougar to Bobcat migration strategy document for review
Thread-Index: AchvbqopvgW12kSCT9ObBmiSqQQqFAAAK1Bw
From: "Raj Kumar" <raj.kumar@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Naw I still like mounting part ;-

Of course I meant "installing cougar in the rack"

-----Original Message-----
From: Andy Sharp=20
Sent: Thursday, February 14, 2008 5:04 PM
To: Raj Kumar
Cc: Sripal Surendiran (HCL); dl-Design Review
Subject: Re: Cougar to Bobcat migration strategy document for review

On Thu, 14 Feb 2008 16:09:19 -0800 "Raj Kumar" <raj.kumar@onstor.com>
wrote:

> Hi all,
>=20
> =20
>=20
> Is everybody ok with this requirement?
>=20
> =20
>=20
> 1.	"Migration requires downtime of the entire Bobcat cluster.
>=20
> =20
>=20
> The following operation will add up to the total downtime while we
> migrate from BC to CG.
>=20
> =20
>=20
> For Each node in a cluster:
>=20
> =20
>=20
> 1.	Power down BC and take care removing all cables, label them,
> remove power cable, flash cards, label them.
> 2.	Remove BC from the rack
> 3.	mount cougar
        ^^^^^^^^^^^^

Hmm, sounds rather zoological.  Perhaps "Install Cougar in rack"?

> 4.	Installing FP/FC cables and modifying MAC and rebooting it
> again.
> 5.	Usual boot up time + updating config from 2ndry flash
>=20
> =20
>=20
> The above tasks can take anywhere between 50 minutes to 2 hours
> depends on the racking conditions and/or labor skills/availability.=20
>=20
> =20
>=20
> If you have a 2 node, total down time: 1 hours 40 minutes to 4 hours
>=20
> If you have 4 node: 3 hours 20 minutes to 8 hours.
>=20
> =20
>=20
> We need to be prepared for the worst case scenario as well. If for any
> reason we run into some issues bringing up services in cougar, we will
> need to revert back to BC. It will be the same time it takes to
> migrate to cougar.
>=20
> =20
>=20
> Is this downtime acceptable?=20
>=20
> =20
>=20
> Did we consider some kind of rolling upgrade? Possibly supporting
> BC-CG cluster just for upgrade purposes?
>=20
> =20
>=20
> Thanks.
>=20
> =20
>=20
> =20
>=20
> ________________________________
>=20
> From: Sripal Surendiran (HCL)=20
> Sent: Thursday, February 07, 2008 8:07 AM
> To: dl-Design Review
> Cc: Sripal Surendiran (HCL)
> Subject: Cougar to Bobcat migration strategy document for review
>=20
> =20
>=20
> Hi all,
>=20
> =20
>=20
> PFA Bobcat to Cougar migration strategy functional specification
> document. Please do respond me with your review comments.
>=20
> =20
>=20
> Regards,
>=20
> Sripal.
>=20
