Page tree

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/FUNCovsdbtest/43/

...

commit 280e791115830772b72557d47b91622a9802897f (HEAD, onos-1.333279c8f41a23d47f32aa0cda971aea63c70ee0c (HEAD, origin/master, origin/HEAD, master)
Author: Sho SHIMIZU andrea [sshimizu@usandrea@onlab.fujitsu.comus]
AuthorDate: Tue Wed Sep 29 1330 15:4230:03 48 2015 -0700
Commit: Gerrit Code Review [gerrit@onlabRay Milkey [ray@onlab.us]
CommitDate: Wed Sep 30 0023:4214:24 35 2015 +0000
Remove use of org.onosproject.net.resource.ResourceAllocation
--
future refactoring. This commit is to avoid the conflict.
Change-Id: I47928ba6fa56c00aea7c0f85d7be8593b4862cba
Minor formatting changes in unit test for component config loader

Case 1: Setting up test environment - PASS

...

  • 1.1 Create cell file - No Result (warning)
  • 1.2 Applying cell variable to environment - No Result (warning)
  • 1.3 Git checkout and pullmaster - No Result (warning)
  • 1.4 Using mvn clean install - PASS (tick)
  • 1.5 Creating ONOS package - PASS (tick)
  • 1.6 Installing ONOS package - PASS (tick)
  • 1.7 Checking if ONOS is up yet - PASS (tick)
  • 1.8 App Ids check - No Result (warning)
  • 1.9 Install onos-ovsdatabase - PASS (tick)
  • 1.10 Install onos-app-vtnrsc - PASS (tick)
  • 1.11 Install onos-app-vtn - PASS (tick)
  • 1.12 Install onos-app-vtnweb - PASS (tick)

Case

...

3: Test

...

Test ovsdb connection create and delete over ovsdb node and onos node

...

default br-int configuration and vxlan port - FAIL

onos create default br-int bridge and vxlan port on the ovsdb node

  • 3.1 ovsdb node 1 set ovs manager to 10.254.1.201 - PASS (tick)
  • 2 3.2 Check ovsdb node 2 set ovs manager is to 10.254.1.201 - PASS (tick)
  • 2 3.3 Delete Check ovsdb node 1 manager is 10.254.1.201 - PASS (tick)
  • 2 3.4 Check ovsdb node delete 2 manager is 10.254.1.201 - PASS (tick)

...

  • 3

...

  • .5 Check default br-int

...

  • bridge on ovsdb node 10.254.1.200 - FAIL (error)
    • onos

...

    • add default bridge on the node 1 failed
  • 3.6 Check default br-int

...

  • bridge on ovsdb node 10.254.1.201 - FAIL (error)
    • onos add default bridge on the node 2 failed
  • 3.7 Check default vxlan port on ovsdb node 10.254.1.200 - FAIL (error)
    • onos add default vxlan port on the node 1 failed
  • 3.8 Check default vxlan port on ovsdb node 10.254.1.201 - FAIL (error)
    • onos add default vxlan port on the node

...

    3
    • 2 failed

Case 4: - FAIL

  • 4.1 ovsdb node 1 set ovs manager to 10.254.1.201 - PASS (tick)
  • 3 4.2 ovsdb node 2 set ovs manager to 10.254.1.201 - PASS (tick)
  • 3 4.3 Check ovsdb node 1 manager is 10.254.1.201 - PASS (tick)
  • 3 4.4 Check ovsdb node 2 manager is 10.254.1.201 - PASS (tick) 3
  • 4.5 Check default br-int bridge on ovsdb node Check ovsdb node 1 bridge br-int controller set to 10.254.1.201 - PASS (tick)
  • 4.6 Check ovsdb node 2 bridge br-int controller set to 10.254.1.201 - FAIL (error)
    • Check ovsdb node 2 bridge br-int controller set to 10.254.1.201 failed
  • 4.7 Check onoscli devices have ovs 10.254.1.200 - PASS (tick)
  • 4.8 Check onoscli devices have ovs 10.254.1.201 - PASS (tick)

Case 2: Test ovsdb connection and teardown - PASS

Test ovsdb connection create and delete over ovsdb node and onos node

  • 2.1 Set ovsdb node manager - PASS (tick)
  • 2.2 Check ovsdb node manager is 10.254.1.201 - PASS (tick)
  • 2.3 Delete ovsdb node manager - PASS (tick)
  • 2.4 Check ovsdb node delete manager 10.254.1.201 - PASS (tick)

Case 5: - FAIL

  • 5.1 ovsdb node 1 set ovs manager to onos - PASS (tick)
  • 5.2 Check ovsdb node 1 manager is 10.254.1.201 - PASS (tick)
  • 5.3 Check ovsdb node 1 bridge br-int default flows on 10.254.1.200 - FAIL (error)
    • onos add default bridge on the node 1 failed
    3.6 Check default br-int bridge on ovsdb
    • Failed to set default flows 10.254.1.201

Case 6: Configure Network Subnet Port - PASS

Configure Network Subnet Port Verify post is OK

  • 6.1 Generate Post Data - No Result (warning)
  • 6.2 Post Network Data via HTTP(Post port need post network) - PASS (tick)
  • 6.3 Post Subnet Data via HTTP(Post port need post subnet) - PASS (tick)
  • 6.4 Post Port1 Data via HTTP - PASS (tick)
  • 6.5 Post Port2 Data via HTTP - PASS (tick)

Case 7: - FAIL

  • 7.1 ovsdb node 1 set ovs manager to 10.254.1.201 - PASS (tick)
  • 7.2 ovsdb node 2 set ovs manager to 10.254.1.201 - PASS (tick)
  • 7.3 Create host1 on node 1 10.254.1.200 - PASS (tick)
  • 7.4 Create host2 on node 2 10.254.1.201 - PASS (tick)
  • 7.5 Create port on host1 on the node 10.254.1.200 - PASS (tick)
  • 7.6 Create port on host2 on the node 10.254.1.201 - PASS (tick)
  • 7.7 Add port to ovs br-int and host go-online on the node 10.254.1.200 - PASS (tick)
  • 7.8 Add port to ovs br-int and host go-online on the node 10.254.1.201 - PASS (tick)
  • 3.7 Check default vxlan port on ovsdb 7.9 Check onos set host flows on the node 10.254.1.200 - PASS (tick)
  • 7.10 Check onos set host flows on the node 10.254.1.200 201 - FAIL (error)
    • onos add default vxlan port Check onos set host flows on the node 10.254.1.201 failed
  • 7.11 Check hosts can ping each other - FAIL (error)
    • Failed to host go online and ping each other,controller is 10.254.1.201

Case 8: - PASS

  • 8.1 Delete ovsdb node 1 manager - PASS (tick)
  • 8.2 Delete ovsdb node 2 manager - PASS (tick)
  • 8.3 Delete ovsdb node 1 bridge br-int - PASS (tick)
  • 8.8 Check default vxlan port on ovsdb node 4 Delete ovsdb node 2 bridge br-int - PASS (tick)
  • 8.5 Delete ip netns host on the ovsdb node 1 - PASS (tick)
  • 8.6 Delete ip netns host on the ovsdb node 2 - PASS (tick)
  • 8.7 Check onoscli devices openflow session is false 10.254.1.200 - PASS (tick)
  • 8.8 Check onoscli devices have ovs 10.254.1.201 - PASS (tick)