AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080214170337.2ea9faac@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<raj.kumar@onstor.com>,<sripal.surendiran@onstor.com>,<dl-designreview@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#mh/Mailbox/design review	0	BB375AF679D4A34E9CA8DFA650E2B04E0856E776@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 14 Feb 2008 17:04:06 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Raj Kumar" <raj.kumar@onstor.com>
Cc: "Sripal Surendiran (HCL)" <sripal.surendiran@onstor.com>, "dl-Design
 Review" <dl-designreview@onstor.com>
Subject: Re: Cougar to Bobcat migration strategy document for review
Message-ID: <20080214170406.1fa857f7@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0856E776@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04EC247CD@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0856E776@onstor-exch02.onstor.net>
Organization: Onstor
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

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

> Hi all,
> 
>  
> 
> Is everybody ok with this requirement?
> 
>  
> 
> 1.	"Migration requires downtime of the entire Bobcat cluster.
> 
>  
> 
> The following operation will add up to the total downtime while we
> migrate from BC to CG.
> 
>  
> 
> For Each node in a cluster:
> 
>  
> 
> 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
> 
>  
> 
> The above tasks can take anywhere between 50 minutes to 2 hours
> depends on the racking conditions and/or labor skills/availability. 
> 
>  
> 
> If you have a 2 node, total down time: 1 hours 40 minutes to 4 hours
> 
> If you have 4 node: 3 hours 20 minutes to 8 hours.
> 
>  
> 
> 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.
> 
>  
> 
> Is this downtime acceptable? 
> 
>  
> 
> Did we consider some kind of rolling upgrade? Possibly supporting
> BC-CG cluster just for upgrade purposes?
> 
>  
> 
> Thanks.
> 
>  
> 
>  
> 
> ________________________________
> 
> From: Sripal Surendiran (HCL) 
> 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
> 
>  
> 
> Hi all,
> 
>  
> 
> PFA Bobcat to Cougar migration strategy functional specification
> document. Please do respond me with your review comments.
> 
>  
> 
> Regards,
> 
> Sripal.
> 
