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_SdnipFunctionCluster/674/

...

...

Case 101: Starting up 3 node(s) ONOS cluster - PASS

Set up ONOS with 3 node(s) ONOS cluster

...

  • 101.1 Copying config files - PASS (tick)
  • 101.2 Create cell file - No Result (warning) 101.3 Applying cell variable Apply cell to environment - PASS (tick)
  • 101.4 Verify cell connectivity - PASS (tick) 101.5 3 Uninstalling ONOS package - PASS (tick)
  • 101.6 4 Creating ONOS package - PASS (tick)
  • 101.7 5 Installing ONOS package - PASS (tick)
  • 101.8 6 Set up ONOS secure SSH - PASS (tick)
  • 101.9 Checking if ONOS is up yet 7 Starting ONOS service - PASS (tick)
  • 101.10 Checking if 8 Starting ONOS CLI is ready sessions - PASS (tick)
  • 101.11 9 Checking if ONOS CLI is ready for issuing commands - PASS (tick)

...

  • 102.1 Set up tunnel from Mininet node 1.1.1.2:2000 to ONOS node 10.254.1.201:2000 - PASS (tick)
  • 102.2 Set up tunnel from Mininet node 1.1.1.4:2000 to ONOS node 10.254.1.202:2000 - PASS (tick)
  • 102.3 Set up tunnel from Mininet node 1.1.1.6:2000 to ONOS node 10.254.1.203:2000 - PASS (tick)
  • 102.4 Set up tunnel from Mininet node 1.1.1.8:2000 to ONOS node 10.254.1.204:2000 - PASS (tick)
  • 102.5 Set up tunnel from Mininet node 1.1.1.10:2000 to ONOS node 10.254.1.205:2000 - PASS (tick)
  • 102.6 Set up tunnel from Mininet node 1.1.1.12:2000 to ONOS node 10.254.1.206:2000 - PASS (tick)
  • 102.7 Set up tunnel from Mininet node 1.1.1.14:2000 to ONOS node 10.254.1.207:2000 - PASS (tick)

Case 1: Ping between BGP peers and speakers - PASS

...

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

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

...

  • 5.1 Bring down the link between sw32 and p64514 - PASS (tick)
  • 5.2 Check routes installed - PASS (tick)
  • 5.3 Check M2S intents installed - PASS (tick)
  • 5.4 Bring down the link between sw8 and p64515 - PASS (tick)
  • 5.5 Check routes installed - PASS (tick)
  • 5.6 Check M2S intents installed - PASS (tick)
  • 5.7 Bring down the link between sw28 and p64516 - PASS (tick)
  • 5.8 Check routes installed - PASS (tick)
  • 5.9 Check M2S intents installed - PASS (tick)
  • 5.10 Check whether all flow status are ADDED - PASS (tick)
  • 5.11 BGP speakers ping peers, expect all tests to fail - PASS (tick)
  • 5.12 Check ping between each host pair, expect all to succede=False - PASS (tick)

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

...

FAIL

  • 6.1 Bring up the link between sw32 and p64514 - 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 p64515 - 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 p64516 - 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 fail - PASS (tick)
  • 6.12 Check ping between each host pair, expect all to succede=True - PASS (tick)False - FAIL (error)
    • Ping test results are Not expected

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

...