On 20/02/09 12:07 PM, Michael Schuster wrote: > Peter Tribble wrote: >> On Fri, Feb 20, 2009 at 3:24 AM, Michael Schuster >> <Michael.Schuster at sun.com> wrote: >>> I wrote: >>> >>>> This can be done in several ways; we selected to extend the "ilbadm >>>> create-servergroup" subcommand thus: >>>> >>>> ilbadm create-servergroup ... [-n serverID=foo ] .. >>> upon reflection, I'd like to modify this such that serverID comes >>> under the >>> -s option, just like server, eg. >>> >>> ilbadm create-servergroup -s >>> server=10.1.1.1-10.1.1.10,serverID=myservers group1 >>> >>> the same would also apply to "add-server". >> >> So the servers then get names >> >> myservers.1, myservers.2, ..., myservers.10 >> >> is that right? > > yes. > >> What if I then >> >> ilbadm create-servergroup -s >> server=10.1.1.1-10.1.1.10,serverID=myservers group2 >> >> And specify the same name 'myservers' for a different server group? > > if you use "myservers" as a servergroup name, that should be OK, as > the namespaces are distinct. If you implicitly use it as the serverID, > an error should be triggered. > >> How do I specify the name 'fred' to a particular server? (So that one >> back-end server >> is called 'fred', another 'joe', etc. Without the .1, .2, .3 etc >> suffix.) > > we could probably do something with ilbadm add-server to assign just a > name and no suffix.
How about the 'serverID' string being a format string? i.e you set the serverID string like this: -n foo.%i to get ".1", ".2", etc. or if you want no suffix: -n foo or maybe: -n foo.%g.%i to get "foo.group2.2" or -n foo.%a to get "foo.10.1.1.1", etc. Darren
