Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://onos-jenkins.onlab.us/job/USECASE_SdnipFunction_onos-1.3/16/

...

Case 102: Loading methods from other Python file - PASS

Case 1: Ping tests between BGP peers and speakers - PASS

  • 1.1 BGP speakers ping peers, expect all tests to succeed - PASS (tick)

Case 2: Check point-to-point intents - PASS

...

- PASS

...

    Case

    ...

    1

    ...

    : Ping

    ...

    • 4.1 Check ping between each host pair - PASS (tick)

    Case 5: Bring down links and check routes/intents - PASS

    ...

    tests

    ...

    Case 6: Bring up links and check routes/intents - PASS

    • 6.1 Bring up the link between sw32 and peer64514 - PASS (tick)
    • 6.2 Check routes installed - PASS (tick)
    • 6.3 Check M2S intents installed - PASS (tick)
    • 6.4 Bring up the link between sw8 and peer64515 - PASS (tick)
    • 6.5 Check routes installed - PASS (tick)
    • 6.6 Check M2S intents installed - PASS (tick)
    • 6.7 Bring up the link between sw28 and peer64516 - PASS (tick)
    • 6.8 Check routes installed - PASS (tick)
    • 6.9 Check M2S intents installed - PASS (tick)
    • 6.10 Check whether all flow status are ADDED - PASS (tick)
    • 6.11 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
    • 6.12 Check ping between each host pair - PASS (tick)

    Case 7: Stop edge sw32,check P-2-P and M-2-S intents, ping test - PASS

    ...

    between BGP peers and speakers

    ...

    -

    ...

    PASS

    • 8. 1 Start sw32 - PASS (tick)
    • 8.2 Check routes installed - PASS (tick)
    • 8.3 Check M2S intents installed - PASS (tick)
    • 8.4 Check P2P intents installed - PASS (tick)
    • 8.5 Check whether all flow status are ADDED - PASS (tick)
    • 8.6 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
    • 8.7 Check ping between each host pair - PASS (tick)

    Case 9: Stop sw11 located in best path, check route number, P2P intent number, M2S intent number, ping test - PASS

    • 9.1 Check flow entry number in sw11 - PASS (tick)
    • 9.2 Check flow entry number in sw1 - PASS (tick)
    • 9.3 Check flow entry number in sw7 - PASS (tick)
    • 9.4 Stop sw11 - PASS (tick)
    • 9.5 Check routes installed - PASS (tick)
    • 9.6 Check M2S intents installed - PASS (tick)
    • 9.7 Check P2P intents installed - PASS (tick)
    • 9.8 Check whether all flow status are ADDED - PASS (tick)
    • 9.9 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
    • 9.10 Check ping between each host pair - PASS (tick)

    Case 10: Start sw11 which was stopped in CASE9, check route number, P2P intent number, M2S intent number, ping test - PASS

    • 10.1 Check flow entry number in sw1 - PASS (tick)
    • 10.2 Check flow entry number in sw7 - PASS (tick)
    • 10.3 Start sw11 - PASS (tick)
    • 10.4 Check routes installed - PASS (tick)
    • 10.5 Check M2S intents installed - PASS (tick)
    • 10.6 Check P2P intents installed - PASS (tick)
    • 10.7 Check whether all flow status are ADDED - PASS (tick)
    • 10.8 BGP speakers ping peers, expect all tests to succeed - PASS (tick) 10.9 Check ping between each host pair - PASS (tick)