X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7BF2A.444557D9@onstor-exch02.onstor.net>; Thu, 5 Jul 2007 09:31:05 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Delorean Wraup Up Report
Date: Thu, 5 Jul 2007 09:30:49 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E046A8369@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E034B4991@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Delorean Wraup Up Report
Thread-Index: Aceu4ZySPhf98U60Q7SyVG56mh2nNQFMDQAnAB1GoqwAA5vU4AAoeM5QAAB6t9wAAPG9QAABEtPwAAAGt/cCeg+14A==
X-Priority: 1
Priority: Urgent
Importance: high
References: <BB375AF679D4A34E9CA8DFA650E2B04E034B4991@onstor-exch02.onstor.net>
From: "Narayan Venkat" <narayan.venkat@onstor.com>
To: "Narayan Venkat" <narayan.venkat@onstor.com>,
	"Caeli Collins" <caeli.collins@onstor.com>,
	"Paul Hammer" <paul.hammer@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>

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?

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

I am copying Tom and Sudheesh for their comments.=20

Thanks.

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


-----Original Message-----
From: Narayan Venkat=20
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).=20

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

-----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.=20

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

-----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
=20
Do you want us to put everything on hold?  Do companies put these kinds
of limits in a SAG? =20
=20

Caeli=20

=20

________________________________

From: Paul Hammer=20
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.
=20
-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:

=20

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.

=20

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

________________________________

From: Paul Hammer=20
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

=20

Agree.=20

=20

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?

=20

-Paul

=20

________________________________

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,

=20

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

=20

Thanks.

=20

Narayan

=20

=20

________________________________

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,

=20

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

=20

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

=20

Thanks.

=20

--kumar :)

=20

=20

=20

________________________________

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

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.=20

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

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

	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.=20

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

=20

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

=20

Regards,

Andy

