[ofa-general] Re: [PATCH] opensm/scripts: handling opensm config file

[Doug Ledford]

On Thu, 2008-10-23 at 21:34 +0200, Sasha Khapyorsky wrote:
> Hi Doug,
> 
> On 14:58 Thu 23 Oct     , Doug Ledford wrote:
> > 
> > Well, I don't use the OFED scripts anyway.  They aren't LSB compliant in
> > so many ways it's not worth discussing.  Plus they do things that that
> > should not be done in a production environment, or things that should be
> > handled via other scripts.  So, it's of little importance to me.
> 
> Why to not help us to make it in a proper way? We are discussing this
> right now.

Well, for the most part, because your idea of the "proper way" and my
idea of that are usually two different things.  All the ofed scripts
throw everything, including the kitchen sink, into one big script that
does way more than it should (in fairness, opensm is much better than
the openibd script).  However, as far as requirements I have for the
opensmd init script, they are basically to be LSB compliant (function
names and return codes, as well as operation of the status function and
return codes from the status function), to be clean and easy to read and
understand (as much as is possible anyway), and to not assume things
that aren't safe to assume (the whole copy around the guid2lid file
using ssh is just a broken assumption and gets stripped from my init
scripts).

> > However, if you guys have moved the opensm stuff to /etc/opensm just to
> > have a single opensm.conf file in there, then I have to wonder why
> > bother with an /etc/opensm directory?
> 
> It is not just a single file. In addition to opensm.conf OpenSM by
> default will look in this directory (directory name is configurable btw)
> for partition, route prefixes configuration and QoS policy files.
> 
> > Are there other files in there by
> > default now?
> 
> There are nothing by default, but user may put files there.
> 
> > You don't save any /etc/ directory namespace pollution if
> > you create a subdirectory for a single file. Oh well, that doesn't
> > matter too much to me either.  All the packages I maintain use /etc/ofed
> > for rhel4 and rhel5, and will use /etc/rdma for fedora and rhel6 and
> > later.
> 
> Directory name can be configured if somebody cares. However OpenSM itself
> does not required OFED or RDMA to be installed, we are fine to run in
> stand-alone mode. Then '/etc/opensm' (or actually ${sysconfdir}/opensm)
> looks fine for me.

Of course you require RDMA.  You don't require libibverbs, but
libibverbs != rdma.  InfiniBand/iWARP = rdma hardware.  The point of
the /etc/rdma directory is to be a focal area for rdma hardware related
files, and all of opensm's files certainly qualify as that.  After all,
it's not like opensm manages Cisco VLAN subnets on gigabit ethernet...it
manages IB fabrics and that's it, and they are always RDMA fabrics.

-- 
Doug Ledford <dledford at redhat.com>
              GPG KeyID: CFBFF194
              http://people.redhat.com/dledford

Infiniband specific RPMs available at
              http://people.redhat.com/dledford/Infiniband

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20081024/bafd2c64/attachment.sig>