X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C86758.1B04C3DE@onstor-exch02.onstor.net>; Mon, 4 Feb 2008 11:02:28 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C86758.1B04C3DE"
Content-class: urn:content-classes:message
Subject: RE: Beta Readiness Criteria Document
Date: Mon, 4 Feb 2008 11:02:21 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0812B255@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E080CB04C@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Beta Readiness Criteria Document
Thread-Index: Achmjn+DLSlttRCPTgmahBtOAgSlzwADRZ7CAC5RVEA=
References: <BB375AF679D4A34E9CA8DFA650E2B04E0812AF9A@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E080CB04C@onstor-exch02.onstor.net>
From: "Joshua Goldenhar" <IMCEAEX-_O=ONSTOR_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=JOSHUA+2EGOLDENHAR@onstor.com>
To: "Paul Hammer" <paul.hammer@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>
Cc: "Narayan Venkat" <narayan.venkat@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C86758.1B04C3DE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Responses in-line below..

=20

-Josh=20

Josh Goldenhar=20
Phone: 408 963 2408, Cell: 408 547 7693=20

________________________________

From: Paul Hammer=20
Sent: Sunday, February 03, 2008 12:16 PM
To: Joshua Goldenhar; dl-Cougar
Subject: RE: Beta Readiness Criteria Document

=20

Thanks Josh, very helpful and a good start.

=20

Sandrine is correct, we do not currently have plans/requirements to
increase the number of vsvr's or volumes. Also believe that the >2tb lun
will only be available by FCS, won't make beta.=20

Hmm - OK, did that drop out while I was away? Did it move to keg or is
it off the table all together. I didn't think the lun label stuff would
make Beta, that's why I put it in "desired" instead of required. I
removed the >32 vservers.

=20

Assume where the docs says 2 node cluster it means 2 mother boards and 1
physical chassis. Believe that QA is already testing with a 2 physical
chassis and 4 mother board cfg, Vikas can you confirm?

Yes - I believe we will only be sending out single chassis, dual node
systems.

=20

So for beta it looks like we only require 3 switches and 2 storage
arrays supported (only surprise to me was the absence of Nexsan). This
is good. What is a V100 Pantera? Is this Xyratex?

Yes, the V100 is the Xyratex 5404 storage. No Nexsan in the beta
customers and we want to start de-emphasizing our support for Nexsan
since we will push the V100 as a denser alternative.

=20

Can you let us know what DMA we need qualified (if any) , and with what
tape device?

None - I put NDMP and backup apps in the "desired" section. If we get
any, it's a bonus. NetBackup would probably top the list. LT03 and 04
tape drives. Doc has been updated.

=20

Client support looks good, not sure we need NT (can't recall if we even
support today outside of an AD host), no Mac support?

Mac support is thorny because of the leopard issue. Last I heard we were
considering this an apple problem, not ours to fix, that Apple would be
coming out with a patch. Has that changed?

=20

Thought we discussed DMIP at the team meeting last week and agreed that
we did not have to have this support, although Cougar to Bobcat and vice
a versa is a feasible combination. I am okay with adding it if it will
help with the beta should not be hard to test, don't think there is any
incompatibility between the two. Ditto for vol import.

I'm OK moving DMIP (cougar-Cougar) to "desired" as Sandrine was right
that it is unlikely to be tested. I would like to keep vol import in
required but is this important to test if the LUN label work is NOT
there?

=20

Given our customer base I would think that we may need to require Copper
SFP's support for beta.

Yep.

=20

Josh, are we providing and Pantera's for beta (Cougar with Storage pre
configured), or are we only providing Cougar?

I believe we are only supplying Cougar HW, no storage.

=20

Are we going to require a beta refresh during the beta (forces testing
of upgrade in the field, think that would be a good test)?

I think it's inevitable - I thought I had put system upgrade in must
have but I see it's missing, adding it to the doc.

=20

Post Beta Completion questions (not sure that they belong in the
readiness doc but thought I would ask):

Do we have to retain user data created during the beta?

Nope.

Do we have to retain configuration data created during the beta?

Nope

Do we have to have a way to migrate a cougar from Beta code to
production code?

Hmm - The last discussion I was involved in said we were going to bring
the Beta units back home, that the units that went out for beta would
not be converted to sales - at least not the actual physical units
themselves. I suppose much of the answer to this question lies with
"Will the beta units be complete HW final versions, at final versions of
PROM code?" and if system upgrade works properly. Will have to
investigate.

=20

Thanks,

=20

-Paul

=20

=20

________________________________

From: Joshua Goldenhar
Sent: Sun 2/3/2008 9:59 AM
To: dl-Cougar
Subject: Beta Readiness Criteria Document

First released draft is attached. It will be kept and maintained in:

\\mightydog\Program Management\Cougar\Marketing

-Josh=20

Josh Goldenhar=20
Sr. Dir. Technical Strategy=20
ONStor, Inc. - http://www.onstor.com/=20
joshua.goldenhar@onstor.com=20
Phone: 408 963 2408, Cell: 408 547 7693=20

=20


------_=_NextPart_001_01C86758.1B04C3DE
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=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-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]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 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:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
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.emailstyle17
	{font-family:Arial;
	color:windowtext;}
span.EmailStyle20
	{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=3Dpurple>

<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'>Responses in-line =
below..<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>

<p><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy'>-Josh</span></font><font color=3Dnavy><span =
style=3D'color:navy'>
<o:p></o:p></span></font></p>

<p><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy'>Josh Goldenhar</span></font><font color=3Dnavy><span
style=3D'color:navy'> <br>
</span></font><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'>Phone: 408 963 2408, Cell: 408 547 =
7693</span></font><font
color=3Dnavy><span style=3D'color:navy'> </span></font><o:p></o:p></p>

</div>

<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'> Paul =
Hammer <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Sunday, February =
03, 2008
12:16 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Joshua Goldenhar; =
dl-Cougar<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Beta =
Readiness
Criteria Document</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=3DidOWAReplyText24182>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Thanks Josh, very helpful and a =
good
start.</span></font><o:p></o:p></p>

</div>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Sandrine is correct, we do not currently have
plans/requirements to increase the number of vsvr's or volumes. Also =
believe
that the &gt;2tb lun will only be available by FCS, won't make beta. =
<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'>Hmm &#8211; OK, did that drop out =
while I
was away? Did it move to keg or is it off the table all together. I =
didn&#8217;t
think the lun label stuff would make Beta, that&#8217;s why I put it in =
&#8220;desired&#8221;
instead of required. I removed the &gt;32 =
vservers.<o:p></o:p></span></font></p>

</div>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Assume where the docs says 2 node cluster it means 2 =
mother
boards and 1 physical chassis. Believe that QA is already testing with a =
2
physical chassis and 4 mother board cfg,&nbsp;Vikas can you =
confirm?<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'>Yes &#8211; I believe we will only =
be
sending out single chassis, dual node =
systems.<o:p></o:p></span></font></p>

</div>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>So for beta it looks like we only&nbsp;require&nbsp;3
switches and 2 storage arrays supported (only surprise to me was the =
absence of
Nexsan). This is good. What is a </span></font><font face=3DArial><span
style=3D'font-family:Arial'>V100 Pantera? Is this =
Xyratex?<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'>Yes, the V100 is the Xyratex 5404 =
storage.
No Nexsan in the beta customers and we want to start de-emphasizing our =
support
for Nexsan since we will push the V100 as a denser =
alternative.<o:p></o:p></span></font></p>

</div>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Can you let us know what DMA we need qualified (if =
any) ,
and with what tape device?<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'>None &#8211; I put NDMP and backup =
apps in
the &#8220;desired&#8221; section. If we get any, it&#8217;s a bonus. =
NetBackup
would probably top the list. LT03 and 04 tape drives. Doc has been =
updated.<o:p></o:p></span></font></p>

</div>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Client support looks good, not sure we need NT (can't =
recall
if we even support today outside of an AD host), no Mac =
support?<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'>Mac support is thorny because of =
the
leopard issue. Last I heard we were considering this an apple problem, =
not ours
to fix, that Apple would be coming out with a patch. Has that =
changed?<o:p></o:p></span></font></p>

</div>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thought we discussed DMIP at the team meeting last =
week and
agreed that we did not have to have this support, although&nbsp;Cougar =
to
Bobcat and vice a versa is a feasible combination. </span></font>I am =
okay
with&nbsp;adding it if it will help with the beta&nbsp;should not be =
hard to
test, don't think there is any incompatibility between the two. Ditto =
for vol
import.<o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I&#8217;m OK moving DMIP =
(cougar-Cougar)
to &#8220;desired&#8221; as Sandrine was right that it is unlikely to be
tested. I would like to keep vol import in required but is this =
important to
test if the LUN label work is NOT there?<o:p></o:p></span></font></p>

</div>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Given our customer base I would think that =
we&nbsp;may need
to&nbsp;require Copper SFP's support&nbsp;for =
beta.<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'>Yep.<o:p></o:p></span></font></p>

</div>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Josh, are we providing and Pantera's for beta (Cougar =
with
Storage pre configured), or are we only providing =
Cougar?<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'>I believe we are only supplying =
Cougar HW,
no storage.<o:p></o:p></span></font></p>

</div>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Are we going to require a beta refresh during the =
beta
(forces testing of upgrade in the field, think that would be a good =
test)?<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'>I think it&#8217;s inevitable =
&#8211; I thought
I had put system upgrade in must have but I see it&#8217;s missing, =
adding it
to the doc.<o:p></o:p></span></font></p>

</div>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Post Beta Completion questions (not sure that they =
belong in
the readiness doc but thought I would ask):</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Do we have to retain user data created during the =
beta?<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'>Nope.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Do we have to retain configuration data created =
during the
beta?<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'>Nope<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Do we have to have a way to migrate a cougar from =
Beta code
to production code?<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'>Hmm &#8211; The last discussion I =
was
involved in said we were going to bring the Beta units back home, that =
the
units that went out for beta would not be converted to sales &#8211; at =
least
not the actual physical units themselves. I suppose much of the answer =
to this
question lies with &#8220;Will the beta units be complete HW final =
versions, at
final versions of PROM code?&#8221; and if system upgrade works =
properly. Will
have to investigate.<o:p></o:p></span></font></p>

</div>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks,</span></font><o:p></o:p></p>

</div>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>-Paul</span></font><o:p></o:p></p>

</div>

<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'> Joshua
Goldenhar<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Sun 2/3/2008 9:59 =
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> dl-Cougar<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Beta Readiness =
Criteria
Document</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>First released draft is attached. It will be kept and
maintained in:</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>\\mightydog\Program =
Management\Cougar\Marketing</span></font><o:p></o:p></p>

<p><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>-Josh</span></font>
<o:p></o:p></p>

<p><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Josh
Goldenhar</span></font> <br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Sr.
Dir. Technical Strategy</span></font> <br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>ONStor,
Inc. - <a =
href=3D"http://www.onstor.com/">http://www.onstor.com/</a></span></font>
<br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>joshua.goldenhar@onstor.com<=
/span></font>
<br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Phone:
408 963 2408, Cell: 408 547 7693</span></font> <o:p></o:p></p>

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

</body>

</html>

------_=_NextPart_001_01C86758.1B04C3DE--
