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_fsfw/284/

...

commit fc4ef00d9dd109a422144e1f4dd29441c846790a (HEAD, origin/onos-1.6, onos-1.6)
Author: Thomas Vachuska [tom@onlab.us]
AuthorDate: Tue May 31 17:59:59 2016 -0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Wed Jun 1 01:20:12 2016 +0000

Fixing javadocs.

Case 101: Setting up ONOS environment - PASS

  • 101.1 Copying config files - PASS (tick)
  • 101.2 Create cell file - No Result (warning)
  • 101.3 Applying cell variable to environment - PASS (tick)
  • 101.4 Verify cell connectivity - PASS (tick)
  • 101.5 Creating ONOS package - PASS (tick)
  • 101.6 Installing ONOS package - PASS (tick)
  • 101.7 Checking if ONOS is up yet - PASS (tick)
  • 101.8 Checking if ONOS CLI is ready - PASS (tick)
  • 101.9 Activate sdn-ip application - PASS (tick)

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

    • 2.1 Check P2P intents number from ONOS CLI - PASS (tick)

    Case 3: Check routes and M2S intents to all BGP peers - PASS

    • 3.1 Check routes installed - PASS (tick)
    • 3.2 Check M2S intents installed - PASS (tick)
    • 3.3 Check whether all flow status are ADDED - PASS (tick)

    Case 4: Ping test for each route, all hosts behind BGP peers - PASS

    • 4.1 Check ping between each host pair, expect all to succede=True - PASS (tick)

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

    • 7.1 Stop sw32 - PASS (tick)
    • 7.2 Check routes installed - PASS (tick)
    • 7.3 Check M2S intents installed - PASS (tick)
    • 7.4 Check P2P intents installed - PASS (tick)
    • 7.5 Check ping between hosts behind BGP peers - PASS (tick)
    • 7.6 Check ping between BGP peers and speakers - PASS (tick)
    • 7.7 Check whether all flow status are ADDED - PASS (tick)

    Case 8: Start the edge sw32, check P-2-P and M-2-S intents, ping test - 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, expect all to succede=True - 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, expect all to succede=True - 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, expect all to succede=True - PASS (tick)