X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8C1F3.DE885AC8@onstor-exch02.onstor.net>; Thu, 29 May 2008 18:24:13 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8C1F3.DE885AC8"
Content-class: urn:content-classes:message
Subject: Minutes from 5/28 Cougar Core Team Meeting
Date: Thu, 29 May 2008 18:24:13 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0A30AA0E@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Minutes from 5/28 Cougar Core Team Meeting
Thread-Index: AcjB896DQBxEomNDQD25xN1Ohpdf8w==
From: "Andrew LeFebvre" <andrew.lefebvre@onstor.com>
To: "dl-Cougar Core Team" <dl-CougarCore@onstor.com>

This is a multi-part message in MIME format.

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

All,

If you missed Wednesday's meeting, then you can see what was presented
by using the following link:
\\mightydog\Program Management\Cougar\Weekly Team
Meetings\05-2008\05-28-2008\Team Meeting Agenda 5-28-08.pps

Attendees: Tim, Vikas, Eugene, Rich, Brian M (partial), Sandrine, Paul
N, Andy S, Larry, John R, Andy

Key decisions and actions from the meeting were as follows:
1)	Brian's HW status highlighted that Max resolved the sequential
read performance issue and now Cougar has close to twice the performance
of Bobcat.  Spec is looking good again as well.  Max is still working on
a write performance problem.
2)	Eugene clarified that the 19 motherboards will be here early
next week and that approximately 8 systems should be ready for lab or
beta use around 6/13.
3)	Eugene also reminded everyone that beta systems must first be
staged in Ops for system testing before they will be shipped to
customers.
4)	Tim commented that Bobcat 3000 is going to require some software
changes from Cougar to account for the name change.  Paul N said Bobcat
3000 is not planned to come out at the same time as Cougar, so the SW
changes need to be taken into account as that project schedule gets put
together.
5)	This week's Submittal 24 is waiting for the fixes for the
sequential read performance problem.
6)	John R said that Mightydog is not ready for 3.3 until they get
all of the backup administrative stuff in place.  He will let the team
know a target day, but it is likely to be sometime next week.
7)	Both Tim and Vikas reported that 3.3 is still having backup
issues.  Several were found on Supersoak over the weekend.  These need
to get resolved before it goes on Mightydog.
8)	However, 3.3 is ready for the SE and CS groups to check out.
Vikas said they should be given Submittal 23.
9)	Vikas and Sandrine do not think 3.3 should be given to LSI and
Lehman until the backup issues are fixed as well as a CIFS triggered
hang that is also in 3.1 and 4.0.
10)	Vikas reported a big spike in defects found last week (around
100).  About half are P1/P2.  Only about 10% are duplicates.

Please feel free to reply back to all with this message if you recall
anything important I may have missed.

Regards,

Andy

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>Minutes from 5/28 Cougar Core Team Meeting</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">All,</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">If =
you missed</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">Wednes</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">day&#8217;s meeting, then you can see what was presented =
by using the following link:</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"></SPAN><A =
HREF=3D"file://\\mightydog\Program Management\Cougar\Weekly Team =
Meetings\05-2008\05-28-2008\Team Meeting Agenda 5-28-08.pps"><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">\\mightydog\Program Management\Cougar\Weekly =
Team Meetings\05-2008\05-28-2008</FONT></U></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">\</FONT></U></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">Team Meeting Agenda =
5-28-08.pps</FONT></U></SPAN><SPAN LANG=3D"en-us"></SPAN></A><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Attendees: Tim, Vikas, Eugene, Rich, Brian =
M</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial"> (partial)</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">, Sandrine, Paul N, Andy S, Larry, John R, =
Andy</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Key =
decisions and actions from the meeting were as =
follows:</FONT></SPAN></P>
<UL>
<OL TYPE=3D1>
<DIV ALIGN=3DLEFT><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Brian</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&#8217;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">s HW status highlighted that</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">Max resolved the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">sequential</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">read performance issue and =
now Cougar has close to twice the performance of =
Bobcat.&nbsp;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">Spec is looking good again =
as well.&nbsp;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">M</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">ax is still working on a write performance =
problem.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></LI></DIV>

<DIV ALIGN=3DLEFT><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Eugene clarified that the 19 motherboards will be here =
early next week and that</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">approximately =
8</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
SIZE=3D2 FACE=3D"Arial">systems should be ready for</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">lab or</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">beta</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">use</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">around 6/13.</FONT></SPAN></LI></DIV>

<DIV ALIGN=3DLEFT><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Eugene also reminded everyone that beta systems must =
first be staged in Ops for system testing before they will be shipped to =
customers.</FONT></SPAN></LI></DIV>

<DIV ALIGN=3DLEFT><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Tim commented that Bobcat 3000 is going to require some =
software changes from Cougar to account for the name =
change.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;<FONT SIZE=3D2 FACE=3D"Arial"> Paul N said Bobcat =
3000 is not planned to come out at the same time as Cougar, so the SW =
changes need to be taken into account as that</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">project schedule gets put together.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></LI></DIV>

<DIV ALIGN=3DLEFT><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">This week</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&#8217;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">s Submittal 24</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">is waiting for</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">the fixes for the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">sequential</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">read</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"> performance problem.</FONT></SPAN></LI></DIV>

<DIV ALIGN=3DLEFT><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">John R said that Mightydog is not ready for 3.3 until =
they get all of the backup</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">administrative stuff</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">in place.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;<FONT SIZE=3D2 FACE=3D"Arial"> He will let the team =
know a target day, but it is likely to be sometime next =
week.</FONT></SPAN></LI></DIV>

<DIV ALIGN=3DLEFT><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Both Tim and Vikas reported that 3.3 is still having =
backup issues.&nbsp; Several were found on Supersoak over the =
weekend.&nbsp; These need to get resolved before it goes on =
Mightydog.</FONT></SPAN></LI></DIV>

<DIV ALIGN=3DLEFT><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">However, 3.3 is ready for the SE and CS groups to check =
out.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;<FONT SIZE=3D2 FACE=3D"Arial"> Vikas said they =
should be given Submittal 23.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></LI></DIV>

<DIV ALIGN=3DLEFT><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Vikas and Sandrine do not think 3.3 should be given to =
LSI and Lehman until the backup issues are fixed as well as a CIFS =
triggered hang that is also in 3.1 and 4.0.</FONT></SPAN></LI></DIV>

<DIV ALIGN=3DLEFT><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Vikas reported a big spike in defects found last week =
(around 100).&nbsp; About half are P1/P2.&nbsp; Only about 10% are =
duplicates.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></LI></DIV>
<BR>
</OL></UL>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Please feel free to reply back to all with this message =
if you recall anything important I may have missed.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Andy</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C8C1F3.DE885AC8--
