X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C866A1.88F04881@onstor-exch02.onstor.net>; Sun, 3 Feb 2008 13:15:35 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C866A1.88F04881"
Content-class: urn:content-classes:message
Subject: RE: Beta Readiness Criteria Document
Date: Sun, 3 Feb 2008 13:15:35 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E080CB04C@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Beta Readiness Criteria Document
Thread-Index: Achmjn+DLSlttRCPTgmahBtOAgSlzwADRZ7C
References: <BB375AF679D4A34E9CA8DFA650E2B04E0812AF9A@onstor-exch02.onstor.net>
From: "Paul Hammer" <paul.hammer@onstor.com>
To: "Joshua Goldenhar" <IMCEAEX-_O=ONSTOR_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=JOSHUA+2EGOLDENHAR@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C866A1.88F04881
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks Josh, very helpful and a good start.
=20
Sandrine is correct, we do not currently have plans/requirements to =
increase the number of vsvr's or volumes. Also believe that the >2tb lun =
will only be available by FCS, won't make beta.=20
=20
Assume where the docs says 2 node cluster it means 2 mother boards and 1 =
physical chassis. Believe that QA is already testing with a 2 physical =
chassis and 4 mother board cfg, Vikas can you confirm?
=20
So for beta it looks like we only require 3 switches and 2 storage =
arrays supported (only surprise to me was the absence of Nexsan). This =
is good. What is a V100 Pantera? Is this Xyratex?
=20
Can you let us know what DMA we need qualified (if any) , and with what =
tape device?
=20
Client support looks good, not sure we need NT (can't recall if we even =
support today outside of an AD host), no Mac support?
=20
Thought we discussed DMIP at the team meeting last week and agreed that =
we did not have to have this support, although Cougar to Bobcat and vice =
a versa is a feasible combination. I am okay with adding it if it will =
help with the beta should not be hard to test, don't think there is any =
incompatibility between the two. Ditto for vol import.
=20
Given our customer base I would think that we may need to require Copper =
SFP's support for beta.
=20
Josh, are we providing and Pantera's for beta (Cougar with Storage pre =
configured), or are we only providing Cougar?
=20
Are we going to require a beta refresh during the beta (forces testing =
of upgrade in the field, think that would be a good test)?
=20
Post Beta Completion questions (not sure that they belong in the =
readiness doc but thought I would ask):
Do we have to retain user data created during the beta?
Do we have to retain configuration data created during the beta?
Do we have to have a way to migrate a cougar from Beta code to =
production code?
=20
Thanks,
=20
-Paul
=20

________________________________

From: Joshua Goldenhar
Sent: Sun 2/3/2008 9:59 AM
To: dl-Cougar
Subject: Beta Readiness Criteria Document



First released draft is attached. It will be kept and maintained in:

\\mightydog\Program Management\Cougar\Marketing

-Josh=20

Josh Goldenhar=20
Sr. Dir. Technical Strategy=20
ONStor, Inc. - http://www.onstor.com/=20
joshua.goldenhar@onstor.com=20
Phone: 408 963 2408, Cell: 408 547 7693=20

=20


------_=_NextPart_001_01C866A1.88F04881
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3132" name=3DGENERATOR>=0A=
<STYLE>=0A=
<!--=0A=
                        =0A=
 p.MsoNormal, li.MsoNormal, div.MsoNormal=0A=
	{margin:0in;=0A=
	margin-bottom:.0001pt;=0A=
	font-size:12.0pt;=0A=
	font-family:"Times New Roman";}=0A=
a:link, span.MsoHyperlink=0A=
	{color:blue;=0A=
	text-decoration:underline;}=0A=
a:visited, span.MsoHyperlinkFollowed=0A=
	{color:purple;=0A=
	text-decoration:underline;}=0A=
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText=0A=
	{margin:0in;=0A=
	margin-bottom:.0001pt;=0A=
	font-size:10.0pt;=0A=
	font-family:"Courier New";}=0A=
p=0A=
	{=0A=
	margin-right:0in;=0A=
	margin-left:0in;=0A=
	font-size:12.0pt;=0A=
	font-family:"Times New Roman";}=0A=
span.EmailStyle17=0A=
	{=0A=
	font-family:Arial;=0A=
	color:windowtext;}=0A=
=0A=
div.Section1=0A=
	{page:Section1;}=0A=
-->=0A=
</STYLE>=0A=
</HEAD>=0A=
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>=0A=
<DIV id=3DidOWAReplyText24182 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Thanks Josh, =
very helpful and a good start.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Sandrine is correct, we do =
not currently have plans/requirements to increase the number of vsvr's =
or volumes. Also believe that the &gt;2tb lun will only be available by =
FCS, won't make beta. </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Assume where the docs says 2 =
node cluster it means 2 mother boards and 1 physical chassis. Believe =
that QA is already testing with a 2 physical chassis and 4 mother board =
cfg,&nbsp;Vikas can you confirm?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>So for beta it looks like we =
only&nbsp;require&nbsp;3 switches and 2 storage arrays supported (only =
surprise to me was the absence of Nexsan). This is good. What is a <SPAN =
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: Arial; mso-fareast-font-family: =
'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: =
EN-US; mso-bidi-language: AR-SA">V100 Pantera? Is this =
Xyratex?</SPAN></FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Can you let us know what DMA =
we need qualified (if any) , a</FONT><FONT face=3DArial size=3D2>nd with =
what tape device?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Client support looks good, =
not sure we need NT (can't recall if we even support today outside of an =
AD host), no Mac support?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Thought we discussed DMIP at =
the team meeting last week and agreed that we did not have to have this =
support, although&nbsp;Cougar to Bobcat and vice a versa is a feasible =
combination. </FONT>I am okay with&nbsp;adding it if it will help with =
the beta&nbsp;should not be hard to test, don't think there is any =
incompatibility between the two. Ditto for vol import.</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Given our customer base I =
would think that we&nbsp;may need to&nbsp;require Copper SFP's =
support&nbsp;for beta.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Josh, are we providing and =
Pantera's for beta (Cougar with Storage pre configured), or are we only =
providing Cougar?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Are we going to require a =
beta refresh during the beta (forces testing of upgrade in the field, =
think that would be a good test)?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Post Beta Completion =
questions (not sure that they belong in the readiness doc but thought I =
would ask):</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Do we have to retain user =
data created during the beta?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Do we have to retain =
configuration data created during the beta?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Do we have to have a way to =
migrate a cougar from Beta code to production code?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>-Paul</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Joshua =
Goldenhar<BR><B>Sent:</B> Sun 2/3/2008 9:59 AM<BR><B>To:</B> =
dl-Cougar<BR><B>Subject:</B> Beta Readiness Criteria =
Document<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<DIV class=3DSection1>=0A=
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">First released draft is =
attached. It will be kept and maintained in:</SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">\\mightydog\Program =
Management\Cougar\Marketing</SPAN></FONT></P>=0A=
<P><FONT face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">-Josh</SPAN></FONT> </P>=0A=
<P><FONT face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">Josh Goldenhar</SPAN></FONT> <BR><FONT face=3DArial =
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Sr. Dir. =
Technical Strategy</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">ONStor, Inc. - <A =
href=3D"http://www.onstor.com/">http://www.onstor.com/</A></SPAN></FONT> =
<BR><FONT face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">joshua.goldenhar@onstor.com</SPAN></FONT> <BR><FONT =
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Phone: 408 963 2408, Cell: 408 547 7693</SPAN></FONT> </P>=0A=
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
style=3D"FONT-SIZE: =
12pt"></SPAN></FONT>&nbsp;</P></DIV></DIV></BODY></HTML>
------_=_NextPart_001_01C866A1.88F04881--
