Versions Compared

Old Version 29

changes.mady.by.user Amir Shehata

Saved on

compared with

New Version Current

changes.mady.by.user Olaf Weber

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Primary Requirement IDSecondary Requirement IDUnit Test IDUnit Test Description
  dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040UT-DD-CFG-0001
  • turn on lnet discovery
  • run lnetctl discover
  • ensure that peers are discovered
  UT-DD-CFG-0002
  • turn off lnet discovery
  • run lnetctl discover
  • ensure we get some valid error back
  UT-DD-CFG-0003
  • show the status of lnet discovery (if it's on or off)
  UT-DD-CFG-0004
  • Make sure lnet discovery is configurable via YAML
  UT-DD-CFG-0005
  • configure lnet_max_interfaces from command line
  • Show lnet_max_interfces from command line and ensure it's set
  UT-DD-CFG-0006
  • configure lnet_max_interfaces from YAML
  • show lnet_max_interfaces from YAML and ensure it's set
  dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040UT-DD-EN-0001Basic functionality 1-1: discovery of an MR peer via its primary.
  • MR Node with interfaces N1, N2
  • MR Peer with interfaces P1, P2, P3
  • Ping P1 from node
  • Ping P2 from node
  • Verify that node sees two different peers: P1, P2.
  • Discover P1 from node
  • Verify that node sees one MR peer with three NIDS: P1, P2, P3.
  • Verify that peer sees node as one MR peer with two NIDS: N1, N2.
  dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040UT-DD-EN-0002Basic functionality 1-2: discovery of an MR peer via a secondary.
  • MR Node with interfaces N1, N2
  • MR Peer with interfaces P1, P2, P3
  • Ping P1 from node
  • Ping P2 from node
  • Verify that node sees two different peers: P1, P2.
  • Discover P2 from node
  • Verify that node sees one MR peer with three NIDS: P1, P2, P3.
  • Verify that peer sees node as one MR peer with two NIDS: N1, N2.
  UT-DD-EN-0003dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040UT-DD-EN-0003Basic functionality 1-Basic functionality 1-3: discovery of an MR peer via a tertiary.
  • MR Node with interfaces N1, N2
  • MR Peer with interfaces P1, P2, P3
  • Ping P1 from node
  • Ping P2 from node
  • Verify that node sees two different peers: P1, P2.
  • Discover P3 from node
  • Verify that node sees one MR peer with three NIDS: P1, P2, P3.
  • Verify that peer sees node as one MR peer with two NIDS: N1, N2.
dyn-020dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040, dyn-055  UT-DD-EN-0004

Basic functionality 1-4: implicit discovery of an MR peer

  • MR Node with interfaces N1, N2
  • MR Peer with interfaces P1, P2, P3
  • Force some filesystem traffic between node and peer.
  • Verify that node sees one MR peer with three NIDS: P1, P2, P3.
  • Verify that peer sees node as one MR peer with two NIDS: N1, N2.
  dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040UT-DD-EN-0005

Basic functionality 1-5: discovery of an MR peer with > 16 interfaces.

(This test exercises the code path that resizes the push buffers.)

  • MR Node with interfaces N1, N2, ..., N17
  • MR Peer with interfaces P1, P2, ..., P17
  • Ping P1 from node.
  • Discover P1 from node
  • Verify that node sees one MR peer with all NIDS: P1, P2, ..., P17
  • Verify that peer sees node as one MR peer with all NIDS: N1, N2, ..., N17.
  UT-DD-EN-0006dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040UT-DD-EN-0006

Compatibility 2-1: discovery of a non-MR peer via its primary.

  • MR Node with interface N1, N2.
  • Non-MR Peer with interfaces P1, P2, P3.
  • Ping P1 from node.
  • Ping P2 from node.
  • Verify that node sees two different peers: P1, P2.
  • Discover P1 from node
  • Verify that node sees one non-MR peer with three NIDS: P1, P2, P3.
  • Verify that peer sees one as one peer with one NID: N1.
  dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040UT-DD-EN-0007

Compatibility 2-2: discovery of a non-MR peer via a secondary.

  • MR Node with interface N1, N2.
  • Non-MR Peer with interfaces P1, P2, P3.
  • Ping P1 from node.
  • Ping P2 from node.
  • Verify that node sees two different peers: P1, P2.
  • Discover P2 from node
  • Verify that node sees one non-MR peer with three NIDS: P1, P2, P3.
  • Verify that peer sees one as one peer with one NID: N1.
  dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040UT-DD-EN-0008

Compatibility 2-3: discovery of a non-MR peer via a tertiary.

  • MR Node with interface N1, N2.
  • Non-MR Peer with interfaces P1, P2, P3.
  • Ping P1 from node.
  • Ping P2 from node.
  • Verify that node sees two different peers: P1, P2.
  • Discover P3 from node
  • Verify that node sees one non-MR peer with three NIDS: P1, P2, P3.
  • Verify that peer sees one as one peer with one NID: N1.
  UT-DD-EN-0009dyn-020dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040, dyn-055UT-DD-EN-0009

Compatibility 2-4Compatibility 2-4: implicit discovery of an MR peer

  • MR Node with interfaces N1, N2
  • MR Peer with interfaces P1, P2, P3
  • Force some filesystem traffic between node and peer.
  • Verify that node sees one non-MR peer with three NIDS: P1, P2, P3.
  • Verify that peer sees node as one peer with one NID: N1
dyn-060dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040  UT-DD-EN-0010

Interaction with DLC 3-1: DLC overrides Discovery of MR peer

  • MR node with interface N1
  • MR peer with interface P1, P2, P3
  • DLC configure MR peer on node with interfaces P1, P2, P4*.
  • Discover P1 from node.
  • Verify that node sees one MR peer with three NIDS: P1, P2, P4*.
  • Verify presence of error messages on node (error code is -EPERM):
    • Error adding NID P3 to peer P1: -1
    • Error deleting NID P3 from peer P1: -1
dyn-060dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040  UT-DD-EN-0011

Interaction with DLC 3-2: DLC overrides Discovery of non-MR peer

  • MR node with interface N1
  • non-MR peer with interface P1, P2, P3
  • DLC configure non-MR peer on node with interfaces P1, P2, P4*.
  • Discover P1 from node.
  • Verify that node sees one non-MR peer with three NIDS: P1, P2, P4*.
  • Verify presence of error messages on node (error code is -EPERM):
    • Error adding NID P3 to peer P1: -1
    • Error deleting NID P3 from peer P1: -1
dyn-060dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040, dyn-065  UT-DD-EN-0012

Interaction with DLC 3-3: DLC overrides Discovery of MR peer with primary conflict

  • MR node with interface N1
  • MR peer with interface P1, P2, P3
  • DLC configure MR peer on node with interfaces P2, P3, P4*.
  • Discover P2 from node.
  • Verify that node sees one MR peer with three NIDS: P2, P3, P4*.
  • Verify presence of error message on node (error code is -EEXIST):
    • Primary NID error P2 versus P1: -17
    is -EEXIST):
    • Primary NID error P2 versus P1: -17
dyn-060dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040, dyn-065  UT-DD-EN-0013

Interaction with DLC 3-4: DLC overrides Discovery of non-MR peer with primary conflict

  • MR node with interface N1
  • non-MR peer with interface P1, P2, P3
  • DLC configure non-MR peer on node with interfaces P2, P3, P4*.
  • Discover P2 from node.
  • Verify that node sees one MR peer with three NIDS: P2, P3, P4*.
  • Verify presence of error message on node (error code is -EEXIST):
    • Primary NID error P2 versus P1: -17
dyn-060dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040  UT-DD-EN-0014

Interaction with DLC 3-5: "push MR bit" exception to DLC overrides Discovery

  • MR node with interface N1
  • MR peer with interface P1, P2, P3
  • DLC configure non-MR peer on node with interfaces P1, P2, P4*.
  • Discover N1 from peer.
  • Verify that node sees one MR peer with three NIDS: P1, P2, P4*.
  • Verify presence of error message on node (error code is -EEXIST):
    • Push says P1 is Multi-Rail, DLC says not
    • Error adding NID P3 to peer P1: -1
    • Error deleting NID P3 from peer P1: -1
dyn-060dyn-005, dyn-015, dyn-025, dyn-030, dyn-035, dyn-040, dyn-065  UT-DD-EN-0015

Interaction with DLC 3-6: "push MR bit" exception to DLC overrides Discovery

  • MR node with interface N1
  • MR peer with interface P1, P2, P3
  • DLC configure non-MR peer on node with interfaces P2, P3, P4*.
  • Discover N1 from peer.
  • Verify that node sees one MR peer with three NIDS: P2, P3, P4*.
  • Verify presence of error message on node (error code is -EEXIST):
    • Push says P2 is Multi-Rail, DLC says not
    • Primary NID error P2 versus P1: -17

...

Primary Requirement IDSecondary Requirement IDUnit Test IDUnit Test Description
  dyn-005, dyn-025, dyn-030UT-DD-DIS-0001Discovery disabled 4-1: discovery of an MR peer via its primary
  • MR Node with interfaces N1, N2
  • MR Peer with interfaces P1, P2, P3
  • Discovery is disabled on Node
  • Ping P1 from node
  • Ping P2 from node
  • Verify that node sees two different peers: P1, P2.
  • Discover P1 from node
  • Verify that node sees two different peers: P1, P2.
  • Verify that peer sees node as one peer with one NID: N1
  dyn-005, dyn-025, dyn-030UT-DD-DIS-0002Discovery disabled 4-2: discovery of an MR peer via a secondary
  • MR Node with interfaces N1, N2
  • MR Peer with interfaces P1, P2, P3
  • Discovery is disabled on Node
  • Ping P1 from node
  • Ping P2 from node
  • Verify that node sees two different peers: P1, P2.
  • Discover P2 from node
  • Verify that node sees two different peers: P1, P2.
  • Verify that peer sees node as one peer with one NID: N1
  dyn-005, dyn-025, dyn-030UT-DD-DIS-0003Discovery disabled 4-3: discovery of an MR peer via a tertiary.
  • MR Node with interfaces N1, N2
  • MR Peer with interfaces P1, P2, P3
  • Discovery is disabled on Node
  • Ping P1 from node
  • Ping P2 from node
  • Verify that node sees two different peers: P1, P2.
  • Discover P3 from node
  • Verify that node sees three different peers: P1, P2, P3.
  • Verify that peer sees node as one peer with one NID: N1
  dyn-005, dyn-025, dyn-030UT-DD-DIS-0004

Discovery disabled 4-4: implicit discovery of an MR peer

  • MR Node with interfaces N1, N2
  • MR Peer with interfaces P1, P2, P3
  • Discovery is disabled on both Node and Peer
  • Force some filesystem traffic between node and peer.
  • Verify that node sees one peer with one NID: P1.
  • Verify that peer sees node as one peer with one NID: N1.
dyn-020dyn-005, dyn-025, dyn-030, dyn-055  UT-DD-DIS-0005

Discovery disabled 4-5: implicit discovery of an MR peer.

(This test shows that if discovery is enabled on either node or peer, it happens on both.)

  • MR Node with interfaces N1, N2
  • MR Peer with interfaces P1, P2, P3
  • Discovery is disabled on Node
  • Force some filesystem traffic between node and peer.
  • Verify that node sees one MR peer with NIDs: P1, P2, P3
  • Verify that peer sees node as one peer with NIDs: N1, N2.
dyn-020dyn-005, dyn-025, dyn-030, dyn-055  UT-DD-DIS-0006

Discovery disabled 4-6: implicit discovery of an MR peer, > 16 interfaces.

(This test shows that if discovery is enabled on either node or peer, it happens on both, including retries required because buffers need to be extended.)

  • MR Node with interfaces N1, N2, ..., N17
  • MR Peer with interfaces P1, P2, ..., P17
  • Discovery is disabled on Node
  • Force some filesystem traffic between node and peer.
  • Verify that node sees one MR peer with all NIDs: P1, P2, ..., P17
  • Verify that peer sees node as one MR peer with all NIDs: N1, N2. ... , N17.
dyn-060dyn-005, dyn-025, dyn-030  UT-DD-DIS-0007

Disabled with DLC 5-1: DLC overrides Discovery of MR peer

  • MR node with interface N1
  • MR peer with interface P1, P2, P3
  • Discovery is disabled on node.
  • DLC configure MR peer on node with interfaces P1, P2, P4*.
  • Discover P1 from node.
  • Verify that node sees one MR peer with three NIDs: P1, P2, P4*.
  • No error messages should show up.
dyn-060dyn-005, dyn-025, dyn-030  UT-DD-DIS-0008

Disabled with DLC 5-2: DLC overrides Discovery of non-MR peer

  • MR node with interface N1
  • non-MR peer with interface P1, P2, P3
  • Discovery is disabled on node.
  • DLC configure non-MR peer on node with interfaces P1, P2, P4*.
  • Discover P1 from node.
  • Verify that node sees one non-MR peer with three NIDS: P1, P2, P4*.
  • No error messages should show up.
dyn-060dyn-005, dyn-025, dyn-030  UT-DD-DIS-0009

Disabled with DLC 5-3: DLC overrides Discovery of MR peer with primary conflict

  • MR node with interface N1
  • MR peer with interface P1, P2, P3
  • Discovery is disabled on node.
  • DLC configure MR peer on node with interfaces P2, P3, P4*.
  • Discover P2 from node.
  • Verify that node sees one MR peer with three NIDs: P2, P3, P4*.
  • No error messages should show up.
dyn-060dyn-005, dyn-025, dyn-030  UT-DD-DIS-0010

Disabled with DLC 5-4: DLC overrides Discovery of non-MR peer with primary conflict

  • MR node with interface N1
  • non-MR peer with interface P1, P2, P3
  • Discovery is disabled on node.
  • DLC configure non-MR peer on node with interfaces P2, P3, P4*.
  • Discover P2 from node.
  • Verify that node sees one MR peer with three NIDS: P2, P3, P4*.
  • No error messages should show up.
dyn-060dyn-005, dyn-025, dyn-030  UT-DD-DIS-0011

Disabled with DLC 5-5: "push MR bit" exception to DLC overrides Discovery

  • MR node with interface N1
  • MR peer with interface P1, P2, P3
  • Discovery is disabled on node.
  • DLC configure non-MR peer on node with interfaces P1, P2, P4*.
  • Discover N1 from peer.
  • Verify that node sees one MR peer with three NIDS: P1, P2, P4*.
  • Verify presence of error message on node (error code is -EPERM):
    • Push says P1 is Multi-Rail, DLC says not
    • Error adding NID P3 to peer P1: -1
    • Error deleting NID P3 from peer P1: -1
dyn-060dyn-005, dyn-025, dyn-030, dyn-065  UT-DD-DIS-0012

Disabled with DLC 5-6: "push MR bit" exception to DLC overrides Discovery

  • MR node with interface N1
  • MR peer with interface P1, P2, P3
  • Discovery is disabled on node.
  • DLC configure non-MR peer on node with interfaces P2, P3, P4*.
  • Discover N1 from peer.
  • Verify that node sees one MR peer with three NIDS: P2, P3, P4*.
  • Verify presence of error message on node (error code is -EEXIST):
    • Push says P2 is Multi-Rail, DLC says not
    • Primary NID error P2 versus P1: -17

...