https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-16822 Lustre <p>It should be possible to add test cases to <tt>sanity-lnet.sh</tt> that are using IPv6 addresses that are (probably) already being assigned to the test nodes in autotest.</p> <p>As a starting point, a patch that is adding a new <tt>test_0</tt> that is just printing out the interfaces configured in the VM node with <tt>ifconfig</tt> (or new-fangled alternative) would give us useful information and not be harmful in the future.</p> <p>At that point, if the client and MDS/OSS nodes have IPv6 addresses assigned, it should be possible to add subtests that are configuring IPv6 NIDs:</p> <ul class="alternate" type="square"> <li>use <tt>lnetctl</tt> to add IPv6 NIDs to a node</li> <li>use <tt>lnetctl ping</tt> to ping the local and peer NIDs with IPv4 and IPv6 addresses to see all NIDs reported</li> <li>configure and run <tt>lnet selftest</tt> with the IPv6 NIDs</li> <li>etc.</li> <li>unconfigure IPv6 NIDs from the nodes</li> </ul> <p>I suspect that this can be done without any changes to autotest, since <tt>sanity-lnet.sh</tt> is unmounting Lustre anyway, and there should already be enough IPv6 infrastructure on master to test at the LNet level.</p> LU-16822

test IPv6 NIDs in sanity-lnet.sh

Improvement Minor Open Unresolved James A Simmons Andreas Dilger IPv6 Thu, 11 May 2023 19:24:29 +0000 Mon, 8 Jan 2024 17:00:59 +0000 0 6 <p>Chris, since you wrote most of <tt>sanity-lnet.sh</tt> could you please chime in with suggestions on how this could best be done.</p> <p>"James Simmons &lt;jsimmons@infradead.org&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/51818" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/51818</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-16822" title="test IPv6 NIDs in sanity-lnet.sh" class="issue-link" data-issue-key="LU-16822">LU-16822</a> test: collect IP setup<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 819957820eae7d884e04d393c65e6391a947bf4d</p> <p>With my Ubuntu systems I have IPv6 setup so I tried  MGSNID with IPv6 to see how far it would go. Sadly we are using lctl net up which defaults to IPv4. I have to think about a solution.</p> <p>"James Simmons &lt;jsimmons@infradead.org&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/53599" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/53599</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-16822" title="test IPv6 NIDs in sanity-lnet.sh" class="issue-link" data-issue-key="LU-16822">LU-16822</a> tests: Setup IPv6 with fake network device<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: b3bc7d66a7f25280fb90be7e9b2398a3c867c25a</p> <p>Not the final patch. Just a step forward to make IPv6 testing possible.</p> <p>For IPv6 testing with sanity-lnet I created two approaches. One is with patch <a href="https://review.whamcloud.com/c/fs/lustre-release/+/53605" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/53605</a> which allows setting up an NI using a specific IP. The second is reworking lnet_inet_enumerate() to register IPv6 first if available. Then lctl net up with use IPv6 first if available. Both approaches can work but we should discuss which approach to use.</p> <p>James, I'd assume that this "IPv6 first" choice would be a socklnd module option? Otherwise, if this is a build-time change it would introduce compatibility issues for systems being updated when they would not actually need to use IPv6. </p> Related LU-10391 Development Rank 1|i03l73: Rank (Obsolete) 9223372036854775807 Severity