X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7BF2D.4D185767@onstor-exch02.onstor.net>; Thu, 5 Jul 2007 09:52:49 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7BF2D.4D185767"
Content-class: urn:content-classes:message
Subject: RE: Delorean Wraup Up Report
Date: Thu, 5 Jul 2007 09:52:48 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E046A8398@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E03E568B8@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Delorean Wraup Up Report
Thread-Index: Aceu4ZySPhf98U60Q7SyVG56mh2nNQFMDQAnAB1GoqwAA5vU4AAoeM5QAAB6t9wAAPG9QAABEtPwAAAGt/cCeg+14AAASUWOAAB8YHA=
References: <BB375AF679D4A34E9CA8DFA650E2B04E034B4991@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E046A8369@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E03E568B8@onstor-exch02.onstor.net>
From: "Jonathan Goldick" <jonathan.goldick@onstor.com>
To: "Paul Hammer" <paul.hammer@onstor.com>,
	"Narayan Venkat" <narayan.venkat@onstor.com>,
	"Caeli Collins" <caeli.collins@onstor.com>,
	"Raj Kumar" <raj.kumar@onstor.com>,
	"Andrew LeFebvre" <andrew.lefebvre@onstor.com>,
	"dl-Executive" <dl-exec@onstor.com>,
	"dl-eng-ops-staff" <dl-eng-ops-staff@onstor.com>,
	"dl-Delorean Core Team" <dl-DeloreanCoreTeam@onstor.com>,
	"Kevin Matthews" <kevin.matthews@onstor.com>,
	"dl-Delorean" <dl-Delorean@onstor.com>
Cc: "Tom Gallivan" <tom.gallivan@onstor.com>,
	"Sudheesh Nair" <sudheesh.nair@onstor.com>,
	"Bob Miller" <bob.miller@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7BF2D.4D185767
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Keep in mind that our real number of supported volumes is based on the
number that can be reliably failed over.  If we take advantage of filer
groups and a 4-node cluster then we can safely say we support 2 times
the number we know can failover, 4-nodes =3D=3D> two 2-node filer =
groups.

=20

I personally prefer the approach that says that we are working to
increase the number of volumes in a filer group but if you want more
volumes, then buy more nodes for the cluster.

=20

________________________________

From: Paul Hammer=20
Sent: Thursday, July 05, 2007 10:34 AM
To: Narayan Venkat; Caeli Collins; Raj Kumar; Andrew LeFebvre;
dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews;
dl-Delorean
Cc: Tom Gallivan; Sudheesh Nair; Bob Miller
Subject: RE: Delorean Wraup Up Report

=20

=20

=20

________________________________

From: Narayan Venkat
Sent: Thu 7/5/2007 10:30 AM
To: Narayan Venkat; Caeli Collins; Paul Hammer; Raj Kumar; Andrew
LeFebvre; dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; Kevin
Matthews; dl-Delorean
Cc: Tom Gallivan; Sudheesh Nair; Bob Miller
Subject: RE: Delorean Wraup Up Report

Folks,

This issue is still no closed!  Who is talking ownership of publishing
this document so that customers can see what is officially supported?
We cannot continually skirt this issue.  We have to get more disciplined
in communicating what we officially support.  Anybody disagree with
that?

** Not sure who owns it or where we plan to put that info today, agree
with the SAG in the future.  Have no issue with us providing the info.
Need to know how we want to present it and where, QA can provide the
data itself.


If we are concerned that there are customers who are running with more
volumes in their cluster we have to provide a target timeframe for
addressing the volume issue.=20

=20

** 100 volumes support is commited to Zonda. QA is currently testing to
define the limits today (trying to get to a configuration that will
support up to 50 volumes).

I am copying Tom and Sudheesh for their comments.

Thanks.

Narayan Venkat
Vice President, Marketing
ONStor, Inc.
Tel: (408) 963-2404
Cell: (408) 221-4297.


-----Original Message-----
From: Narayan Venkat
Sent: Friday, June 22, 2007 7:51 PM
To: Narayan Venkat; Caeli Collins; Paul Hammer; Raj Kumar; Andrew
LeFebvre; dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; Kevin
Matthews; dl-Delorean
Subject: Re: Delorean Wraup Up Report

BTW, other vendors provide it in their SAG (NTAP and EMC).

Narayan Venkat
Tel: (408) 963-2404
Cell: (408) 221-4297
--------------------------
Sent from my BlackBerry Wireless Handheld


-----Original Message-----
From: Narayan Venkat
To: Caeli Collins; Paul Hammer; Narayan Venkat; Raj Kumar; Andrew
LeFebvre; dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; Kevin
Matthews; dl-Delorean
Sent: Fri Jun 22 19:50:16 2007
Subject: Re: Delorean Wraup Up Report

Let's put it in the SAG from the next release onwards.  For now a
separate doc would be sufficient.  No need to hold the release up.

Narayan Venkat
Tel: (408) 963-2404
Cell: (408) 221-4297
--------------------------
Sent from my BlackBerry Wireless Handheld


-----Original Message-----
From: Caeli Collins
To: Paul Hammer; Narayan Venkat; Raj Kumar; Andrew LeFebvre;
dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews;
dl-Delorean
Sent: Fri Jun 22 19:21:12 2007
Subject: RE: Delorean Wraup Up Report

um - the SAG is done for Delorean, and we have started burning CD's.=20

Do you want us to put everything on hold?  Do companies put these kinds
of limits in a SAG?=20


Caeli



________________________________

From: Paul Hammer
Sent: Friday, June 22, 2007 6:53 PM
To: Narayan Venkat; Raj Kumar; Andrew LeFebvre; dl-Executive;
dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews; dl-Delorean
Subject: RE: Delorean Wraup Up Report


I have no issue with taking that approach, solves several problems in
fact. We have stayed away from doing this in the past due to the
contradiction between tested limits/designed limits and our sales
collateral. I like the idea of putting this info here and refreshing
them in every release.

-Paul

________________________________

From: Narayan Venkat
Sent: Fri 6/22/2007 6:47 PM
To: Paul Hammer; Raj Kumar; Andrew LeFebvre; dl-Executive;
dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews; dl-Delorean
Subject: RE: Delorean Wraup Up Report



I think we should just include this as an addendum to our SAG under a
section called "Tested Limits".  This way it's easy to maintain and we
make this part of the release process.  In my opinion, the customer
visible "limits" are should be as follows:



a)       Number of Volumes per head and per cluster

b)       Size of the Volume/file system (with and without data
management)

c)       Max number of VServers per head and per cluster

d)       Max file size

e)       Max number of directories per single directory

f)         Max number of Open files

g)       Max TCP connections

h)       Max Virus Scan servers

i)         Max Mirror sessions

j)         Max number of LUNs per gateway and cluster

k)       Max shares

l)         Max nodes per cluster.



Narayan Venkat
Vice President, Marketing
ONStor, Inc.
Tel: (408) 963-2404
Cell: (408) 221-4297.

________________________________

From: Paul Hammer
Sent: Thursday, June 21, 2007 11:20 PM
To: Narayan Venkat; Raj Kumar; Andrew LeFebvre; dl-Executive;
dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews; dl-Delorean
Subject: RE: Delorean Wraup Up Report



Agree.



That was an open item when we discussed this previously in the Delorean
exit , who now takes this info from QA testing and puts it in a form
that  is presentable for use in the field (our sales/SE folks, Partners,
Resellers, Customers), is it multiple forms for different
needs/audiences? Any suggestions?



-Paul



________________________________

From: Narayan Venkat
Sent: Thu 6/21/2007 9:36 PM
To: Raj Kumar; Andrew LeFebvre; dl-Executive; dl-eng-ops-staff;
dl-Delorean Core Team; Kevin Matthews; dl-Delorean
Subject: RE: Delorean Wraup Up Report

Raj,



Who is going to be responsible to publish the limits document?  This
should be part of the release process.



Thanks.



Narayan





________________________________

From: Raj Kumar
Sent: Thu 6/21/2007 7:44 AM
To: Andrew LeFebvre; dl-Executive; dl-eng-ops-staff; dl-Delorean Core
Team; Kevin Matthews; dl-Delorean
Subject: Delorean Wraup Up Report

Hi,



On behalf of the Delorean team I like to submit the Delorean project
wrap up report.



\\mightydog\qe\Projects\delorean\Delorean-Wrap-Up-Report.doc
<file://mightydog/qe/Projects/delorean/Delorean-Wrap-Up-Report.doc
<file:///\\mightydog\qe\Projects\delorean\Delorean-Wrap-Up-Report.doc> >



Thanks.



--kumar :)







________________________________

From: Andrew LeFebvre
Sent: Thu 6/14/2007 5:10 PM
To: dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; Kevin
Matthews
Subject: Minutes from 6/14 Delorean FCS Review

All,

Thanks to everyone who participated in today's Delorean FCS Review
(Phase 3 Exit)!  The unanimous decision is for Delorean to FCS
immediately and RTM as soon as the gold master and copies can be created
and verified (either tomorrow or on Monday).  The GA date and whether or
not this is a mandatory upgrade will be decided by CS and others in the
next couple of weeks based on customer uptake and code stability.

Use the following link to review the presentation material:

\\mightydog\Program Management\Delorean\Phase Reviews\FCS Review\FCS
Review Agenda 6-14-07.ppt
<file://mightydog/Program%20Management/Delorean/Phase%20Reviews/FCS%20Re
view/FCS%20Review%20Agenda%206-14-07.ppt
<file:///\\mightydog\Program%20Management\Delorean\Phase%20Reviews\FCS%2
0Review\FCS%20Review%20Agenda%206-14-07.ppt> >

Here are the actions/comments I took down.=20

        1.      QA testing of increased numbers of volumes should begin
now rather than being tied to the Zonda release.  Getting to 50 volumes
can be an intermediate milestone to getting to 100.

        2.      Caeli to use EMRS to determine how many customers have
volumes greater than 32 TB.

        3.      Needs to be some discussion about how best (or if) to
package QE limits testing results for SE, CS, Sales, and customers.

        4.      Andy to develop a quantitative metric for commitments
vs. deliverables that can be used to compare projects.  Share this in
the post mortem review.

        5.      CS and SE need to review the Kerberos upgrade procedure
documentation and let DEV know if they have any questions or concerns.



Please respond to all on this e-mail if you have any additions or
clarifications.



Regards,

Andy


------_=_NextPart_001_01C7BF2D.4D185767
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]-->
<title>RE: Delorean Wraup Up Report</title>
<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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 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:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{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=3Dblue>

<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'>Keep in mind that our real number =
of
supported volumes is based on the number that can be reliably failed =
over.&nbsp; If
we take advantage of filer groups and a 4-node cluster then we can =
safely say
we support 2 times the number we know can failover, 4-nodes =
</span></font><font
size=3D2 color=3Dnavy face=3DWingdings><span =
style=3D'font-size:10.0pt;font-family:
Wingdings;color:navy'>&egrave;</span></font><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'> two 2-node =
filer groups.<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'>I personally prefer the approach =
that says
that we are working to increase the number of volumes in a filer group =
but if
you want more volumes, then buy more nodes for the =
cluster.<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>

<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'> =
<st1:PersonName
w:st=3D"on">Paul Hammer</st1:PersonName> <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, July 05, =
2007 10:34
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Narayan Venkat; =
<st1:PersonName
w:st=3D"on">Caeli Collins</st1:PersonName>; Raj Kumar; <st1:PersonName =
w:st=3D"on">Andrew
 LeFebvre</st1:PersonName>; dl-Executive; dl-eng-ops-staff; dl-Delorean =
Core
Team; Kevin Matthews; dl-Delorean<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Tom Gallivan; =
Sudheesh Nair;
Bob Miller<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Delorean =
Wraup Up
Report</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 id=3DidOWAReplyText77315>

<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>

<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 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 style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Narayan
Venkat<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thu 7/5/2007 10:30 =
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Narayan Venkat; =
<st1:PersonName
w:st=3D"on">Caeli Collins</st1:PersonName>; <st1:PersonName =
w:st=3D"on">Paul Hammer</st1:PersonName>;
Raj Kumar; <st1:PersonName w:st=3D"on">Andrew LeFebvre</st1:PersonName>;
dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews;
dl-Delorean<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Tom Gallivan; =
Sudheesh Nair;
Bob Miller<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Delorean =
Wraup Up
Report</span></font><o:p></o:p></p>

</div>

<div>

<p><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>Folks,<br>
<br>
This issue is still no closed!&nbsp; Who is talking ownership of =
publishing
this document so that customers can see what is officially =
supported?&nbsp; We
cannot continually skirt this issue.&nbsp; We have to get more =
disciplined in
communicating what we officially support.&nbsp; Anybody disagree with =
that?</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>** Not sure who owns it or where we plan to put that info today, =
agree
with the SAG in the future.&nbsp; Have no issue with us providing the =
info.
Need to know how we want to present it and where, QA can provide the =
data
itself.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'><br>
If we are concerned that there are customers who are running with more =
volumes
in their cluster we have to provide a target timeframe for addressing =
the
volume issue.&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2
face=3D"Times New Roman"><span style=3D'font-size:10.0pt'>** 100 volumes =
support is
commited to Zonda. QA is currently testing to define the limits today =
(trying
to get to a configuration that will support up to 50 volumes).<br>
<br>
I am copying Tom and Sudheesh for their comments.<br>
<br>
Thanks.<br>
<br>
Narayan Venkat<br>
Vice President, Marketing<br>
ONStor, Inc.<br>
Tel: (408) 963-2404<br>
Cell: (408) 221-4297.<br>
<br>
<br>
-----Original Message-----<br>
From: Narayan Venkat<br>
Sent: Friday, June 22, 2007 7:51 PM<br>
To: Narayan Venkat; <st1:PersonName w:st=3D"on">Caeli =
Collins</st1:PersonName>; <st1:PersonName
w:st=3D"on">Paul Hammer</st1:PersonName>; Raj Kumar; <st1:PersonName =
w:st=3D"on">Andrew
 LeFebvre</st1:PersonName>; dl-Executive; dl-eng-ops-staff; dl-Delorean =
Core
Team; Kevin Matthews; dl-Delorean<br>
Subject: Re: Delorean Wraup Up Report<br>
<br>
BTW, other vendors provide it in their SAG (NTAP and EMC).<br>
<br>
Narayan Venkat<br>
Tel: (408) 963-2404<br>
Cell: (408) 221-4297<br>
--------------------------<br>
Sent from my BlackBerry Wireless Handheld<br>
<br>
<br>
-----Original Message-----<br>
From: Narayan Venkat<br>
To: <st1:PersonName w:st=3D"on">Caeli Collins</st1:PersonName>; =
<st1:PersonName
w:st=3D"on">Paul Hammer</st1:PersonName>; Narayan Venkat; Raj Kumar; =
<st1:PersonName
w:st=3D"on">Andrew LeFebvre</st1:PersonName>; dl-Executive; =
dl-eng-ops-staff;
dl-Delorean Core Team; Kevin Matthews; dl-Delorean<br>
Sent: Fri Jun 22 19:50:16 2007<br>
Subject: Re: Delorean Wraup Up Report<br>
<br>
Let's put it in the SAG from the next release onwards.&nbsp; For now a =
separate
doc would be sufficient.&nbsp; No need to hold the release up.<br>
<br>
Narayan Venkat<br>
Tel: (408) 963-2404<br>
Cell: (408) 221-4297<br>
--------------------------<br>
Sent from my BlackBerry Wireless Handheld<br>
<br>
<br>
-----Original Message-----<br>
From: <st1:PersonName w:st=3D"on">Caeli Collins</st1:PersonName><br>
To: <st1:PersonName w:st=3D"on">Paul Hammer</st1:PersonName>; Narayan =
Venkat; Raj
Kumar; <st1:PersonName w:st=3D"on">Andrew LeFebvre</st1:PersonName>;
dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews;
dl-Delorean<br>
Sent: Fri Jun 22 19:21:12 2007<br>
Subject: RE: Delorean Wraup Up Report<br>
<br>
um - the SAG is done for Delorean, and we have started burning =
CD's.&nbsp;<br>
<br>
Do you want us to put everything on hold?&nbsp; Do companies put these =
kinds of
limits in a SAG?&nbsp;<br>
<br>
<br>
Caeli<br>
<br>
<br>
<br>
________________________________<br>
<br>
From: <st1:PersonName w:st=3D"on">Paul Hammer</st1:PersonName><br>
Sent: Friday, June 22, 2007 6:53 PM<br>
To: Narayan Venkat; Raj Kumar; <st1:PersonName w:st=3D"on">Andrew =
LeFebvre</st1:PersonName>;
dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews;
dl-Delorean<br>
Subject: RE: Delorean Wraup Up Report<br>
<br>
<br>
I have no issue with taking that approach, solves several problems in =
fact. We
have stayed away from doing this in the past due to the contradiction =
between
tested limits/designed limits and our sales collateral. I like the idea =
of
putting this info here and refreshing them in every release.<br>
<br>
-Paul<br>
<br>
________________________________<br>
<br>
From: Narayan Venkat<br>
Sent: Fri 6/22/2007 6:47 PM<br>
To: <st1:PersonName w:st=3D"on">Paul Hammer</st1:PersonName>; Raj Kumar; =
<st1:PersonName
w:st=3D"on">Andrew LeFebvre</st1:PersonName>; dl-Executive; =
dl-eng-ops-staff;
dl-Delorean Core Team; Kevin Matthews; dl-Delorean<br>
Subject: RE: Delorean Wraup Up Report<br>
<br>
<br>
<br>
I think we should just include this as an addendum to our SAG under a =
section
called &#8220;Tested Limits&#8221;.&nbsp; This way it&#8217;s easy to =
maintain
and we make this part of the release process.&nbsp; In my opinion, the =
customer
visible &#8220;limits&#8221; are should be as follows:<br>
<br>
<br>
<br>
a)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Number of Volumes per head and =
per
cluster<br>
<br>
b)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Size of the Volume/file system =
(with and
without data management)<br>
<br>
c)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max number of VServers per head =
and per
cluster<br>
<br>
d)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max file size<br>
<br>
e)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max number of directories per =
single
directory<br>
<br>
f)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max number of Open =
files<br>
<br>
g)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max TCP connections<br>
<br>
h)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max Virus Scan servers<br>
<br>
i)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max Mirror =
sessions<br>
<br>
j)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max number of LUNs =
per
gateway and cluster<br>
<br>
k)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max shares<br>
<br>
l)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max nodes per =
cluster.<br>
<br>
<br>
<br>
Narayan Venkat<br>
Vice President, Marketing<br>
ONStor, Inc.<br>
Tel: (408) 963-2404<br>
Cell: (408) 221-4297.<br>
<br>
________________________________<br>
<br>
From: <st1:PersonName w:st=3D"on">Paul Hammer</st1:PersonName><br>
Sent: Thursday, June 21, 2007 11:20 PM<br>
To: Narayan Venkat; Raj Kumar; <st1:PersonName w:st=3D"on">Andrew =
LeFebvre</st1:PersonName>;
dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews;
dl-Delorean<br>
Subject: RE: Delorean Wraup Up Report<br>
<br>
<br>
<br>
Agree.<br>
<br>
<br>
<br>
That was an open item when we discussed this previously in the Delorean =
exit ,
who now takes this info from QA testing and puts it in a form that&nbsp; =
is
presentable for use in the field (our sales/SE folks, Partners, =
Resellers,
Customers), is it multiple forms for different needs/audiences? Any
suggestions?<br>
<br>
<br>
<br>
-Paul<br>
<br>
<br>
<br>
________________________________<br>
<br>
From: Narayan Venkat<br>
Sent: Thu 6/21/2007 9:36 PM<br>
To: Raj Kumar; <st1:PersonName w:st=3D"on">Andrew =
LeFebvre</st1:PersonName>;
dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews;
dl-Delorean<br>
Subject: RE: Delorean Wraup Up Report<br>
<br>
Raj,<br>
<br>
<br>
<br>
Who is going to be responsible to publish the limits document?&nbsp; =
This
should be part of the release process.<br>
<br>
<br>
<br>
Thanks.<br>
<br>
<br>
<br>
Narayan<br>
<br>
<br>
<br>
<br>
<br>
________________________________<br>
<br>
From: Raj Kumar<br>
Sent: Thu 6/21/2007 7:44 AM<br>
To: <st1:PersonName w:st=3D"on">Andrew LeFebvre</st1:PersonName>; =
dl-Executive;
dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews; dl-Delorean<br>
Subject: Delorean Wraup Up Report<br>
<br>
Hi,<br>
<br>
<br>
<br>
On behalf of the Delorean team I like to submit the Delorean project =
wrap up
report.<br>
<br>
<br>
<br>
\\mightydog\qe\Projects\delorean\Delorean-Wrap-Up-Report.doc &lt;<a
href=3D"file:///\\mightydog\qe\Projects\delorean\Delorean-Wrap-Up-Report.=
doc">file://mightydog/qe/Projects/delorean/Delorean-Wrap-Up-Report.doc</a=
>&gt;<br>
<br>
<br>
<br>
Thanks.<br>
<br>
<br>
<br>
--kumar :)<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
________________________________<br>
<br>
From: <st1:PersonName w:st=3D"on">Andrew LeFebvre</st1:PersonName><br>
Sent: Thu 6/14/2007 5:10 PM<br>
To: dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; Kevin =
Matthews<br>
Subject: Minutes from 6/14 Delorean FCS Review<br>
<br>
All,<br>
<br>
Thanks to everyone who participated in today&#8217;s Delorean FCS Review =
(Phase
3 Exit)!&nbsp; The unanimous decision is for Delorean to FCS immediately =
and
RTM as soon as the gold master and copies can be created and verified =
(either
tomorrow or on Monday).&nbsp; The GA date and whether or not this is a
mandatory upgrade will be decided by CS and others in the next couple of =
weeks
based on customer uptake and code stability.<br>
<br>
Use the following link to review the presentation material:<br>
<br>
\\mightydog\Program Management\Delorean\Phase Reviews\FCS Review\FCS =
Review
Agenda 6-14-07.ppt &lt;<a
href=3D"file:///\\mightydog\Program%20Management\Delorean\Phase%20Reviews=
\FCS%20Review\FCS%20Review%20Agenda%206-14-07.ppt">file://mightydog/Progr=
am%20Management/Delorean/Phase%20Reviews/FCS%20Review/FCS%20Review%20Agen=
da%206-14-07.ppt</a>&gt;<br>
<br>
Here are the actions/comments I took down.&nbsp;<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; QA
testing of increased numbers of volumes should begin now rather than =
being tied
to the Zonda release.&nbsp; Getting to 50 volumes can be an intermediate
milestone to getting to 100.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Caeli to use EMRS to determine how many customers have volumes greater =
than 32
TB.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
3.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Needs to be some discussion about how best (or if) to package QE limits =
testing
results for SE, CS, Sales, and customers.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
4.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Andy to develop a quantitative metric for commitments vs. deliverables =
that can
be used to compare projects.&nbsp; Share this in the post mortem =
review.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
5.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CS
and SE need to review the Kerberos upgrade procedure documentation and =
let DEV
know if they have any questions or concerns.<br>
<br>
<br>
<br>
Please respond to all on this e-mail if you have any additions or
clarifications.<br>
<br>
<br>
<br>
Regards,<br>
<br>
Andy<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C7BF2D.4D185767--
