All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Simmons <jsimmons@infradead.org>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] (no subject)
Date: Mon, 16 Jan 2017 21:02:10 +0000 (GMT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1701162100360.27875@casper.infradead.org> (raw)
In-Reply-To: <67f5b76c-cadb-747b-cb90-b2b40ca30c65@llnl.gov>


> Sounds good to me.  Ideally, lnetctl should be able to do everything
> that lctl could do (plus all of the new features).  Has it reached
> parity?  If not, what else still remains to be done?

No lctl pings and the peer and connection handling is missing. I did
some work to support the missing features in lnetctl and combined with
multi-rail should fill in the gaps. Also we are missing lnetctl ping
but I think multi-rail might fix that. Not 100% sure tho.

> 
> Chris
> 
> On 01/10/2017 12:15 PM, Amir Shehata wrote:
> > lctl usage is kept for backwards compatibility. Eventually, we should be
> > moving to using lnetctl exclusively. Which lustre-release we should do
> > that in, is the question. 2.10?
> > 
> > thanks
> > amir
> > 
> > On 4 January 2017 at 16:16, Di Natale, Giuseppe <dinatale2@llnl.gov
> > <mailto:dinatale2@llnl.gov>> wrote:
> > 
> >     Greetings,
> > 
> >     I am attempting to port the SysV lnet script as part of a transition
> >     to systemd. I ran into the following in lustre/scripts/lnet:
> > 
> >             if [ -x $LUSTRE_LNET_CONFIG_UTILITY -a -f
> >     "$LUSTRE_LNET_CONFIG_FILE" ]; then
> >                     $LUSTRE_LNET_CONFIG_UTILITY lnet configure || exit 1
> >             else
> >                     lctl network up || exit 1
> >             fi
> > 
> >     Can the check for LUSTRE_LNET_CONFIG_UTILITY  (/usr/sbin/lnetctl by
> >     default) be removed so that way lnetctl is used exclusively?
> > 
> >     Thanks,
> >     Giuseppe Di Natale
> > 
> >     _______________________________________________
> >     lustre-devel mailing list
> >     lustre-devel at lists.lustre.org <mailto:lustre-devel@lists.lustre.org>
> >     http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
> >     <http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org>
> > 
> > 
> > 
> > 
> > _______________________________________________
> > lustre-devel mailing list
> > lustre-devel at lists.lustre.org
> > http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
> > 
> 
> _______________________________________________
> lustre-devel mailing list
> lustre-devel at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
> 

  parent reply	other threads:[~2017-01-16 21:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05  0:16 [lustre-devel] (no subject) Di
2017-01-05  1:36 ` [lustre-devel] LUSTRE_LNET_CONFIG_UTILITY in lnet SysV script Christopher J. Morrone
2017-01-10 20:17   ` Amir Shehata
2017-01-10 20:46     ` Amir Shehata
2017-01-10 22:04       ` Christopher J. Morrone
2017-01-16 21:00       ` James Simmons
2017-01-10 20:15 ` [lustre-devel] (no subject) Amir Shehata
2017-01-10 22:06   ` Christopher J. Morrone
2017-01-11  1:08     ` Amir Shehata
2017-01-11  4:18       ` Dilger, Andreas
2017-01-11 23:20         ` Christopher J. Morrone
2017-01-16 21:25           ` James Simmons
2017-01-16 21:05       ` James Simmons
2017-01-16 21:02     ` James Simmons [this message]
2017-01-17 21:32       ` Christopher J. Morrone
2017-01-18 20:10       ` Amir Shehata
  -- strict thread matches above, loose matches on Subject: below --
2018-01-11 17:16 Fabian Huegel
2018-01-11 17:25 ` [lustre-devel] (no subject) Ben Evans
     [not found] <000c01cae6ee$1d4693d0$57d3bb70$@barton@oracle.com>
2010-04-29  1:25 ` [Lustre-devel] " di.wang
2010-04-29  1:49   ` Andreas Dilger
2010-04-29  2:04     ` di.wang
2009-03-27  5:23 sethpn at gmail.com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.20.1701162100360.27875@casper.infradead.org \
    --to=jsimmons@infradead.org \
    --cc=lustre-devel@lists.lustre.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.