Details
-
Improvement
-
Resolution: Fixed
-
Blocker
-
None
-
3
-
9223372036854775807
Description
It should be possible to add test cases to sanity-lnet.sh that are using IPv6 addresses that are (probably) already being assigned to the test nodes in autotest.
As a starting point, a patch that is adding a new test_0 that is just printing out the interfaces configured in the VM node with ifconfig (or new-fangled alternative) would give us useful information and not be harmful in the future.
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:
- use lnetctl to add IPv6 NIDs to a node
- use lnetctl ping to ping the local and peer NIDs with IPv4 and IPv6 addresses to see all NIDs reported
- configure and run lnet selftest with the IPv6 NIDs
- etc.
- unconfigure IPv6 NIDs from the nodes
I suspect that this can be done without any changes to autotest, since sanity-lnet.sh is unmounting Lustre anyway, and there should already be enough IPv6 infrastructure on master to test at the LNet level.