X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7BF2B.7DE2BE8B@onstor-exch02.onstor.net>; Thu, 5 Jul 2007 09:39:51 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7BF2B.7DE2BE8B"
Content-class: urn:content-classes:message
Subject: RE: Delorean Wraup Up Report
Date: Thu, 5 Jul 2007 09:39:51 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E046A837F@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+14AAASUWOAAAgYLA=
References: <BB375AF679D4A34E9CA8DFA650E2B04E034B4991@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E046A8369@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E03E568B8@onstor-exch02.onstor.net>
From: "Caeli Collins" <caeli.collins@onstor.com>
To: "Paul Hammer" <paul.hammer@onstor.com>,
	"Narayan Venkat" <narayan.venkat@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_01C7BF2B.7DE2BE8B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Narayan -=20
=20
I thought you and I agreed that if someone gives us what we want to list
in the limits document we will publish it on the wiki, making it
externally viewable.  I someone gives it to me today, we can have it up
immediately.  Do we have the summary?

Caeli=20

=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

________________________________

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>



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>

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_01C7BF2B.7DE2BE8B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=3Dltr><HEAD><TITLE>RE: Delorean Wraup Up Report</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D884593717-05072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Narayan - </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D884593717-05072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D884593717-05072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I thought you and I agreed that if someone =
gives us what we=20
want to list in the limits document we will publish it on the wiki, =
making it=20
externally viewable.&nbsp; I someone gives it to me today, we can have =
it up=20
immediately.&nbsp; Do we have the summary?</FONT></SPAN></DIV><!-- =
Converted from text/rtf format -->
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Caeli</FONT></SPAN> =
</P>
<DIV>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Paul Hammer <BR><B>Sent:</B> =
Thursday,=20
July 05, 2007 10:34 AM<BR><B>To:</B> Narayan Venkat; Caeli Collins; Raj =
Kumar;=20
Andrew LeFebvre; dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; =
Kevin=20
Matthews; dl-Delorean<BR><B>Cc:</B> Tom Gallivan; Sudheesh Nair; Bob=20
Miller<BR><B>Subject:</B> RE: Delorean Wraup Up =
Report<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV id=3DidOWAReplyText77315 dir=3Dltr>
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2></FONT>&nbsp;</DIV></DIV>
<DIV dir=3Dltr><BR>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Narayan Venkat<BR><B>Sent:</B> =
Thu=20
7/5/2007 10:30 AM<BR><B>To:</B> Narayan Venkat; Caeli Collins; Paul =
Hammer; Raj=20
Kumar; Andrew LeFebvre; dl-Executive; dl-eng-ops-staff; dl-Delorean Core =
Team;=20
Kevin Matthews; dl-Delorean<BR><B>Cc:</B> Tom Gallivan; Sudheesh Nair; =
Bob=20
Miller<BR><B>Subject:</B> RE: Delorean Wraup Up =
Report<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=3D2>Folks,<BR><BR>This issue is still no closed!&nbsp; Who =
is=20
talking ownership of publishing this document so that customers can see =
what is=20
officially supported?&nbsp; We cannot continually skirt this =
issue.&nbsp; We=20
have to get more disciplined in communicating what we officially =
support.&nbsp;=20
Anybody disagree with that?</FONT></P><FONT size=3D2></FONT></DIV>
<DIV><FONT size=3D2>** Not sure who owns it or where we plan to put that =
info=20
today, agree with the SAG in the future.&nbsp; Have no issue with us =
providing=20
the info. Need to know how we want to present it and where, QA can =
provide the=20
data itself.</FONT></DIV><FONT size=3D2></FONT><FONT size=3D2>
<DIV><BR>If we are concerned that there are customers who are running =
with more=20
volumes in their cluster we have to provide a target timeframe for =
addressing=20
the volume issue.&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>** 100 volumes support is commited to Zonda. QA is currently =
testing to=20
define the limits today (trying to get to a configuration that will =
support up=20
to 50 volumes).<BR><BR>I am copying Tom and Sudheesh for their=20
comments.<BR><BR>Thanks.<BR><BR>Narayan Venkat<BR>Vice President,=20
Marketing<BR>ONStor, Inc.<BR>Tel: (408) 963-2404<BR>Cell: (408)=20
221-4297.<BR><BR><BR>-----Original Message-----<BR>From: Narayan =
Venkat<BR>Sent:=20
Friday, June 22, 2007 7:51 PM<BR>To: Narayan Venkat; Caeli Collins; Paul =
Hammer;=20
Raj Kumar; Andrew LeFebvre; dl-Executive; dl-eng-ops-staff; dl-Delorean =
Core=20
Team; Kevin Matthews; dl-Delorean<BR>Subject: Re: Delorean Wraup Up=20
Report<BR><BR>BTW, other vendors provide it in their SAG (NTAP and=20
EMC).<BR><BR>Narayan Venkat<BR>Tel: (408) 963-2404<BR>Cell: (408)=20
221-4297<BR>--------------------------<BR>Sent from my BlackBerry =
Wireless=20
Handheld<BR><BR><BR>-----Original Message-----<BR>From: Narayan =
Venkat<BR>To:=20
Caeli Collins; Paul Hammer; Narayan Venkat; Raj Kumar; Andrew LeFebvre;=20
dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews;=20
dl-Delorean<BR>Sent: Fri Jun 22 19:50:16 2007<BR>Subject: Re: Delorean =
Wraup Up=20
Report<BR><BR>Let's put it in the SAG from the next release =
onwards.&nbsp; For=20
now a separate doc would be sufficient.&nbsp; No need to hold the =
release=20
up.<BR><BR>Narayan Venkat<BR>Tel: (408) 963-2404<BR>Cell: (408)=20
221-4297<BR>--------------------------<BR>Sent from my BlackBerry =
Wireless=20
Handheld<BR><BR><BR>-----Original Message-----<BR>From: Caeli =
Collins<BR>To:=20
Paul Hammer; Narayan Venkat; Raj Kumar; Andrew LeFebvre; dl-Executive;=20
dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews; =
dl-Delorean<BR>Sent:=20
Fri Jun 22 19:21:12 2007<BR>Subject: RE: Delorean Wraup Up =
Report<BR><BR>um -=20
the SAG is done for Delorean, and we have started burning =
CD's.&nbsp;<BR><BR>Do=20
you want us to put everything on hold?&nbsp; Do companies put these =
kinds of=20
limits in a=20
SAG?&nbsp;<BR><BR><BR>Caeli<BR><BR><BR><BR>______________________________=
__<BR><BR>From:=20
Paul Hammer<BR>Sent: Friday, June 22, 2007 6:53 PM<BR>To: Narayan =
Venkat; Raj=20
Kumar; Andrew LeFebvre; dl-Executive; dl-eng-ops-staff; dl-Delorean Core =
Team;=20
Kevin Matthews; dl-Delorean<BR>Subject: RE: Delorean Wraup Up=20
Report<BR><BR><BR>I have no issue with taking that approach, solves =
several=20
problems in fact. We have stayed away from doing this in the past due to =
the=20
contradiction between tested limits/designed limits and our sales =
collateral. I=20
like the idea of putting this info here and refreshing them in every=20
release.<BR><BR>-Paul<BR><BR>________________________________<BR><BR>From=
:=20
Narayan Venkat<BR>Sent: Fri 6/22/2007 6:47 PM<BR>To: Paul Hammer; Raj =
Kumar;=20
Andrew LeFebvre; dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; =
Kevin=20
Matthews; dl-Delorean<BR>Subject: RE: Delorean Wraup Up =
Report<BR><BR><BR><BR>I=20
think we should just include this as an addendum to our SAG under a =
section=20
called &#8220;Tested Limits&#8221;.&nbsp; This way it&#8217;s easy to =
maintain and we make this=20
part of the release process.&nbsp; In my opinion, the customer visible =
&#8220;limits&#8221;=20
are should be as =
follows:<BR><BR><BR><BR>a)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Number of Volumes per head and per=20
cluster<BR><BR>b)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Size of the =
Volume/file=20
system (with and without data=20
management)<BR><BR>c)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max number of =
VServers=20
per head and per cluster<BR><BR>d)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Max file=20
size<BR><BR>e)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max number of =
directories per=20
single =
directory<BR><BR>f)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max=20
number of Open files<BR><BR>g)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max =
TCP=20
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=20
sessions<BR><BR>j)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max =
number of=20
LUNs per gateway and =
cluster<BR><BR>k)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max=20
shares<BR><BR>l)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Max =
nodes per=20
cluster.<BR><BR><BR><BR>Narayan Venkat<BR>Vice President, =
Marketing<BR>ONStor,=20
Inc.<BR>Tel: (408) 963-2404<BR>Cell: (408)=20
221-4297.<BR><BR>________________________________<BR><BR>From: Paul=20
Hammer<BR>Sent: Thursday, June 21, 2007 11:20 PM<BR>To: Narayan Venkat; =
Raj=20
Kumar; Andrew LeFebvre; dl-Executive; dl-eng-ops-staff; dl-Delorean Core =
Team;=20
Kevin Matthews; dl-Delorean<BR>Subject: RE: Delorean Wraup Up=20
Report<BR><BR><BR><BR>Agree.<BR><BR><BR><BR>That was an open item when =
we=20
discussed this previously in the Delorean exit , who now takes this info =
from QA=20
testing and puts it in a form that&nbsp; is presentable for use in the =
field=20
(our sales/SE folks, Partners, Resellers, Customers), is it multiple =
forms for=20
different needs/audiences? Any=20
suggestions?<BR><BR><BR><BR>-Paul<BR><BR><BR><BR>________________________=
________<BR><BR>From:=20
Narayan Venkat<BR>Sent: Thu 6/21/2007 9:36 PM<BR>To: Raj Kumar; Andrew =
LeFebvre;=20
dl-Executive; dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews;=20
dl-Delorean<BR>Subject: RE: Delorean Wraup Up=20
Report<BR><BR>Raj,<BR><BR><BR><BR>Who is going to be responsible to =
publish the=20
limits document?&nbsp; This should be part of the release=20
process.<BR><BR><BR><BR>Thanks.<BR><BR><BR><BR>Narayan<BR><BR><BR><BR><BR=
><BR>________________________________<BR><BR>From:=20
Raj Kumar<BR>Sent: Thu 6/21/2007 7:44 AM<BR>To: Andrew LeFebvre; =
dl-Executive;=20
dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews; =
dl-Delorean<BR>Subject:=20
Delorean Wraup Up Report<BR><BR>Hi,<BR><BR><BR><BR>On behalf of the =
Delorean=20
team I like to submit the Delorean project wrap up=20
report.<BR><BR><BR><BR>\\mightydog\qe\Projects\delorean\Delorean-Wrap-Up-=
Report.doc=20
&lt;<A=20
href=3D"file://mightydog/qe/Projects/delorean/Delorean-Wrap-Up-Report.doc=
">file://mightydog/qe/Projects/delorean/Delorean-Wrap-Up-Report.doc</A>&g=
t;<BR><BR><BR><BR>Thanks.<BR><BR><BR><BR>--kumar=20
:)<BR><BR><BR><BR><BR><BR><BR><BR>________________________________<BR><BR=
>From:=20
Andrew LeFebvre<BR>Sent: Thu 6/14/2007 5:10 PM<BR>To: dl-Executive;=20
dl-eng-ops-staff; dl-Delorean Core Team; Kevin Matthews<BR>Subject: =
Minutes from=20
6/14 Delorean FCS Review<BR><BR>All,<BR><BR>Thanks to everyone who =
participated=20
in today&#8217;s Delorean FCS Review (Phase 3 Exit)!&nbsp; The unanimous =
decision is=20
for Delorean to FCS immediately and RTM as soon as the gold master and =
copies=20
can be created and verified (either tomorrow or on Monday).&nbsp; The GA =
date=20
and whether or not this is a mandatory upgrade will be decided by CS and =
others=20
in the next couple of weeks based on customer uptake and code=20
stability.<BR><BR>Use the following link to review the presentation=20
material:<BR><BR>\\mightydog\Program Management\Delorean\Phase =
Reviews\FCS=20
Review\FCS Review Agenda 6-14-07.ppt &lt;<A=20
href=3D"file://mightydog/Program%20Management/Delorean/Phase%20Reviews/FC=
S%20Review/FCS%20Review%20Agenda%206-14-07.ppt">file://mightydog/Program%=
20Management/Delorean/Phase%20Reviews/FCS%20Review/FCS%20Review%20Agenda%=
206-14-07.ppt</A>&gt;<BR><BR>Here=20
are the actions/comments I took=20
down.&nbsp;<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; QA testing of increased numbers of =
volumes=20
should begin now rather than being tied to the Zonda release.&nbsp; =
Getting to=20
50 volumes can be an intermediate milestone to getting to=20
100.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Caeli to use EMRS to determine how many =

customers have volumes greater than 32=20
TB.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
3.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Needs to be some discussion about how =
best (or=20
if) to package QE limits testing results for SE, CS, Sales, and=20
customers.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
4.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Andy to develop a quantitative metric =
for=20
commitments vs. deliverables that can be used to compare projects.&nbsp; =
Share=20
this in the post mortem=20
review.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
5.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CS and SE need to review the Kerberos =
upgrade=20
procedure documentation and let DEV know if they have any questions or=20
concerns.<BR><BR><BR><BR>Please respond to all on this e-mail if you =
have any=20
additions or=20
clarifications.<BR><BR><BR><BR>Regards,<BR><BR>Andy<BR><BR></DIV></FONT><=
/BODY></HTML>

------_=_NextPart_001_01C7BF2B.7DE2BE8B--
