[ofa-general] Re: [PATCH 3/3] osm: QoS - parsing port names

[Ira Weiny]

I actually have a patch series which I am testing right now which adds
switch-map support to opensm.  There are 2 main reasons we (LLNL) want this:

   1) log messages in opensm.log match output from the diags

   2) log messages use nice descriptive strings like

      "SW1 (R 3) ISR9024D"

      which tell the sysadmin that this is Switch 1 Rack 3

   3) I am in the process of using the new event plugin interface to start
      logging port counters to a mysql DB.  (This is going to be a separate
      plugin GPL'ed project so there will be no requirement on mysql to
      opensm.) But in the process it will be nice to be able to have
      descriptive names for switches rather than just the GUIDs

I will send the patch series ASAP.

Thanks,
Ira


On Thu, 25 Oct 2007 07:43:55 -0700
Hal Rosenstock <hrosenstock at xsigo.com> wrote:

> On Thu, 2007-10-25 at 16:36 +0200, Yevgeny Kliteynik wrote:
> > Hal Rosenstock wrote:
> > > On Thu, 2007-10-25 at 14:56 +0200, Yevgeny Kliteynik wrote:
> > >> Sasha Khapyorsky wrote:
> > >>> On 06:49 Wed 24 Oct     , Hal Rosenstock wrote:
> > >>>> On Mon, 2007-10-15 at 12:39 +0200, Sasha Khapyorsky wrote:
> > >>>>> On 10:48 Mon 15 Oct     , Yevgeny Kliteynik wrote:
> > >>>>>>>>  Switches have the NodeDescription filled by FW, and it's usually the
> > >>>>>>>>  same string for all the switches.
> > >>>>>>> It must not be same. Also I suppose that node description can be changed
> > >>>>>>> at least for some managed switches even today.
> > >>>>>>  Come on, man...
> > >>>>>>  How many cluster administrators that you know will actually go and set
> > >>>>>>  NodeDescription on switches???
> > >>>>> I know at least one asked for this.
> > >>>> Perhaps switch_map can be used in conjunction with this like in the
> > >>>> diags ?
> > >>> Hmm, right, switch_map is another example of switch naming, which is
> > >>> useful with diags.
> > >>> Perhaps even more generic - guid to name map? And this will work instead
> > >>> of (or in addition to) node description when specified?
> > >> Can you elaborate on this?
> > >> What exactly is switch_map?
> > > 
> > > See infiniband-diags (ibnetdiscover man page for one).
> > > 
> > >> And why would be need an additional guid-to-anything map if we
> > >> already have node map indexed by guids (or am I missing something)?
> > > 
> > > GUIDs are not the most admin friendly identifiers.
> > 
> > In that case I understand that you probably meant
> > "name to guid" and not "guid to name" map.
> 
> The switch map file is guid to name so that names can be used as
> friendly identifiers for (switch) guids (since their NodeDescriptions
> are not easy to set):
> 
> SWITCH MAP FILE FORMAT
> The switch map is used to specify a user friendly name for switches in
> the output.  GUIDs are used to perform the lookup.
> 
> <guid> "<name>"
> 
> -- Hal
> 
> > 
> > --Yevgeny
> > 
> > > 
> > > -- Hal
> > > 
> > >> -- Yevgeny
> > >>
> > >>> Sasha
> > >>>
> > > 
> >