[ofa-general] opensm as service - cfg files

[Al Chu]

On Mon, 2008-10-27 at 20:53 +0200, Yevgeny Kliteynik wrote:
> Al Chu wrote:
> > Hey Philippe,
> > 
> > On Mon, 2008-10-27 at 10:40 +0100, Philippe Gregoire wrote:
> >> Al Chu a écrit :
> >>> On Thu, 2008-10-23 at 14:53 +0200, Philippe Gregoire wrote:
> >>>   
> >>>> Hi Yevgeny,
> >>>>
> >>>> Is it possible to write this service so it will be able to manage multiple instances of opensm on the same node, I mean start and stop all instances at the same time or separately.
> >>>> This will be very usefull when you have several Infiniband storage devices connected directly to one node,
> >>>> so you have to run several opensm -g guid processes on this node.
> >>>>
> >>>> It is authorized to have a service that understand parameters like:
> >>>> service start 0x8000010232
> >>>> or 
> >>>> service start ddn12.conf
> >>>>     
> >>> This doesn't sound like that bad of idea, although "what does the user
> >>> expect" is a concern.  My co-worker brought up the simple issue of the
> >>> log files.  Do you automatically pick a different log file to store to,
> >>> or does it store to the same log, or is it the user's responsibility to
> >>> pick a reasonable different log file name in the .conf file?  I have no
> >>> idea what other daemons/init scripts do.
> >>>
> >>> Al
> >>>
> >>>   
> >> init scripts generally execute/source some configuration file located
> >> in /etc/sysconfig/ to set some variables used in the script. These
> >> variables can be used to distinguish pid filename and log filename for
> >> different opensm instances. If these variables are not defined in the
> >> conf file, they should be build from the parameter value e.g :
> >> opensm.log.ddn12 or opensm.pid.ddn12 
> > 
> > My point was should the script automatically handle this, or is it the
> > user's responsibility to set everything up?  As Ira mentioned in a later
> > post, the console port is supposed to be at a known port value so users
> > know what port to connect to.  So is it wise for the script to auto-
> > magically select different different port values for different opensm
> > instances?  Personally I don't think so.
> > 
> > I was initially thinking the init script could take command line
> > arguments that could be passed directly to the init.d scripts.  So for
> > example, you can say:
> > 
> > service opensmd start "--config ddn.conf"
> > service opensmd start "--config lsi.conf"
> 
> But then how would the user be able to check the specific service
> that was launched? I mean, you have "start" command, but what about
> "status" and "stop"?

I didn't think that far.  So maybe it's not that good of an idea in the
end.  I'm just a bit concerned that a service can be launched and may
elect to override our .conf file settings b/c it wants to launch
multiple daemons.

Al

> -- Yevgeny
> 
> > This puts alternate log file names and console port numbers into the
> > responsibility of the user.
> > 
> > Al
> > 
> >>>> Philippe Gregoire
> >>>> CEA/DAM.
> >>>>
> >>>> Yevgeny Kliteynik a écrit :
> >>>>     
> >>>>> Hi Sasha,
> >>>>>
> >>>>> I was just trying to put some order in my head regarding
> >>>>> the use of opensm as service, and I have couple of questions.
> >>>>> Some of them might be dumb, so please bear with me... :)
> >>>>>
> >>>>> 1. OpenSM config file.
> >>>>>    Do we still need opensm/scripts/opensm.conf?
> >>>>>    I think it's not used any more.
> >>>>>
> >>>>> 2. From opensm/scripts/opensm.init.in:
> >>>>>       @sbindir@/opensm -B $OPTIONS > /dev/null
> >>>>>    Is someone setting the $OPTIONS variable? I think it was
> >>>>>    set in the config file in the past, but not now.
> >>>>>
> >>>>> 3. From opensm/scripts/redhat-opensm.init.in:
> >>>>>      CONFIG=@sysconfdir@/sysconfig/opensm.conf
> >>>>>      if [ -f $CONFIG ]; then
> >>>>>      . $CONFIG
> >>>>>      fi
> >>>>>
> >>>>>    From opensm/scripts/opensm.init.in:
> >>>>>      if [[ -s /etc/sysconfig/opensm ]]; then
> >>>>>          . /etc/sysconfig/opensm
> >>>>>      fi
> >>>>>
> >>>>>    If it's not some naming convention, perhaps we should use
> >>>>>    opensm.conf in both cases?
> >>>>>
> >>>>> 4. Logrotate:
> >>>>>    opensm/scripts/opensm.spec.in installs logrotate file as follows:
> >>>>>       install -m 644 scripts/opensm.logrotate $etc/logrotate.d/opensm
> >>>>>    I may be off here, but should the installed file name be opensmd
> >>>>>    to match the service name?
> >>>>>
> >>>>> -- Yevgeny
> >>>>> _______________________________________________
> >>>>> general mailing list
> >>>>> general at lists.openfabrics.org
> >>>>> http://   lists.openfabrics.org/cgi-bin/mailman/listinfo/general
> >>>>>
> >>>>> To unsubscribe, please visit 
> >>>>> http://   openib.org/mailman/listinfo/openib-general
> >>>>>
> >>>>>       
> >>>> _______________________________________________
> >>>> general mailing list
> >>>> general at lists.openfabrics.org
> >>>> http://   lists.openfabrics.org/cgi-bin/mailman/listinfo/general
> >>>>
> >>>> To unsubscribe, please visit http://   openib.org/mailman/listinfo/openib-general
> >>>>
> >>>>     
> >>
> 
> 
-- 
Albert Chu
chu11 at llnl.gov
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory