X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C86456.BF35A721@onstor-exch02.onstor.net>; Thu, 31 Jan 2008 15:15:11 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C86456.BF35A721"
Content-class: urn:content-classes:message
Subject: RE: Bobcat to Cougar migration document for review
Date: Thu, 31 Jan 2008 15:15:11 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08058BA8@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04EC247B1@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Bobcat to Cougar migration document for review
Thread-Index: AchkDocLwpIkfzgAQOa6CoxV6gaGLQAQ/cpg
From: "Tim Gardner" <tim.gardner@onstor.com>
To: "Sripal Surendiran (HCL)" <sripal.surendiran@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>,
	"Jonathan Goldick" <jonathan.goldick@onstor.com>
Cc: "Sudharsan Srinivasan" <sudharsan@onstor.com>,
	"Narain Ramadass" <narain.ramadass@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C86456.BF35A721
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I'd like to see a real functional specification that adheres to the
standard documentation template.

=20

Most of the items in the requirements section are not requirements; they
are implementation details.=20

We need a clear definition of the requirements.

=20

This document assumes that migration will only be performed when the
system is first installed. I believe that it is likely that a customer
will deploy the cougar in eval mode and then later migrate the config
from a bobcat.

This needs to be discussed. Perhaps the process is to force the cougar
to go through FTI again. This needs to be documented.

=20

1.4. Restore from secondary flash is ambiguous. This option needs to
clearly indicate something like "Migrate configuration from Bobcat
flash".

=20

1.4. Since this document is providing implementation details, I would
like to know how you plan to read the BSD flash from Linux.

Simply mounting the BSD flash will not work due to the incompatible
block layout. Andy has some ideas on this but there

is a fair amount of work involved.

=20

WWN on cougar is derived from MAC address. As part of the migration you
will need to program the Cougar chassis seep with the

MAC address. I don't believe that the bobcat MAC address is stored on
the flash since it comes from the PCB seep on

the bobcat. This issue needs to be addressed.

=20

Network configuration may be different if migrating from a 2220 since a
2220 only has 2 network interfaces.

This needs to be addressed.

=20

________________________________

From: Sripal Surendiran (HCL)=20
Sent: Thursday, January 31, 2008 5:46 AM
To: Brian DeForest; Tim Gardner; Andy Sharp; Jonathan Goldick
Cc: Sudharsan Srinivasan; Narain Ramadass
Subject: Bobcat to Cougar migration document for review

=20

Hi All,

=20

PFA document that contains strategy for migrating from Bobcat to Cougar
system. Please look into the document and let me know your thoughts.

=20

Regards

Sripal.


------_=_NextPart_001_01C86456.BF35A721
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:navy;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dnavy>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I&#8217;d like to see a real =
functional
specification that adheres to the standard documentation =
template.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Most of the items in the =
requirements
section are not requirements; they are implementation details. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>We need a clear definition of the
requirements.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>This document assumes that =
migration will
only be performed when the system is first installed. I believe that it =
is
likely that a customer will deploy the cougar in eval mode and then =
later
migrate the config from a bobcat.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>This needs to be discussed. Perhaps =
the
process is to force the cougar to go through FTI again. This needs to be
documented.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>1.4. Restore from secondary flash =
is
ambiguous. This option needs to clearly indicate something like =
&#8220;Migrate
configuration from Bobcat flash&#8221;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>1.4. Since this document is =
providing
implementation details, I would like to know how you plan to read the =
BSD flash
from Linux.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Simply mounting the BSD flash will =
not
work due to the incompatible block layout. Andy has some ideas on this =
but
there<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>is a fair amount of work =
involved.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>WWN on cougar is derived from MAC =
address.
As part of the migration you will need to program the Cougar chassis =
seep with
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>MAC address. I don&#8217;t believe =
that
the bobcat MAC address is stored on the flash since it comes from the =
PCB seep
on<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>the bobcat. This issue needs to be
addressed.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Network configuration may be =
different if
migrating from a 2220 since a 2220 only has 2 network =
interfaces.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>This needs to be =
addressed.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Sripal
Surendiran (HCL) <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, January =
31, 2008
5:46 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Brian DeForest; =
<st1:PersonName
w:st=3D"on">Tim Gardner</st1:PersonName>; <st1:PersonName =
w:st=3D"on">Andy Sharp</st1:PersonName>;
<st1:PersonName w:st=3D"on">Jonathan Goldick</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Sudharsan Srinivasan; =
Narain
Ramadass<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Bobcat to Cougar =
migration
document for review</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Hi =
All,</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>PFA document that contains strategy for migrating =
from
Bobcat to Cougar system. Please&nbsp;look into the document and let me =
know
your thoughts.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Regards</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Sripal.</span></font><o:p></o:p></p>

</div>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C86456.BF35A721--
