AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20071031142002.7d5e5245@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<ronb@onstor.com>,<jonathan.goldick@onstor.com>,<chris.vandever@onstor.com>,<dl-Customer-Engineering@onstor.com>,<dl-designreview@onstor.com>,<charissa.willard@onstor.com>,<brian.deforest@onstor.com>,<ronb@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#mh/Mailbox/design review	0	BB375AF679D4A34E9CA8DFA650E2B04E0648DF6A@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 31 Oct 2007 14:20:11 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Ron Bhanukitsiri" <ronb@onstor.com>
Cc: "Jonathan Goldick" <jonathan.goldick@onstor.com>, "Chris Vandever"
 <chris.vandever@onstor.com>, "dl-Customer-Engineering"
 <dl-Customer-Engineering@onstor.com>, "dl-Design Review"
 <dl-designreview@onstor.com>, "Charissa Willard"
 <charissa.willard@onstor.com>, "Brian DeForest"
 <brian.deforest@onstor.com>, "Ron Bhanukitsiri" <ronb@onstor.com>
Subject: Re: Hostnames, Filer Names, and Cluster Names... Case Sensitive or
 Not?
Message-ID: <20071031142011.3b4b348e@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0648DF6A@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E03E9A407@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0648DE49@onstor-exch02.onstor.net>
	<20071031133728.74d236bc@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0648DF6A@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

Well, it's a bit different for user/pass, because we aren't the
authority.  So we can let the authentication server in use decide if a
name/pass is acceptable.  But for object names, our software has to
enforce the restrictions both in the UI and at lower levels.  And
obviously our rules can't violate any protocols that come into play.

Cheers,

a

On Wed, 31 Oct 2007 14:13:28 -0700 "Ron Bhanukitsiri" <ronb@onstor.com>
wrote:

> In my opinion, namescase sensitivity is protocol specific.  Another
> instance
> of this other than host name is username.  Username in Windows is case
> insensitive while on unix is case sensitive.
> 
> It seems to me the simple solution is to keep the original name the
> admin
> typed in in the database and let the protocol pick which name they
> want to use?
> 
> Ron B[ee]
> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Wednesday, October 31, 2007 1:37 PM
> To: Jonathan Goldick
> Cc: Chris Vandever; dl-Customer-Engineering; dl-Design Review;
> Charissa Willard; Brian DeForest
> Subject: Re: Hostnames, Filer Names, and Cluster Names... Case
> Sensitive or Not?
> 
> On Wed, 31 Oct 2007 11:58:00 -0700 "Jonathan Goldick"
> <jonathan.goldick@onstor.com> wrote:
> 
> > In SystemX I am planning on host and volume names being case
> > insensitive in all commands, although you can set the names to any
> > variant of case you want.  What this means is that you can create a
> > filer name like FilerHost1 but you cannot then create another called
> > filerhost1.
> > 
> > While the Internet standard for DNS names is case sensitive this is
> > just too confusing to allow.  I strongly believe that we should
> > define rules of acceptable configuration that prevent customers from
> > shooting themselves in the foot...like the customer that deleted the
> > wrong volume last year because one was called vol1 and the other was
> > Vol1.
> 
> Hm, OK, I didn't get this the first time I read it, apologies.
> Assuming that I get it now, however ~:^)  But what it sounds like is
> that we would have case-sticky but case-insensitive names?  I can
> get behind this idea, because it satisfies pretty much all reasonable
> needs. It allows us to "help" the customer not do something dim while
> still allowing them to use case to their own naming style.  I don't
> think anyone really wants two different host, volume or interface
> names that differ only in case, but I'm sure they would want to be
> able to name a volume "CountDracula" and not see "COUNTDRACULA"
> </shiver> or "countdracula" in the NFS exports.  Or in any UI output.
> CIFS users are so used to be being case-abused I'm sure they don't
> care ~:^)
> 
>  
> > _____________________________________________
> > From: Chris Vandever 
> > Sent: Wednesday, October 31, 2007 11:52 AM
> > To: dl-Customer-Engineering; dl-Design Review
> > Cc: Charissa Willard; Brian DeForest
> > Subject: Hostnames, Filer Names, and Cluster Names... Case Sensitive
> > or Not?
> > 
> > We have two ECRs we'd like to get some feedback on:
> > 
> > *	#17831 (Gateway names should be case-insensitive)
> > *	#11325 ("vsvr move -f filername" is case sensitive, "vsvr
> > set vsvrname" is not)
> > 
> > Currently, filer names and cluster names are case sensitive, just
> > like the underlying hostname on which they are based in BSD.  Vsvr
> > names and CIFS share names are case insensitive, and are converted
> > to upper case before they are stored in the cluster database.
> > 
> > Convenience would dictate that filer names and cluster names be case
> > insensitive.  However, that imposes restrictions that do not exist
> > for the underlying hostnames in BSD.  Do we have customers who rely
> > on the names being case sensitive?  What do customers expect?
> > 
> > Thoughts?
> > 
> > ChrisV & Charissa
> > 
