Purpose

The purpose of this document is to provide the description of the design verification procedure necessary to verify Lustre operation with IPv6 feature. The procedure is not isolated to testing specific Lustre modules but rather Lustre as a complete system. 

Scope

This document covers design verification procedures for an IPv6-only system and a mixed IPv6-IPv4 system with the focus on IPv6 functionality. Testing of IPv4-only system is considered to be regression testing with regard to the IPv6 feature and is not covered by this document. 

Requirements

The requirements for executing this test plan are same as for a regular Lustre system testing with the exception that every node involved in this testing is expected to be able to work with IPv6.

HW Requirements

A pool of server nodes and a pool of client nodes is expected to be available. Exact numbers are TBD

Network Requirements

Each node is expected to have at least two interfaces available for the purpose of LNet configuration. The connection between the nodes should be such that both IPv4 and IPv6 can be supported on every link.

While majority of the testing is projected to use TCP/Ethernet networking, IPv6 with o2ib shall also be tested.

SW Requirements

Exact Lustre SW version to be used is TBD. Linux kernel versions to be used are TBD.

Testing Procedure

Test Case Structure

The test is defined as the combination of the following:

Identifier

Label which uniquely identifies the testcase.

Objective

Description of what the test case is verifying. Ideally refers to a specific requirement from a system design document which is being verified.

Procedure

Describes the test setup and procedure. Level of detail should be sufficient for a test engineer to follow (should not rely on information available to developers only).

Expected Behaviour

Describes how the system is expected to behave when test procedure is executed.

Actual Results

Describes actual results observed when the test case is executed.

Test Cases

IDObjectiveProcedureExpected BehaviourActual ResultsNotes
IPv6.Config.Client.1Configure Lustre Client using only IPv6
  1. Select an IPv6-enabled machine
  2. Install lustre client
  3. Configure the client to use a connected interface which has only IPv6 address configured
  4. Bring up lustre
  5. Execute "lnetctl net show"
  6. Execute "lnetctl ping" of own NID
  1. "lnetctl net show" output should indicate an active NID featuring IPv6 address of the interface configured for use with LNet.
  2. "lnetctl ping" of own NID should be successful


IPv6.Config.Client.2Configure second Lustre Client using only IPv6 and test connectivity between the two clients
  1. Select an IPv6-enabled machine
  2. Install lustre client
  3. Configure the client to use a connected interface which has only IPv6 address configured. 
  4. Execute "ping" to the IPv6 of the other client
  5. Bring up lustre
  6. Execute "lnetctl net show"
  7. Execute "lnetctl ping" of own NID
  8. Execute "lnetctl ping" of the other client's NID
  1. "ping" of the other client's IPv6 address should succeed
  2. "lnetctl net show" output should indicate an active NID featuring IPv6 address of the interface configured for use with LNet.
  3. "lnetctl ping" of own NID should be successful
  4. "lnetctl ping" of the other client's NID should be successful

Assumes that Client.1 and Client.2 are able to reach each other over IPv6 network.
IPv6.Config.Server.1Configure Lustre Server using only IPv6
  1. Select an IPv6-enabled machine
  2. Install lustre server (ok to collocate MDS and OSS)
  3. Configure the server to use a connected interface which has only IPv6 address configured.
  4. Execute "ping" to the IPv6 of a client
  5. Bring up lustre
  6. Execute "lnetctl net show"
  7. Execute "lnetctl ping" of own NID
  8. Execute "lnetctl ping" of the other client's NID