Page History

...

<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/FUNCnetCfg_onos-2.0_20-builds_graph.jpg", alt="FUNCnetCfg", style="width:525px;height:350px;border:0">

commit ea646e910b2a9d2607f8e3605109dbc893ba60b5 1e0d651c1109e6cc6704ed1b62f614ac220f956f (HEAD -] onos-2.0, origin/onos-2.0)
Author: ONOS Jenkins User pier [jenkins@onlabpier@opennetworking.usorg]
AuthorDate: Tue Jan 8 00:32:36 2019 +0000Fri Dec 21 22:02:25 2018 +0100
Commit: ONOS Jenkins User [jenkins@onlab.usRay Milkey [ray@opennetworking.org]
CommitDate: Tue Fri Jan 8 0011 04:3245:36 33 2019 +0000
Starting snapshot 2.0.0-SNAPSHOT
Fix route events delivery

Case 1: Pull onos branch and build onos on Teststation. - PASS

...

• 25.1 Moving network-cfg.json to $ONOS_ROOT/tools/package/config/ - PASS

Case 2: Starting

...

up

...

3 node(s)

...

• 2.1 Apply cell to environment - PASS
• 2.2 Uninstalling Atomix - PASS
• 2.3 Uninstalling ONOS package - PASS
• 2.4 Creating ONOS package - PASS
• 2.5 Installing Atomix - PASS
• 2.6 Installing ONOS package - PASS
• 2.7 Set up ONOS secure SSH - PASS
• 2.8 Checking ONOS service - PASS
• 2.9 Starting ONOS CLI sessions - PASS
• 2.10 Checking ONOS nodes - PASS
• 2.11 Checking ONOS applications - PASS

Case 20: Add Network configurations to the cluster - FAIL

Add Network Configurations for devices not discovered yet. One device is allowed, the other disallowed.

• 20.1 Add Net Cfg for switch1 - PASS
• 20.2 Add Net Cfg for switch3 - PASS
• 20.3 Check net config - FAIL
• Check Net Cfg failed. Check above messages.

Case 11: Start Mininet topology with OF 1.3 switches - PASS

Start mininet topology with OF 1.3 switches to test intents, exits out if topology did not start correctly

• 11.1 Starting Mininet topology with OF 1.3 switches - PASS

Case 27: Posting network configurations to the top level web resource - FAIL

• 27.1 Get json object from Net Cfg - No Result
• 27.2 Posting json object to Net Cfg - No Result
• 27.3 Compare device with ONOS - No Result
• 27.4 Check net config - FAIL
• Check Net Cfg failed. Check above messages.
• 27.5 ONOS should only show devices S1, S2, S4, S5 and S6 - PASS
• 27.6 Modify json object so S6 is disallowed - PASS

Case 26: Check to see if the pre-startup configurations were set, then remove their allowed status - PASS

• 26.1 Checking configurations for Switches 5 and 6 - No Result
• 26.2 ONOS should only show devices S1, S2, S4, and S5 - PASS
• 26.3 Removing allowed status from Switches 5 and 6 - No Result

...

ONOS

...

• 21.1 Check net config - FAIL
• Check Net Cfg failed. Check above messages.
• 21.2 ONOS should only show devices S1, S2, and S4 - PASS
• 21.3 Check device annotations - PASS

...

cluster - FAIL

...

Add Network Configurations for discovered devices. One device is allowed, the other disallowed.

• 22.1 Add Net Cfg for switch2 - PASS
• 22.2 Add Net Cfg for switch4 - FAIL
• Net Cfg for device s4 not correctly set
• 22.3 Check net config - FAIL
• Check Net Cfg failed. Check above messages.

Case 23: Check Devices after all configurations are set - FAIL

• 23.1 Check net config - FAIL
• Check Net Cfg failed. Check above messages.
• 23.2 ONOS should only show devices S1 and S2 - FAIL
• ONOS devices doesn't match the list of allowed devices.
• Expected devices: ['of:0000000000000001', 'of:0000000000000002']
• Actual devices: ['of:0000000000000001', 'of:0000000000000002', 'of:0000000000000004']
• 23.3 Check device annotations - PASS

Case 24: Testing removal of configurations - FAIL

...

• Failed to remove the 'allowed' config key.

...

• Check Net Cfg failed. Check above messages.

...

• Check Net Cfg failed. Check above messages.

...

• Failed to removed S3's config

...

• Check Net Cfg failed. Check above messages.

...

• Failed to remove device config

...

• Check Net Cfg failed. Check above messages.

...