X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C77E28.A5C0D1BE@onstor-exch02.onstor.net>; Fri, 13 Apr 2007 17:05:44 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C77E28.A5C0D1BE"
Content-class: urn:content-classes:message
Subject: RE: Delorean upgrade/install fixes/enhancements plan
Date: Fri, 13 Apr 2007 17:05:44 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E03436A0E@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E03436A05@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Delorean upgrade/install fixes/enhancements plan
Thread-Index: Acd+Ja3hr51Ny90tQ8Oepfwwdl+85gAAL9tQAABR3yA=
References: <BB375AF679D4A34E9CA8DFA650E2B04E034369FD@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E03436A05@onstor-exch02.onstor.net>
From: "Tim Gardner" <tim.gardner@onstor.com>
To: "Brian DeForest" <brian.deforest@onstor.com>,
	"Jay Michlin" <jay.michlin@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

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

Development is opposed to the 1 step upgrade.
Although at first glance it appears to be something that would be quick
to do, it actually requires
a bit of thought and engineering. It would also impose additional
testing and have an impact on
pubs and probably also web-ui.
I have discussed this with Jay and have agreed to only make this change
if given adequate time
to properly engineer this change. That means analyze the requirements,
develop a functional
specification, design it, and finally implement it. Such a process would
surely impact both the
Delorean and Cougar schedules. My alternative is to require that
customers follow the
documented install procedure and detect when they have not.=20

Tim

_____________________________________________
From: Brian DeForest=20
Sent: Friday, April 13, 2007 4:58 PM
To: Tim Gardner; Jay Michlin
Cc: Larry Scheer; Andy Sharp
Subject: RE: Delorean upgrade/install fixes/enhancements plan

I think we're almost there.   There is a primary requirement (from
Jerry) we need to consider.   Larry and I discussed this previously. =20

As I understand, this is what you propose:
The upgrade from 2.2.3 to 3.0 a 2 step process:
step 1:  repartition the flash for the new layout
step 2:  do the upgrade
If step 1 is omitted then step 2 returns an error.

If step 1 is performed automatically by 'system upgrade' for a 2.2.3 to
3.0 upgrade, this would meet the 1 step process requirement, and this is
effectively foolproof.

Is there a downside to a 1 step upgrade that automatically does the
partitioning automatically for 2.2.3 -> 3.0 upgrade?
_____________________________________________
From: Tim Gardner=20
Sent: Friday, April 13, 2007 4:45 PM
To: Brian DeForest; Jay Michlin
Cc: Larry Scheer; Andy Sharp
Subject: Delorean upgrade/install fixes/enhancements plan

Based on feedback from the Delorean core team in response to the
install/upgrade proposals presented to the
core team a couple of weeks ago, development is proceeding with the
following plan:

Requirement 1
In order to upgrade to Delorean, a customer will be required to either
install a flash pre-installed with the Delorean
release or first upgrade to 2.2.3 and then upgrade from 2.2.3 to 3.0.
The 2.2.3 release will contain system upgrade fixes and enhancements
that enable release 3.0 to
be successfully installed. Release 2.2.3 will also contain functionality
to repartition the flash to=20
the new layout.

Requirement 2
Release 3.0 will only be supported on the new flash layout.
Pre-installed flashes containing 3.0 will contain the new flash layout.
A customer upgrading from release 2.2.3 to 3.0 will need to change to
the
new flash layout as part of the upgrade procedure.

Development has nearly completed all of the system upgrade changes that
will be part of
2.2.3 and 3.0.=20

A change is being made to system upgrade to restrict installs of release
3.0 and later
to a flash formatted with the new layout. Attempts to install 3.0 to the
old flash layout
will fail and will output a message indicating that the correct install
procedure must be
followed including formatting to the new flash layout.

The flash upgrade script has been modified to format flashes using the
new layout.
The script has a new name (the 512 suffix has been removed).
Andy still needs to update the wiki page that contains the flash upgrade
procedure to reflect the new name.
This script resides in the Delorean release directory. The old script
has been removed.

The pubs department needs to document the procedure for upgrading to
Delorean.
They should work with Larry on this.

Andy/Larry: please review and comment on this plan.

Brian: please present this plan to the Delorean core team and provide
any resulting feedback.

Tim


------_=_NextPart_001_01C77E28.A5C0D1BE
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: Delorean upgrade/install fixes/enhancements plan</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"#000080" SIZE=3D2 FACE=3D"Arial">Development is opposed to the =
1 step upgrade.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Although at first glance it appears to be something that =
would be quick to do, it actually requires</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">a bit of th</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">ought and engineering. It would also impose =
additional testing and have an impact on</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">pubs and probably also web-ui.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">I have discusse</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">d this with Jay and have agreed to only make =
this change if given adequate time</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">to properly engineer this change. That means analyze the =
requirements, develo</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">p a =
functional</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">specification, design it, and finally implement it. Such =
a process would sur</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">e</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">ly impact =
both the</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">Delorean and Cougar schedules. =
My alternative is to require that customers follow the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">document</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">ed</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> install =
procedure and</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">detect =
when they have not.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Tim</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"><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"> 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"> Friday, April 13, 2007 =
4:58 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"> Tim Gardner; Jay =
Michlin<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"> Larry Scheer; Andy =
Sharp<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: Delorean upgrade/install fixes/enhancements =
plan</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">I think we&#8217;re almost =
there.&nbsp;&nbsp; There is a primary requirement (from Jerry) we need =
to consider.&nbsp;&nbsp; Larry and I discussed this previously.&nbsp; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">As I understand, this is what you =
propose:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">The upgrade from 2.2.3 to 3.0 a 2 step =
process:</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">step 1:&nbsp; repartition the =
flash for the new layout</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">step 2:&nbsp; do the upgrade</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">If step 1 is omitted then step 2 returns an =
error.</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"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">If step 1 is performed automatically by &#8216;system =
upgrade&#8217; for a 2.2.3 to 3.0 upgrade, this would meet the 1 step =
process requirement, and this is effectively =
foolproof.</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"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Is there a downside to a 1 step upgrade that =
automatically does the partitioning automatically for 2.2.3 -&gt; 3.0 =
upgrade?</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"> Tim Gardner<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"> Friday, April 13, 2007 =
4:45 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"> Brian DeForest; Jay =
Michlin<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"> Larry Scheer; Andy =
Sharp<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"> Delorean upgrade/install fixes/enhancements =
plan</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">Based on feedback from the Delorean core team in =
response to the install/upgrade proposals presented to =
the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">core =
team a couple of weeks ago, development is proceeding with the following =
plan:</FONT></SPAN></P>

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

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">In order =
to upgrade to Delorean, a customer will be required to either install a =
flash pre-installed with the Delorean</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">release =
or first upgrade to 2.2.3 and then upgrade from 2.2.3 to =
3.0.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
2.2.3 release will contain system upgrade fixes and enhancements that =
enable release 3.0 to</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">be =
successfully installed. Release 2.2.3 will also contain functionality to =
repartition the flash to </FONT></SPAN></P>

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

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

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Release =
3.0 will only be supported on the new flash layout.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Pre-installed flashes containing 3.0 will contain the new =
flash layout.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">A =
customer upgrading from release 2.2.3 to 3.0 will need to change to =
the</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">new =
flash layout as part of the upgrade procedure.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Development has nearly completed all of the system =
upgrade changes that will be part of</FONT></SPAN></P>

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

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">A change =
is being made to system upgrade to restrict installs of release 3.0 and =
later</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">to a =
flash formatted with the new layout. Attempts to install 3.0 to the old =
flash layout</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">will =
fail and will output a message indicating that the correct install =
procedure must be</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">followed =
including formatting to the new flash layout.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
flash upgrade script has been modified to format flashes using the new =
layout.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
script has a new name (the 512 suffix has been =
removed).</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Andy =
still needs to update the wiki page that contains the flash upgrade =
procedure to reflect the new name.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">This =
script resides in the Delorean release directory. The old script has =
been removed.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The pubs =
department needs to document the procedure for upgrading to =
Delorean.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">They =
should work with Larry on this.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Andy/Larry: please review and comment on this =
plan.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Brian: =
please present this plan to the Delorean core team and provide any =
resulting feedback.</FONT></SPAN></P>

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

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

</BODY>
</HTML>
------_=_NextPart_001_01C77E28.A5C0D1BE--
