X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C81AAC.236B1C02@onstor-exch02.onstor.net>; Mon, 29 Oct 2007 21:20:01 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C81AAC.236B1C02"
Content-class: urn:content-classes:message
Subject: RE: Online eek functional spec
Date: Mon, 29 Oct 2007 21:19:59 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0648D413@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0648D3A9@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Online eek functional spec
Thread-Index: AcgWBsLed0cCfFyTS9a1lfbg11LoMAEUeBfAAAFk4AAAAqSygAAAKL2wAAGXlIAAAIocgAAAh0TQAACk1bAABzqmkAABMASgAATigcA=
References: <BB375AF679D4A34E9CA8DFA650E2B04E062AD31F@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E063842D9@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E06384346@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0648D079@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0648D08A@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0648D12B@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0648D144@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0648D17A@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0648D194@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0648D36B@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0648D3A9@onstor-exch02.onstor.net>
From: "Bob Miller" <bob.miller@onstor.com>
To: "Jobi Ariyamannil" <jobi.ariyamannil@onstor.com>
Cc: "dl-Design Review" <dl-designreview@onstor.com>,
	"Sudheesh Nair" <sudheesh.nair@onstor.com>,
	"Eric Barrett" <eric.barrett@onstor.com>,
	"Huy Duong" <huy.duong@onstor.com>,
	"Jonathan Goldick" <jonathan.goldick@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>,
	"Narayan Venkat" <narayan.venkat@onstor.com>,
	"Joshua Goldenhar" <joshua.goldenhar@onstor.com>,
	"Paul Hammer" <paul.hammer@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C81AAC.236B1C02
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I agree with Jobi, especially since we are moving away from BSD. Let's
concentrate on having on line eek as soon as possible.
B

_____________________________________________
From: Jobi Ariyamannil=20
Sent: Monday, October 29, 2007 7:17 PM
To: Jonathan Goldick; Brian DeForest; Narayan Venkat; Joshua Goldenhar
Cc: dl-Design Review; Sudheesh Nair; Eric Barrett; Huy Duong; Bob Miller
Subject: RE: Online eek functional spec


I think nobody has any disagreement promoting eek to nfxsh.  But there
is no reason combining that work with online eek work.
The issues to address for promoting eek to nfxsh are totally different
and nobody had looked at them at all, because nobody strongly requested
for that so far.
Some of the issues I can think of right away - nfxsh must be modified to
handle to large amount of output, make it interactive to answer eek
questions, handle any timeouts due to large eek times, having eek
options/output well documented etc etc.

I think the requirements must be defined early during the release while
reviewing MRD/PRD etc and functional spec reviews must not redefine the
requirements.

It is very easy to list the broken/misbehaved things in our system, but
it is not fair to expect the engineer doing some feature to go and fix
rest of the system.
All enhancements happen incrementally and over time.  We should be smart
enough to prioritize things.
For example, most of our customers are not going to complain about eek
being a BSD root command instead of an nfxsh command.
When their filesystem is corrupt, they don't really care how we invoke
the command.
But a lot of them will be really happy to hear about our online eek
feature.

And they will be happier if our filesystems do not get corrupted or in
the event it gets corrupted, eek fix them correctly.
So guys, let us focus our energy on achieving those instead of these
nfxsh/BSD arguments.

Regards,
Jobi

_____________________________________________
From: Jonathan Goldick=20
Sent: Monday, October 29, 2007 6:26 PM
To: Brian DeForest; Narayan Venkat; Joshua Goldenhar
Cc: dl-Design Review; Sudheesh Nair; Eric Barrett; Huy Duong
Subject: RE: Online eek functional spec

While I agree that this belongs in the design review meeting, I would
expect a CLI command to be created.  EEK is run enough that it should be
made more straightforward than it has been to date.

_____________________________________________
From: Brian DeForest=20
Sent: Monday, October 29, 2007 3:00 PM
To: Narayan Venkat; Joshua Goldenhar; Jonathan Goldick
Cc: dl-Design Review; Sudheesh Nair; Eric Barrett; Huy Duong
Subject: RE: Online eek functional spec

Request input from those on the "To" line.

Is moving eek into nfxsh beyond the scope of the online eek project?
Or should it be added as a new requirement?

_____________________________________________=20
From: 	Brian DeForest =20
Sent:	Monday, October 29, 2007 2:44 PM
To:	Jobi Ariyamannil; Amit Bothra; Sandrine Boulanger; dl-Design
Review
Cc:	Narayan Venkat; Sudheesh Nair; Eric Barrett; Huy Duong
Subject:	RE: Online eek functional spec

Or put another way, moving eek into nfxsh is considered beyond the scope
of the online eek project.  I checked the MRD and promoting eek to nfxsh
isn't a requirement. =20

_____________________________________________=20
From: 	Jobi Ariyamannil =20
Sent:	Monday, October 29, 2007 2:27 PM
To:	Brian DeForest; Amit Bothra; Sandrine Boulanger; dl-Design
Review
Cc:	Narayan Venkat; Sudheesh Nair; Eric Barrett; Huy Duong
Subject:	RE: Online eek functional spec

While this is vague, the difference between new "online" eek and current
"offline" eek is the ability to validate/repair a filesystem while
serving the data.
In long term, we should have self healing built into the filesystem so
that no need of running eek manually.

Adding eek to CLI is a different project. =20

Regards,
Jobi

_____________________________________________
From: Brian DeForest=20
Sent: Monday, October 29, 2007 2:20 PM
To: Jobi Ariyamannil; Amit Bothra; Sandrine Boulanger; dl-Design Review
Cc: Narayan Venkat; Sudheesh Nair; Eric Barrett; Huy Duong
Subject: RE: Online eek functional spec

The issue/question is whether it should be in nfxsh.   If the consensus
is that it doesn't need to be in nfxsh, then the issue is closed.
Maybe others have an opinion.

_____________________________________________=20
From: 	Jobi Ariyamannil =20
Sent:	Monday, October 29, 2007 1:28 PM
To:	Brian DeForest; Amit Bothra; Sandrine Boulanger; dl-Design
Review
Subject:	RE: Online eek functional spec

Eek was never part of nfxsh.  We did not plan to make it part of nfxsh
in R98.
Online eek implemention itself is going to take rest of the R98 time
(Nov 15 feature complete).

Regards,
Jobi

_____________________________________________
From: Brian DeForest=20
Sent: Monday, October 29, 2007 1:21 PM
To: Amit Bothra; Sandrine Boulanger; dl-Design Review
Subject: RE: Online eek functional spec

Maybe I'm missing something, but the incremental time it takes to
implement an admin command vs. diag command is maybe 2 more days at most
-- documentation (1 day) and internal review (1 day).

Additionally, this is a highly requested feature so it presumably should
be exposed as an admin command.

_____________________________________________=20
From: 	Amit Bothra =20
Sent:	Monday, October 29, 2007 12:03 PM
To:	Sandrine Boulanger; dl-Design Review
Subject:	RE: Online eek functional spec

Hi Sandrine,

I agree that its probably nice to have a CLI interface at admin level
for this, but given the time frame its not do-able.

Thanks,
Amit

_____________________________________________
From: Sandrine Boulanger=20
Sent: Monday, October 29, 2007 11:24 AM
To: Amit Bothra; dl-Design Review
Subject: RE: Online eek functional spec

If we want to give customers the ability to run online EEK, shouldn't we
provide a CLI interface at admin level instead of having to login as
root and go to bsd to start online eek?

_____________________________________________
From: Amit Bothra=20
Sent: Tuesday, October 23, 2007 11:26 PM
To: dl-Design Review
Subject: Online eek functional spec

Please review the attached online eek functional specification. Any
feedback is highly appreciated.

Thanks,
Amit

 << File: Online EEK - Func  Spec-v4.doc >>=20

------_=_NextPart_001_01C81AAC.236B1C02
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.7652.24">
<TITLE>RE: Online eek functional spec</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#1F497D" FACE=3D"Calibri">I agree with Jobi, especially since =
we are moving away from BSD. Let</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#1F497D" =
FACE=3D"Calibri">&#8217;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#1F497D" FACE=3D"Calibri">s concentrate =
on</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#1F497D" FACE=3D"Calibri">having on line eek as soon as =
possible.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#1F497D" =
FACE=3D"Calibri">B</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Jobi Ariyamannil<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Monday, October 29, 2007 7:17 PM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Jonathan Goldick; Brian DeForest; Narayan Venkat; =
Joshua Goldenhar<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">Cc:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> dl-Design Review; Sudheesh Nair; Eric Barrett; Huy =
Duong; Bob Miller<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></SPAN></B><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> RE: Online eek functional =
spec</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">I think nobody has any =
disagreement promoting eek to nfxsh.&nbsp; But there is no reason =
combining that work with online eek work.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">The issues to a</FONT><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">ddress for promoting eek to nfxsh are totally different =
and nobody had looked at them at all, because nobody strongly requested =
for that so far.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Some of the issues I can think of right away - nfxsh must =
be modified to handle to large amount of output, make</FONT><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> it interactive to answer eek =
questions, handle any timeouts due to large eek times, having eek =
options/output well documented etc etc.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">I think the requirements must be defined early during the =
release while reviewing MRD/PRD etc and functional spec =
revie</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">ws must not =
redefine the requirements.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">It is very easy to list the broken/misbehaved things in =
our system, but it is not fair to expect the engineer doing some feature =
to go and fix rest of the system.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">All enhancements happen incrementally and over =
time.&nbsp; We should be smart enough to prioritize =
things.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">For example, most of our customers are not going to =
complain about eek being a BSD root command instead of an nfxsh =
command.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">When their filesystem is corr</FONT><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">upt, they don</FONT><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">&#8217;</FONT><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">t really care how we invoke =
the command.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">But a lot of them will be really happy to hear about our =
online eek feature.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">And they will be happier if our filesystems do not get =
corrupted or in the event it gets corrupted, eek fix them =
correctly.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">So guys, let us focus our energy on achieving those =
instead of these nfxsh/BSD arguments.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Jobi</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Jonathan Goldick<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Monday, October 29, 2007 6:26 PM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Brian DeForest; Narayan Venkat; Joshua Goldenhar<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">Cc:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> dl-Design Review; Sudheesh Nair; Eric Barrett; Huy =
Duong<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></SPAN></B><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> RE: Online eek functional =
spec</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">While I agree that this =
belongs in the design review meeting, I would expect a CLI command to be =
created.&nbsp; EEK</FONT> <FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">is run enough that it should be made more straightforward =
than it has been to date.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"></FONT> <FONT SIZE=3D2 =
FACE=3D"Tahoma">Brian DeForest<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Monday, October 29, 2007 =
3:00 PM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Narayan Venkat; Joshua =
Goldenhar;</FONT> <FONT SIZE=3D2 FACE=3D"Tahoma">Jonath</FONT><FONT =
SIZE=3D2 FACE=3D"Tahoma">an Goldick<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Cc:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> dl-Design Review; =
Sudheesh Nair;</FONT> <FONT SIZE=3D2 FACE=3D"Tahoma">Eric Barrett; Huy =
Duong<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> RE: Online eek functional spec</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Request input from those on =
the &quot;To&quot; line.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">Is moving eek into nfxsh beyond the scope of the online =
eek project?&nbsp;&nbsp; Or should it be ad</FONT><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">ded as a new =
requirement?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D1 FACE=3D"Tahoma">_____________________________________________ =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: =
&nbsp;</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D1 FACE=3D"Tahoma">Brian DeForest&nbsp; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Monday, October 29, 2007 2:44 PM</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Jobi Ariyamannil; Amit Bothra; Sandrine Boulanger; =
dl-Design Review</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Narayan Venkat; Sudheesh Nair;</FONT> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Eric Barrett; Huy Duong</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
SIZE=3D1 FACE=3D"Tahoma">RE: Online eek functional =
spec</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Or put another way, moving eek =
into nfxsh is considered beyond the scope of the online eek =
project.&nbsp; I checked the MRD and promoting eek to nfxsh isn't a =
requirement.&nbsp; </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D1 FACE=3D"Tahoma">___________</FONT><FONT SIZE=3D1 =
FACE=3D"Tahoma">__________________________________ </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: =
&nbsp;</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D1 FACE=3D"Tahoma">Jobi Ariyamannil&nbsp; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Monday, October 29, 2007 2:27 PM</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Brian DeForest; Amit Bothra; Sandrine Boulanger; =
dl-Design Review</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Narayan Venkat; Sudheesh Nair;</FONT> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Eric Barrett; Huy Duong</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 FACE=3D"Tahoma">Subjec</FONT><FONT =
SIZE=3D1 =
FACE=3D"Tahoma">t:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B></=
SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D1 =
FACE=3D"Tahoma">RE: Online eek functional spec</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">While this is vague, the =
difference between new &#8220;online&#8221; eek and current =
&#8220;offline&#8221; eek is the ability to validate/repair a filesystem =
while serving the data.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">In long term, we should have self healing built into the =
filesy</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">stem so =
that no need of running eek manually.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Adding eek to CLI is a different project.&nbsp; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Jobi</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"></FONT> <FONT SIZE=3D2 =
FACE=3D"Tahoma">Brian DeForest<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Monday, October 29, 2007 =
2:20 PM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Jobi Ariyamannil; Amit =
Bothr</FONT><FONT SIZE=3D2 FACE=3D"Tahoma">a; Sandrine Boulanger; =
dl-Design Review<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Cc:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Narayan Venkat; Sudheesh =
Nair;</FONT> <FONT SIZE=3D2 FACE=3D"Tahoma">Eric Barrett; Huy Duong<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> RE: Online eek functional spec</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">The issue/question is whether =
it</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">should</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> be in =
nfxsh.&nbsp;&nbsp; If the consensus is that it doesn't need to be in =
n</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">fxsh, then the =
issue is closed.&nbsp;&nbsp; Maybe others have an =
opinion.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D1 FACE=3D"Tahoma">_____________________________________________ =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: =
&nbsp;</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D1 FACE=3D"Tahoma">Jobi Ariyamannil&nbsp; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Monday, October 29, 2007 1:28 PM</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Brian DeForest; Amit Bothra; Sandrine Boulanger; =
dl-Design Review</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
SIZE=3D1 FACE=3D"Tahoma">RE: Online eek functional =
spec</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Eek was never part of =
nfxsh.&nbsp; We did not plan to make it part of nfxsh in =
R98.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Online eek implemention itself is going to take rest of =
the R98 time (Nov 15 feature complete).</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Jobi</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Tahoma">_______________________</FONT><FONT SIZE=3D2 =
FACE=3D"Tahoma">______________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"></FONT> <FONT SIZE=3D2 =
FACE=3D"Tahoma">Brian DeForest<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Monday, October 29, 2007 =
1:21 PM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Amit Bothra; Sandrine =
Boulanger; dl-Design Review<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> RE: Online eek functional spec</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Maybe I'm missing something, =
but the incremental time it takes to i</FONT><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">mplement an admin command vs. diag command is =
maybe 2 more days at most -- documentation (1 day) and internal review =
(1 day).</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">Additionally, this is a highly requested feature so it =
presumably should be exposed as an admin command.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D1 FACE=3D"Tahoma">_______________________</FONT><FONT SIZE=3D1 =
FACE=3D"Tahoma">______________________ </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: =
&nbsp;</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D1 FACE=3D"Tahoma">Amit Bothra&nbsp; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Monday, October 29, 2007 12:03 PM</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Sandrine Boulanger; dl-Design Review</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
SIZE=3D1 FACE=3D"Tahoma">RE: Online eek functional =
spec</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Hi Sandrine,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">I agree that its probably nice to have a CLI interface at =
admin level for t</FONT><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">his, but given the time frame its not =
do-able.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Thanks,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Amit</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Sandrine Boulanger<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Monday, October 29, 2007 =
11:24 AM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Amit Bothra; dl-Design =
Review<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> RE: Online eek functional spec</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">If we want to give customers =
the ability to run online EEK, shouldn</FONT><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">&#8217;</FONT><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">t we provide a CLI interface at admin level instead of =
having to login as root and go to bsd to start online =
eek?</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Amit Bothra<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Tu</FONT><FONT SIZE=3D2 =
FACE=3D"Tahoma">esday, October 23, 2007 11:26 PM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> dl-Design Review<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Online eek functional spec</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">Please review the attached online eek functional =
specification. Any feedback is highly appreciated.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Thanks,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Amit</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Times New =
Roman">&nbsp;&lt;&lt; File: Online EEK - Func&nbsp; Spec-v4.doc =
&gt;&gt;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
</SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C81AAC.236B1C02--
