<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">It's fine to add the lnet-specific functionality from lctl to lnetctl, but we shouldn't remove existing functionality from lctl to avoid breaking scripts that may be using it today. 4+
releases after all of the LNet specific lctl functionality has been added to lnetctl we can start printing deprecation warnings, and after 8+ releases they can be removed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri;color:black">Cheers, Andreas<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri;color:black">-- <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri;color:black">Andreas Dilger<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri;color:black">Lustre Principal Architect<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri;color:black">Intel High Performance Data Division</span><span style="font-size:11.0pt;font-family:Calibri"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">On 2017/01/10, 18:08, "lustre-devel on behalf of Amir Shehata" <<a href="mailto:lustre-devel-bounces@lists.lustre.org">lustre-devel-bounces@lists.lustre.org</a> on behalf of
<a href="mailto:amir.shehata.whamcloud@gmail.com">amir.shehata.whamcloud@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">lnetctl was designed to control LNet only. We have not moved the rest of the lctl functionality. lctl does a lot of other lustre specific functions.
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">The idea was to have lnetctl be only LNet specific, and lctl lustre specific. In essence we are attempting to decouple LNet from lustre. There has been some talk about upstreaming LNet before lustre with all the
work that James Simmons from ORNL is doing.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">thanks<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">amir<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">On 10 January 2017 at 14:06, Christopher J. Morrone <<a href="mailto:morrone2@llnl.gov" target="_blank">morrone2@llnl.gov</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal" style="margin-left:.5in">Sounds good to me. Ideally, lnetctl should be able to do everything<br>
that lctl could do (plus all of the new features). Has it reached<br>
parity? If not, what else still remains to be done?<br>
<br>
Chris<br>
<br>
On 01/10/2017 12:15 PM, Amir Shehata wrote:<br>
> lctl usage is kept for backwards compatibility. Eventually, we should be<br>
> moving to using lnetctl exclusively. Which lustre-release we should do<br>
> that in, is the question. 2.10?<br>
><br>
> thanks<br>
> amir<br>
><br>
> On 4 January 2017 at 16:16, Di Natale, Giuseppe <<a href="mailto:dinatale2@llnl.gov">dinatale2@llnl.gov</a><br>
> <mailto:<a href="mailto:dinatale2@llnl.gov">dinatale2@llnl.gov</a>>> wrote:<br>
><br>
> Greetings,<br>
><br>
> I am attempting to port the SysV lnet script as part of a transition<br>
> to systemd. I ran into the following in lustre/scripts/lnet:<br>
><br>
> if [ -x $LUSTRE_LNET_CONFIG_UTILITY -a -f<br>
> "$LUSTRE_LNET_CONFIG_FILE" ]; then<br>
> $LUSTRE_LNET_CONFIG_UTILITY lnet configure || exit 1<br>
> else<br>
> lctl network up || exit 1<br>
> fi<br>
><br>
> Can the check for LUSTRE_LNET_CONFIG_UTILITY (/usr/sbin/lnetctl by<br>
> default) be removed so that way lnetctl is used exclusively?<br>
><br>
> Thanks,<br>
> Giuseppe Di Natale<br>
><br>
> _______________________________________________<br>
> lustre-devel mailing list<br>
> <a href="mailto:lustre-devel@lists.lustre.org">lustre-devel@lists.lustre.org</a> <mailto:<a href="mailto:lustre-devel@lists.lustre.org">lustre-devel@lists.lustre.org</a>><br>
> <a href="http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org" target="_blank">http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org</a><br>
> <<a href="http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org" target="_blank">http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org</a>><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">><br>
><br>
><br>
><br>
> _______________________________________________<br>
> lustre-devel mailing list<br>
> <a href="mailto:lustre-devel@lists.lustre.org">lustre-devel@lists.lustre.org</a><br>
> <a href="http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org" target="_blank">
http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org</a><br>
><br>
<br>
_______________________________________________<br>
lustre-devel mailing list<br>
<a href="mailto:lustre-devel@lists.lustre.org">lustre-devel@lists.lustre.org</a><br>
<a href="http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org" target="_blank">http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
</div>
</body>
</html>