Versions Compared

Old Version 2

changes.mady.by.user Amir Shehata

Saved on

compared with

New Version Current

changes.mady.by.user Amir Shehata

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Repeat the above test twice
  • dynamic nids enabled on the MDS
    • feature should remain disabled.
    • dynamic nids enabled on the client onlyfeature should remain disabled.
    Advanced Tables - CSV Table
    sortColumn1
    Advanced Tables - Table Plus
    columnStyles
    autoNumberSorttrue
    autoNumberallowExporttrue
    PurposeProcedureResult
    test enabling dynamic_nids
    • 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
    		test disabling dynamic_nids
    • On the client and on the MDS
      • lctl set_param mgc.*.dynamic_nids=0
      • lctl get_param mgc.*.dynamic_nids
        • Check the value is 0
    		test OSS changing NID
    • 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 succeed
    		test OSS failover without specifying the list of failover NIDs
    • Setup a file system consistent of:
      • 1 node: MGS/MDS
      • 2 node: OSS each with at least 1 IP address
      • 1 node: Client
    • Mount the File System and the client
      • Ensure you have a shared drive between both OSS nodes
      • setup one OSS as the primary
      • mount the OSS without specifying the failover OSS NID
    • 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 primary OSS and remove lustre modules
    • load the lustre modules on the second OSS and mount the second OSS
    • 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 succeed
    script^dynamic-nids_tp.csv
    		test disabling dynamic nids feature works
    • 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.
    		test asymmetric enablment of dynamic nids feature  disables the feature