AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080805140937.75b5f43b@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<jonathan.goldick@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#mh/Mailbox/design review	0	BB375AF679D4A34E9CA8DFA650E2B04E0B319EA3@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 5 Aug 2008 14:09:50 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Jonathan Goldick" <jonathan.goldick@onstor.com>
Subject: Re: Addition of new system cmd option for resetting alternate blade
Message-ID: <20080805140950.284f1122@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0B319EA3@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E05DA1EE5@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E09624BF8@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0B319DED@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0B319E5B@onstor-exch02.onstor.net>
	<20080805133257.2eb70c53@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0B319EA3@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Let's talk about this in person because I believe that it deserves
such a discussion.

As for you issuing the tie breaker, if by that you mean that you are
the Chief Architect and as such things travel upwards to you in the
case of ties, then I agree with that.

However I think that your case should be sufficiently convincing that
such an action isn't necessary when you yourself are involved.  But
hopefully a discussion can resolve any disagreement.

Cheers,

a

On Tue, 5 Aug 2008 13:52:13 -0700 "Jonathan Goldick"
<jonathan.goldick@onstor.com> wrote:

> I disagree.  We should stop creating new command verbs that mean the
> same thing.
> 
> A customer is not going to think about needing to reset/halt/reboot a
> board, they identify things by host name.  It is often the case that
> they log into a filer by vsvr name and don't even know which physical
> box they are on.  There is too much opportunity for a customer to log
> into the wrong physical box and halt/reboot something they didn't
> intend to.  The command syntax I gave is unambiguous and doesn't
> require the customer to known anything but the name of the machine
> they want to halt/reboot, and uses commands that are already known to
> them.
> 
> Max's comment about an optional [-n NODENAME] is an improvement over
> my suggestion as it's consistent with the other API(s).
> 
> If this cannot be completed by GA then that's another discussion but
> let's get the UI right the first time.
> 
> 
> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Tuesday, August 05, 2008 1:33 PM
> Cc: dl-Design Review
> Subject: Re: Addition of new system cmd option for resetting alternate
> blade
> 
> This is going way beyond what is a good idea for GA.  system reset
> was a good idea and I think we should stick with that.  I don't want
> this to be part of system reboot at all.  Various options to the
> command to reset and/or halt might be OK but the result is achievable
> with just a reset.  Doing it by node name would be nice but possibly
> a much more significant coding exercise to make smooth.
> 
> The command is not meant to be able to reset the blade you're running
> it on, so there doesn't need to be an argument, does there?
> 
> 
> On Tue, 5 Aug 2008 13:19:34 -0700 "Jonathan Goldick"
> <jonathan.goldick@onstor.com> wrote:
> 
> > You need to think of this like a customer.  They have no idea about
> > what is blade 0 and what is blade 1.
> > What they know is that they want a particular node, which they will
> > know by name, to either halt or reboot.
> > 
> > I would suggest that we use the existing system reboot and halt
> > commands and give them an optional SSC host name.  If the name
> > matches the node you are logged into, or is omitted, it works just
> > like today.  If it's the name of the other blade in the chassis it
> > uses the new functionality.  If it's none of the above we report
> > that this is not supported.
> > 
> > 
> > 
> > _____________________________________________
> > From: Manohar Divate 
> > Sent: Tuesday, August 05, 2008 12:15 PM
> > To: Rendell Fong; Henry Lau; dl-Design Review
> > Subject: RE: Addition of new system cmd option for resetting
> > alternate blade
> > 
> > 1) If more specific like slot/blade 0 or 1
> > Fallowed by 
> > 2) Confirmation Y is a must
> > 3) And only available to privileged level administrator 
> > 
> > _____________________________________________
> > From: Rendell Fong 
> > Sent: Tuesday, August 05, 2008 12:04 PM
> > To: Henry Lau; dl-Design Review
> > Subject: RE: Addition of new system cmd option for resetting
> > alternate blade
> > 
> > Ok, if everyone agrees.
> > 
> > _____________________________________________
> > From: Henry Lau 
> > Sent: Tuesday, August 05, 2008 11:57 AM
> > To: Rendell Fong
> > Subject: RE: Addition of new system cmd option for resetting
> > alternate blade
> > 
> > Hi Rendell,
> > 
> > Can we still use system reboot instead of system reset as they are
> > the same?
> > 
> > Henry
> > 
> > _____________________________________________
> > From: Rendell Fong 
> > Sent: Tuesday, August 05, 2008 11:55 AM
> > To: dl-Design Review
> > Subject: RE: Addition of new system cmd option for resetting
> > alternate blade
> > 
> > Should blade be qualified to avoid potential confusion?  Like
> > "altblade" or "otherblade".
> > Do we need a "-y" option like system reboot?
> > 
> > _____________________________________________
> > From: Sandrine Boulanger 
> > Sent: Tuesday, August 05, 2008 11:50 AM
> > To: Rendell Fong; dl-Design Review
> > Subject: RE: Addition of new system cmd option for resetting
> > alternate blade
> > 
> > I would use an object rather than an option, and replace -s by
> > "blade" or whatever else is meaningful.
> > 
> > _____________________________________________
> > From: Rendell Fong 
> > Sent: Tuesday, August 05, 2008 11:37 AM
> > To: dl-Design Review
> > Subject: Addition of new system cmd option for resetting alternate
> > blade
> > 
> > Hi folks,
> > 
> > I have been requested to add new system command option for Cougar
> > that allows the alternate blade in the chassis to be rebooted.
> > It will reduce the need to power cycle the entire chassis when a
> > blade is hung and unresponsive.
> > 
> > Note that it will only work with changes that BrianS made in the
> > BMFPGA (version 4 or higher).  
> > So the command will check the version and return an error if it
> > cannot be performed as requested.
> > 
> > Use of the "reset -s" option name is rather arbitrary so I am open
> > to renaming it to whatever makes more sense.
> > 
> > The help page describes the command as follows:
> > 
> > NAME
> > 
> >         system reset             Reboots the alternate blade of a
> > NAS Gateway.
> > 
> > SYNOPSIS
> > 
> >         system reset -s
> > 
> > DESCRIPTION
> > 
> >         This command causes a remote system reboot in the other
> > blade of a 6000 series NAS Gateway. 
> >         It is useful when a system reboot cannot be reliably
> > performed from within the blade itself.
> > 
> > SEE ALSO
> > 
> >         system reboot           Reboots the NAS Gateway from the
> > specified compact flash card.
> > 
> > 
> > Thanks,
> > Rendell
