Test Case ID Requirement ID Test Description test_dynamic_nids_06 LU-10360-07 1. Configure an MGS/OSS servers on tcp network and mount them
2. Configure a client node on the tcp441 network
3. Dynamically add a new network to all the servers:
lnetctl net add --net tcp441 --if eth0
4. Mount the client. Client mount should succeed
5. Do a read/write from the client to verify it works.
6. Unmount the client
7. Remove all Lustre modules from the client.test_dynamic_nids_04 LU-10360-06 Setup a file system consistent of:
1 node: MGS/MDS
1 node: OSS should have 2 IP addresses
1 node: Client
Mount the File System and the client
Use only one of the IP addresses on the OSS
Disable the dynamic_nids feature on the MDS but enable it on the client
Write multiple files to the FS
Read back the files and make sure they are correct
unmount the OSS and remove lustre modules
Change the OSS configuration to use the other IP address for NID
load lustre on the OSS and re mount
LS the file system.
the metadata might be cached on the client and the LS could work
Writing to the FS should timeout and fail.test_dynamic_nids_05 LU-10360-06 Setup a file system consistent of:
1 node: MGS/MDS
1 node: OSS should have 2 IP addresses
1 node: Client
Mount the File System and the client
Use only one of the IP addresses on the OSS
Disable the dynamic_nids feature on the client but disable it on the MDS
Write multiple files to the FS
Read back the files and make sure they are correct
unmount the OSS and remove lustre modules
Change the OSS configuration to use the other IP address for NID
load lustre on the OSS and re mount
LS the file system.
the metadata might be cached on the client and the LS could work
Writing to the FS should timeout and fail.test_dynamic_nids_07 LU-10360-08 1. Configure an MGS/OSS servers on tcp network and mount them
2. Configure a client node on the tcp441 network
3. Dynamically add a new network to all the servers:
lnetctl net add --net tcp441 --if eth0
4. Disable dynamic discovery on the client.
5. Mount the client. Client mount should succeed
6. Do a read/write from the client to verify it works.
7. Unmount the client
8. Remove all Lustre modules from the client.test_dynamic_nids_08 LU-10360-09 1. Configure an MGS/OSS servers on tcp network and mount them
2. Disable discovery on the servers.
2. Configure a client node on the tcp441 network
3. Dynamically add a new network to all the servers:
lnetctl net add --net tcp441 --if eth0
4. Mount the client. Client mount should fail
5. Repeat the test once with discovery enabled on the client and once with
discovery disabled on the client.test_dynamic_nids_09 LU-10360-10 1. Configure an MGS/OSS servers on tcp network and mount them
2. Configure a client node on the tcp network
3. Enable debug=-1 on the client.
4. Dynamically add a new network to all the servers:
lnetctl net add --net tcp441 --if eth0
5. sleep for 10 seconds and then capture the log.
6. Search for "dynamic NID entry" from the function mgc_apply_recover_logs().
There should be an entry for each of the servers NIDs on tcp441
7. Dynamicall delete the NID from the servers
lnetctl net del --net tcp441 --if eth0
8. Sleep 10 seconds then capture the log.
9. We should see the updated IR log entry via the message above, and there
shouldn't be any entries for tcp441test_dynamic_nids_01 LU-10360-01 LU-10360-02 On the client and on the MDS
lctl set_param mgc.*.dynamic_nids=1
lctl get_param mgc.*.dynamic_nids
Check the value is 1
On the client and on the MDS
lctl set_param mgc.*.dynamic_nids=0
lctl get_param mgc.*.dynamic_nids
Check the value is 0test_dynamic_nids_02 LU-10360-03 Setup a file system consistent of:
1 node: MGS/MDS
1 node: OSS should have 2 IP addresses
1 node: Client
Mount the File System and the client
Use only one of the IP addresses on the OSS
Enable the dynamic_nids feature on both the MDS and the client
Write multiple files to the FS
Read back the files and make sure they are correct
unmount the OSS and remove lustre modules
Change the OSS configuration to use the other IP address for NID
load lustre on the OSS and re mount
LS the file system.
We should get the exact same list of files
Write more files and read them back.
the write/read operation should succeedtest_dynamic_nids_03 LU-10360-05 Setup a file system consistent of:
1 node: MGS/MDS
1 node: OSS should have 2 IP addresses
1 node: Client
Mount the File System and the client
Use only one of the IP addresses on the OSS
Disable the dynamic_nids feature on both the MDS and the client
Write multiple files to the FS
Read back the files and make sure they are correct
unmount the OSS and remove lustre modules
Change the OSS configuration to use the other IP address for NID
load lustre on the OSS and re mount
LS the file system.
the metadata might be cached on the client and the LS could work
Writing to the FS should timeout and fail.
Overview
Content Tools