Versions Compared

Old Version 95

changes.mady.by.user Jenkins Technical User

Saved on

compared with

New Version 96

changes.mady.by.user Jon Hall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 93

...

commit 3203557e6b0725b505f14135c6f15ebd48c5e1fb 9d54c26ea9ed3a3bffadb87e26e082e28eaae188 (HEAD, origin/master, origin/HEAD, master)
Author: Satish K jiangrui [satishk@huaweijiangrui1@huawei.com]
AuthorDate: Sun Sat Nov 22 28 14:4923:14 39 2015 +05300800
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Mon Nov 23 1930 01:4538:29 42 2015 +0000
tenant network review fix
[ONOS-2755] add restfull service of floatingIp

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 default br-int configuration and vxlan port -

...

PASS

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

  • 3.1 ovsdb node 1 set ovs manager to 10.128254.201.11 201 - PASS (tick)
  • 3.2 ovsdb node 2 set ovs manager to 10.128254.201.11 201 - PASS (tick)
  • 3.3 Check ovsdb node 1 manager is 10.128254.201.11 201 - PASS (tick)
  • 3.4 Check ovsdb node 2 manager is 10.128254.201.11 201 - FAIL (error)
    • ovsdb node 2 manager check failed
  • PASS (tick)
  • 3.5 Check default br-int bridge on ovsdb node 10.128254.101.11 200 - PASS (tick)
  • 3.6 Check default br-int bridge on ovsdb node 10.128254.201.11 201 - FAIL (error)
    • onos add default bridge on the node 2 failed
  • PASS (tick)
  • 3.7 Check default vxlan port on ovsdb node 10.128254.101.11 - FAIL (error)
    • onos add default vxlan port on the node 1 failed
  • 200 - PASS (tick)
  • 3.8 Check default vxlan port on ovsdb node 10.128254.201.11 - FAIL (error)
    • onos add default vxlan port on the node 2 failed
  • 201 - PASS (tick)

Case 4: -

...

PASS

  • 4.1 ovsdb node 1 set ovs manager to 10.128254.201.11 201 - PASS (tick)
  • 4.2 ovsdb node 2 set ovs manager to 10.128254.201.11 201 - PASS (tick)
  • 4.3 Check ovsdb node 1 manager is 10.128254.201.11 201 - PASS (tick)
  • 4.4 Check ovsdb node 2 manager is 10.128254.201.11 - FAIL (error)
    • ovsdb node 2 manager check failed
    • sudo ovs-vsctl show
    • sudo: ovs-vsctl: command not found
    • ^[]0;sdn@suibin-prodVM-onos01: ~^Gsdn@suibin-prodVM-onos01:~$
  • 201 - PASS (tick)
  • 4.5 Check ovsdb node 1 bridge br-int controller set to 10.128254.201.11 201 - PASS (tick)
  • 4.6 Check ovsdb node 2 bridge br-int controller set to 10.128254.201.11 - FAIL (error)
  • ^[[Ksudo ovs-vsctl show
  • sudo: ovs-vsctl: command not found
    • ^[]0;sdn@suibin-prodVM-onos01: ~^Gsdn@suibin-prodVM-onos01:~$
  • 201 - PASS (tick)
  • 4.7 Check onoscli devices have ovs 10.128254.101.11 200 - PASS (tick)
  • 4.8 Check onoscli devices have ovs 10.128254.201.11 201 - FAIL (error)PASS (tick)

Case 2: Test ovsdb connection and teardown - PASS

...

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

Case 5: - PASS

  • 5.1 ovsdb node 1 set ovs manager to onos - PASS (tick)
  • 5.2 Check ovsdb node 1 manager is 10.128254.201.11 201 - PASS (tick)
  • 5.3 Check ovsdb node 1 bridge br-int default flows on 10.128254.101.11 200 - PASS (tick)

Case 6: Configure Network Subnet Port - PASS

...

  • 7.1 ovsdb node 1 set ovs manager to 10.128254.201.11 201 - PASS (tick)
  • 7.2 ovsdb node 2 set ovs manager to 10.128254.201.11 201 - PASS (tick)
  • 7.3 Create host1 on node 1 10.128254.101.11 200 - PASS (tick)
  • 7.4 Create host2 on node 2 10.128254.201.11 201 - PASS (tick)
  • 7.5 Create port on host1 on the node 10.128254.101.11 200 - PASS (tick)
  • 7.6 Create port on host2 on the node 10.128254.201.11 201 - PASS (tick)
  • 7.7 Add port to ovs br-int and host go-online on the node 10.128254.101.11 200 - PASS (tick)
  • 7.8 Add port to ovs br-int and host go-online on the node 10.128254.201.11 201 - PASS (tick)
  • 7.9 Check onos set host flows on the node 10.128254.101.11 200 - PASS (tick)
  • 7.10 Check onos set host flows on the node 10.128254.201.11 201 - FAIL (error)PASS (tick)
  • 7.11 Check hosts can ping each other - FAIL (error)

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.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.128254.101.11 200 - PASS (tick)
  • 8.8 Check onoscli devices have ovs 10.128254.201.11 201 - FAIL (error)PASS (tick)