X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7AA1C.16059969@onstor-exch02.onstor.net>; Fri, 8 Jun 2007 15:26:40 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7AA1C.16059969"
Content-class: urn:content-classes:message
Subject: FW: Update on standalone install script
Date: Fri, 8 Jun 2007 15:26:39 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E040F1043@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Update on standalone install script
Thread-Index: AceqDnWczqcq62rvQ+W8SZkBRuf/ngADY3LA
From: "Brian DeForest" <brian.deforest@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>

This is a multi-part message in MIME format.

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

FYI

_____________________________________________
From: Sandrine Boulanger=20
Sent: Friday, June 08, 2007 1:49 PM
To: dl-Delorean Core Team
Subject: Update on standalone install script

We started all the tests of the install script this morning on all 4
setups:
- single node on 1.2.8.11 (Sandrine)
- cluster on 1.3.3.17 (Brian)
- single node on 2.1.0.4 (May)
- cluster on 2.2.2.7 (John)
Filers are configured with 250 cifs shares.
=20
Here are the defects filed so far, the most critical one is 19489 where
it rebooted by itself to the same flash (maybe bsd crash but we could
not find a proof) before the install was complete.
Some are cosmetic defects, but since it is facing customers I think it's
important that we address them.
=20
TED00019489    cw_install.sh failed to upgrade filer g10r9 (first node
in 2 node cluster)
TED00019482    cw_install.sh needs to have executable permission
TED00019486    Should not prompt prior to reboot if user answered defect
for interactive or unattended mode (from 2.1.0.4)
TED00019490 	Users should not get the "You have successfully
upgraded" message in subsequent logins post upgrade
TED00019491 	Reword second paragraph of the install script
introduction to make it less confusing
=20
Erik B posted the install and tar files on the support site in a hidden
directory and we verified the customer workflow of browsing the onstor
ftp site to get the script and path to the release, using either the
FQDN or the IP address of the ftp site.
=20
For both single node upgrades, May and I found out that vsd was not
restarted after the db was converted to 3.0 (this is a required step
that should happen to have the upgrade really complete), and Chris said
this is similar to the issue she is investigating with the # of shares,
so we updated #19239 (P1).
=20
Brian's mixed cluster (cheetah/bobcat) upgrade from 1.3.3.17 to 3.0
worked fine; he saw vsd restart after the db was upgraded.
=20
For John's cluster (2.2.2.7), since he ran into 19489 the install did
not complete, the cluster is in half upgraded mode. The script can
probably be restarted on g10r9 to complete the upgrade, but we're
waiting to now if DEV needs to collect more info on the filer right now.

We still need to test other workflows and specifics for the script, but
I wanted to send an update of what we've experienced so far.

Note: We've noticed that the script does only one reboot, the final one
that reboots to the secondary flash where 3.0 is installed. It looks
like the recommended first reboot to clear the memory is not done by the
script. We need to know if the user is responsible for running this step
prior to running the script. From the spec review, this step was
supposed to be part of the script.
=20


------_=_NextPart_001_01C7AA1C.16059969
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>FW: Update on standalone install script</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">FYI</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"> 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"> Friday, June 08, 2007 =
1:49 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-Delorean Core Team<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"> Update on standalone install script</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">We started all the tests of =
the install script this morning on all 4 setups:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">- single node on 1.2.8.11 (Sandrine)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">- cluster on 1.3.3.17 (Brian)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">- single node on 2.1.0.4 (May)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">- cluster on 2.2.2.7 (John)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Filers are configured with 250 cifs =
shares.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us">&nbsp;</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">Here are the defects filed so =
far, the most critical one is 19489 where it rebooted by itself to the =
same flash (maybe bsd crash but we could not find a proof) before the =
install was complete.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Some are cosmetic defects, but since it is facing =
customers I think it&#8217;s important that we address =
them.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us">&nbsp;</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">TED00019489 &nbsp;&nbsp; =
cw_install.sh failed to upgrade filer g10r9 (first node in 2 node =
cluster)</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">TED00019482 &nbsp;&nbsp; =
cw_install.sh needs to have executable permission</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">TED00019486 &nbsp;&nbsp; =
Should not prompt prior to reboot if user answered defect for =
interactive or unattended mode (from 2.1.0.4)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">TED00019490 &nbsp;&nbsp;&nbsp; Users should not get the =
&quot;You have successfully upgraded&quot; message in subsequent logins =
post upgrade</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">TED00019491 &nbsp;&nbsp;&nbsp; Reword second paragraph of =
the install script introduction to make it less =
confusing</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us">&nbsp;</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">Erik B posted the install and =
tar files on the support site in a hidden directory and we verified the =
customer workflow of browsing the onstor ftp site to get the script and =
path to the release, using either the FQDN or the IP address of the ftp =
site.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us">&nbsp;</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">For both single node upgrades, =
May and I found out that vsd was not restarted after the db was =
converted to 3.0 (this is a required step that should happen to have the =
upgrade really complete), and Chris said this is similar to the issue =
she is investigating with the # of shares, so we updated #19239 =
(P1).</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us">&nbsp;</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">Brian&#8217;s mixed cluster =
(cheetah/bobcat) upgrade from 1.3.3.17 to 3.0 worked fine; he saw vsd =
restart after the db was upgraded.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us">&nbsp;</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">For John&#8217;s cluster =
(2.2.2.7), since he ran into 19489 the install did not complete, the =
cluster is in half upgraded mode. The script can probably be restarted =
on g10r9 to complete the upgrade, but we&#8217;re waiting to now if DEV =
needs to collect more info on the filer right now.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">We still need to test other workflows and specifics for =
the script, but I wanted to send an update of what we&#8217;ve =
experienced so far.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><I></I></SPAN><SPAN =
LANG=3D"en-us"><I><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Note: =
We&#8217;ve noticed that the script does only one reboot, the final one =
that reboots to the secondary flash where 3.0 is installed. It looks =
like the recommended first reboot to clear the memory is not done by the =
script. We need to know if the user is responsible for running this step =
prior to running the script. From the spec review, this step was =
supposed to be part of the script.</FONT></I></SPAN><SPAN =
LANG=3D"en-us"><I></I></SPAN></P>

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

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

</BODY>
</HTML>
------_=_NextPart_001_01C7AA1C.16059969--
