X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C895B9.0E4A4110@onstor-exch02.onstor.net>; Thu, 3 Apr 2008 11:32:22 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C895B9.0E4A4110"
Content-class: urn:content-classes:message
Subject: Minutes from 4/1 Cougar Core Team Meeting
Date: Thu, 3 Apr 2008 11:32:21 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0941A88A@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Minutes from 4/1 Cougar Core Team Meeting
Thread-Index: AciVuQ4MgZKDqT+2RcKyP90jRrXgMQ==
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_01C895B9.0E4A4110
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All,

If you missed Tuesday's meeting, then you can see what was presented by
using the following link:
\\mightydog\Program Management\Cougar\Weekly Team
Meetings\04-2008\04-01-2008\Team Meeting Agenda 4-1-08.pps

Attendees: Brian S, Tim, Vikas, Narayan, Dennis, Brian M, Eugene, Paul
N, Paul H, Jonathan, Sandrine, Andy S, Neil, Larry, John R, Andy

Key decisions and actions from the meeting were as follows:
1)	Brian S reported that the 10 REVA motherboards did not come up
because of a design issue, but there is a simple fix.  With this
resolved he is proceeding with the balance of the REVA build (N =3D =
100).
2)	HW data corruption still not to root cause.  QA hasn't yet tried
to reproduce the problem on their systems.  Brian hasn't yet tried to
see if temperature stress can cause it to occur more regularly.
Suggested how best to proceed on this issue be discussed in the
afternoon DEV meeting.
3)	Talked about cluster terminology.  Even though Marketing has put
together their "ONStor Terms and Nomenclature" that we should apply
throughout our documentation, collateral, online help and website,
Narayan does not want to add the effort of making the necessary changes
to the CLI and help text for this initial release.  However, he would
like changes to be made to the documentation where it makes sense to do
so.  Narayan and Dennis will meet to agree on what should be done.
4)	Tim explained they had two submittals last week, so, for those
plans that refer to submittal numbers, take note of the numbering shift.
5)	Feature complete and beta branch is planned for this week's
submittal (Sub16).
6)	Discussed Vikas' updated QA test schedule.  His 4/28 beta test
end date is when QA will be ready for external beta testing to begin.
This is also when they would be ready for a Mightydog beta using Cougar
hardware to begin, which is a change from the previous plan of having
the external beta test run for 2 weeks before we start the Mightydog 4.0
testing.  The 5/29 post beta end date requires approximately 2 more
weeks of testing before QA can assess FCS readiness.  These dates are a
major shift from the previous commitment, so they need to be discussed
in Bob's engineering staff.
7)	Vikas' updated QA test schedule does not show the Bobcat testing
to indicate when QA will be ready to start the Mightydog 3.3 beta.
Vikas and Tim to meet and come up with a target date.
8)	With last Friday's Sub15 QA has moved to opt on all but the NDMP
and DMIP testing.
9)	Soak is running.  DEV asked to see auto support messages, so
Vikas will add dl-Cougar to the send list.
10)	Jonathan commented that we need to clean up the e-log messages
and fix the errors, so both QA and DEV need to begin to file defects for
these.
11)	Brian M asked Narayan when Cougar qualification for XIV and
Fujitsu would need to be completed.  Narayan said they can be post GA.

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

Regards,

Andy


------_=_NextPart_001_01C895B9.0E4A4110
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 4/1 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 Tuesday&#8217;s meeting, then you can see what was presented =
by using the following link:</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"></SPAN><A =
HREF=3D"file://\\mightydog\Program Management\Cougar\Weekly Team =
Meetings\04-2008\04-01-2008\Team Meeting Agenda 4-1-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\04-2008\04-01-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 =
4-1-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: Brian S, Tim, Vikas, Narayan, Dennis, Brian M, =
Eugene, Paul N, Paul H, Jonathan, Sandrine, Andy S, =
Neil,</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Arial">Larry, John R,</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">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 S reported that</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">the 10 REVA motherboards did not come =
up</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
SIZE=3D2 FACE=3D"Arial">because</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"> of a design issue, but there is a simple =
fix.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;<FONT SIZE=3D2 FACE=3D"Arial"> With this resolved =
he is proceeding with</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">the balance of the REVA =
build (N =3D 100).</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">HW data corruption</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">still</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">not to root =
cause.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;<FONT SIZE=3D2 FACE=3D"Arial"> QA =
hasn</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">t yet tried to reproduce the problem on their =
systems.&nbsp; Brian hasn</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">t yet tried to see if temperature stress can cause it to =
occur more regularly.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;<FONT SIZE=3D2 FACE=3D"Arial"> =
Suggested</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Arial">how best to proceed on</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">this</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">issue</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">be discussed in the afternoon DEV =
meeting.</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">Talked about</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">cluster terminology.&nbsp; Even though Marketing =
has</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
SIZE=3D2 FACE=3D"Arial">put together</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">their</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">&#8220;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">ONStor Terms and Nomenclature</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&#8221;</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">that we should apply throughout our documentation, =
collateral, online help and website</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">, Narayan does not want to add the =
effort</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Arial">of making the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">necessary</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">changes</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">to the CLI and help text =
for this initial release.&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">However,</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"> he would like changes to =
be made to the documentation where it makes sense to do =
so.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;<FONT SIZE=3D2 FACE=3D"Arial"> Narayan and Dennis =
will meet to agree on what should be done.</FONT></SPAN></LI></DIV>

<DIV ALIGN=3DLEFT><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Tim explained they ha</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">d two submittals last week,</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">so</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">, for</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">those</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">plan</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">s that refer to submittal numbers,</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">take note of the numbering shift.</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">Feature complete and beta branch</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">is</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">planned =
for</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
SIZE=3D2 FACE=3D"Arial">this</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"> 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 (Sub16).</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">Discussed Vikas</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"> updated QA test =
schedule.&nbsp; His 4/28 beta test end date is when QA will be ready for =
external beta testing to begin.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp; This</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">is also when they would be ready for a Mightydog beta =
using Cougar hardware to begin, which is a change from the previous plan =
of having the external beta test run for 2 weeks before we start the =
Mightydog 4.0 testing.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;<FONT SIZE=3D2 FACE=3D"Arial"> The 5/29 post beta =
end date</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Arial">requires approximately 2 more weeks of =
testing before QA</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">can</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">assess FCS readiness.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp; These dates</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">are a major shift from the previous commitment, so =
they</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Arial">need to be discussed</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">in Bob</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 engineering staff.</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</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"> updated QA test schedule does not show the Bobcat =
testing to indicate when QA will be ready to start</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">the</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">Mightydog 3.3 =
beta.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; Vikas and Tim to =
meet and come up with a target date.</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">With last Friday</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 Sub15</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">QA has moved to opt on all but the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"> NDMP and DMIP testing.</FONT></SPAN></LI></DIV>

<DIV ALIGN=3DLEFT><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Soak is running.&nbsp; DEV asked to =
see</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
SIZE=3D2 FACE=3D"Arial">auto support messages, so Vikas will add =
dl-Cougar to the send list.</FONT></SPAN></LI></DIV>

<DIV ALIGN=3DLEFT><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Jonathan commented that we need to clean up the e-log =
messages and fix the errors, so both QA and DEV need to begin to file =
defects for these.</FONT></SPAN></LI></DIV>

<DIV ALIGN=3DLEFT><LI><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Brian M asked Narayan when Cougar =
qualification</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">for XIV and Fujitsu would =
need to be completed.&nbsp; Narayan said th</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">ey</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">can be post =
GA.</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></P>

</BODY>
</HTML>
------_=_NextPart_001_01C895B9.0E4A4110--
