Have questions? Stuck? Please check our FAQ for some common questions and answers.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Current »

HAfullNetPartition at 25 Oct 2016 03:32:25

commit c70254e15df6e48bf7f4bc712fdd143f18fd801e (HEAD, origin/onos-1.7, onos-1.7)
Author: Brian O'Connor [bocon@onlab.us]
AuthorDate: Mon Oct 24 00:41:40 2016 -0700
Commit: Brian O'Connor [bocon@onlab.us]
CommitDate: Mon Oct 24 15:01:39 2016 -0700

Moving snmp libs to released version; ejecing bti driver due to incompatibility

Case 1: Setting up test environment - PASS

Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.

  • 1.1 Create cell file - No Result (warning)
  • 1.2 Applying cell variable to environment - No Result (warning)
  • 1.3 Starting Mininet - PASS (tick)
  • 1.4 Git checkout and pull master - No Result (warning)
  • 1.5 Using mvn clean install - PASS (tick)
  • 1.6 Creating ONOS package - PASS (tick)
  • 1.7 Installing ONOS package - PASS (tick)
  • 1.8 Checking if ONOS is up yet - PASS (tick)
  • 1.9 Starting ONOS CLI sessions - PASS (tick)
  • 1.10 Checking ONOS nodes - PASS (tick)
  • 1.11 Activate apps defined in the params file - No Result (warning)
  • 1.12 Set ONOS configurations - PASS (tick)
  • 1.13 App Ids check - PASS (tick)

Case 2: Assigning devices to controllers - PASS

Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device.

  • 2.1 Assign switches to controllers - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology - PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN topology - PASS (tick)
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.6 There is only one SCC - PASS (tick)
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - PASS (tick)

Case 21: Assigning Controller roles for switches - PASS

Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'

  • 21.1 Assign mastership of switches to specific controllers - PASS (tick)
  • 21.2 Check mastership was correctly assigned - PASS (tick)

Case 3: Adding host Intents - PASS

Discover hosts by using pingall then assign predetermined host-to-host intents. After installation, check that the intent is distributed to all nodes and the state is INSTALLED

  • 3.1 Install reactive forwarding app - PASS (tick)
  • 3.2 Check app ids - PASS (tick)
  • 3.3 Discovering Hosts( Via pingall for now ) - PASS (tick)
  • 3.4 Uninstall reactive forwarding app - PASS (tick)
  • 3.5 Check app ids - PASS (tick)
  • 3.6 Add host intents via cli - PASS (tick)
  • 3.7 Intent Anti-Entropy dispersion - PASS (tick)

Case 4: Verify connectivity by sending traffic across Intents - PASS

Ping across added host intents to check functionality and check the state of the intent

  • 4.1 Check Intent state - PASS (tick)
  • 4.2 Ping across added host intents - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - PASS (tick)

Case 5: Setting up and gathering data for current state - No Result

  • 5.1 Check that each switch has a master - FAIL (error)
    • Some devices don't have a master assigned
  • 5.2 Get the Mastership of each switch from each controller - FAIL (error)
    • Error in reading roles from ONOS
  • 5.3 Check for consistency in roles from each controller - FAIL (error)
    • ONOS nodes have different views of switch roles
  • 5.4 Get the intents from each controller - FAIL (error)
    • Error in reading intents from ONOS
  • No labels