X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C78783.C08BDF1B@onstor-exch02.onstor.net>; Wed, 25 Apr 2007 14:50:34 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C78783.C08BDF1B"
Content-class: urn:content-classes:message
Subject: RE: Upgrade Procedure for Release Notes
Date: Wed, 25 Apr 2007 14:50:33 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E036D3255@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E02215765@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Upgrade Procedure for Release Notes
Thread-Index: AceHfQZrye5Z59D0SeaD0Oj04OdSKAABCUUg
From: "Jay Michlin" <jay.michlin@onstor.com>
To: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>,
	"Paul Hammer" <paul.hammer@onstor.com>

This is a multi-part message in MIME format.

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

Sandrine,

Here is the current situation:

Larry has built the soft upgrade procedure, requiring first an
intermediate upgrade to a release "2.2.3" and then a second upgrade to
Delorean. This was the initial decision of the core team to accommodate
the needs of Customer Service. It is part of recent submittals.

We also support upgrade from flash (of course). The core team
recommended this for some SE eval installs, in parallel with the soft
approach preferred by CS.

In SW Development we have considered Jerry's dissatisfaction with a two
step upgrade. We determined that we could build a standalone upgrade
program that runs in a single step. But it would have the following
disadvantages:

1. It would take us at least a week just to determine the requirements,
and then at least another week, perhaps two, to develop. The reason is
that the current procedure is highly manual. It has a human reading
output and making decisions at many points. We would have to define and
implement that logic in software, and ti would have to handle the many
combinations of systems in the field.

2. It would be testing-intensive, requiring a potentially large test
matrix with at least a week, and probably longer, to QA.

3. Doing this would necessarily decrease reliability of the product
since any new logic does that. This is not consistent with the
availability initiative.

Jerry has called a meeting to discuss options. Some options are to
install from flash; to install using the system already developed; to do
combinations of these for specific customer subsets; or to delay
Delorean probably at least a month to seek a standalone install program.

I wish we could offer you more definitive direction.

jay


> _____________________________________________=20
> From: 	Larry Scheer =20
> Sent:	Wednesday, April 25, 2007 2:02 PM
> To:	Sandrine Boulanger
> Cc:	dl-Delorean
> Subject:	Upgrade Procedure for Release Notes
>=20
> Sandrine,
>     At the time of this writing the upgrade to Delorean from a
> previous release can take one of several forms. The procedure that
> will be used by customers will be decided sometime in the very near
> future.
>=20
> Attached are two documents. The file named
> SoftwareUpgradeProcedure.pdf is the procedure assuming there is a
> mandatory release (i.e. 2.2.3) that a customer must be at before
> 3.0.0.0 is installed. The document named FlashUpgradeProcedure.pdf is
> the procedure for installing a compact flash preloaded with 3.0.0.0.
>=20
> These are the only procedure I can write about at this time.
>=20
> Please review and give me any feedback or corrections.
>=20
> Thanks, << File: FlashUpgradeProcedure.pdf >>  << File:
> SoftwareUpgradeProcedure.pdf >>=20
>=20
> Larry

------_=_NextPart_001_01C78783.C08BDF1B
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: Upgrade Procedure for Release Notes</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Sandrine,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Here is the current =
situation:</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Larry has built the =
soft upgrade procedure, requiring first an intermediate upgrade to a =
release &quot;2.2.3&quot; and then a second upgrade to Delorean. This =
was the initial decision of the core team to accommodate the needs of =
Customer Service. It is part of recent submittals.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">We also support =
upgrade from flash (of course). The core team recommended this for some =
SE eval installs, in parallel with the soft approach preferred by =
CS.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">In SW Development we =
have considered Jerry's dissatisfaction with a two step upgrade. We =
determined that we could build a standalone upgrade program that runs in =
a single step. But it would have the following disadvantages:</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">1. It would take us =
at least a week just to determine the requirements, and then at least =
another week, perhaps two, to develop. The reason is that the current =
procedure is highly manual. It has a human reading output and making =
decisions at many points. We would have to define and implement that =
logic in software, and ti would have to handle the many combinations of =
systems in the field.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">2. It would be =
testing-intensive, requiring a potentially large test matrix with at =
least a week, and probably longer, to QA.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">3. Doing this would =
necessarily decrease reliability of the product since any new logic does =
that. This is not consistent with the availability =
initiative.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Jerry has called a =
meeting to discuss options. Some options are to install from flash; to =
install using the system already developed; to do combinations of these =
for specific customer subsets; or to delay Delorean probably at least a =
month to seek a standalone install program.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I wish we could offer =
you more definitive direction.</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">jay</FONT>
</P>
<BR>

<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Larry Scheer&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Wednesday, April 25, 2007 2:02 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Sandrine Boulanger</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">dl-Delorean</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">Upgrade Procedure for Release =
Notes</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Sandrine,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp; At the time of this =
writing the upgrade to Delorean from a previous release can take one of =
several forms. The procedure that will be used by customers will be =
decided sometime in the very near future.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Attached are two documents. The file =
named SoftwareUpgradeProcedure.pdf is the procedure assuming there is a =
mandatory release (i.e. 2.2.3) that a customer must be at before 3.0.0.0 =
is installed. The document named FlashUpgradeProcedure.pdf is the =
procedure for installing a compact flash preloaded with =
3.0.0.0.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">These are the only procedure I can =
write about at this time.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Please review and give me any feedback =
or corrections.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks, &lt;&lt; File: =
FlashUpgradeProcedure.pdf &gt;&gt;&nbsp; &lt;&lt; File: =
SoftwareUpgradeProcedure.pdf &gt;&gt; </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Larry</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C78783.C08BDF1B--
