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 62 Next »

FUNCovsdbtest at 26 Oct 2015 20:44:04

commit 596f266186961ed460b25153ae9403f538b2ba99 (HEAD, origin/master, origin/HEAD, master)
Author: Madan Jampani [madan.jampani@gmail.com]
AuthorDate: Fri Oct 23 14:35:23 2015 -0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Fri Oct 23 21:42:22 2015 +0000

Fix onos-setup-karaf to work with new cluster metadata format

Case 1: Setting up test environment - PASS

Setup the test environment including installing ONOS, start ONOS.

  • 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.254.1.201 - PASS (tick)
  • 3.2 ovsdb node 2 set ovs manager to 10.254.1.201 - PASS (tick)
  • 3.3 Check ovsdb node 1 manager is 10.254.1.201 - PASS (tick)
  • 3.4 Check ovsdb node 2 manager is 10.254.1.201 - PASS (tick)
  • 3.5 Check default br-int bridge on ovsdb node 10.254.1.200 - PASS (tick)
  • 3.6 Check default br-int bridge on ovsdb node 10.254.1.201 - PASS (tick)
  • 3.7 Check default vxlan port on ovsdb node 10.254.1.200 - PASS (tick)
  • 3.8 Check default vxlan port on ovsdb node 10.254.1.201 - PASS (tick)

Case 4: - PASS

  • 4.1 ovsdb node 1 set ovs manager to 10.254.1.201 - PASS (tick)
  • 4.2 ovsdb node 2 set ovs manager to 10.254.1.201 - PASS (tick)
  • 4.3 Check ovsdb node 1 manager is 10.254.1.201 - PASS (tick)
  • 4.4 Check ovsdb node 2 manager is 10.254.1.201 - PASS (tick)
  • 4.5 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 - PASS (tick)
  • 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 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.254.1.201 - PASS (tick)
  • 3.2 ovsdb node 2 set ovs manager to 10.254.1.201 - PASS (tick)
  • 3.3 Check ovsdb node 1 manager is 10.254.1.201 - PASS (tick)
  • 3.4 Check ovsdb node 2 manager is 10.254.1.201 - PASS (tick)
  • 3.5 Check default br-int bridge on ovsdb node 10.254.1.200 - PASS (tick)
  • 3.6 Check default br-int bridge on ovsdb node 10.254.1.201 - PASS (tick)
  • 3.7 Check default vxlan port on ovsdb node 10.254.1.200 - PASS (tick)
  • 3.8 Check default vxlan port on ovsdb node 10.254.1.201 - PASS (tick)

Case 4: - PASS

  • 4.1 ovsdb node 1 set ovs manager to 10.254.1.201 - PASS (tick)
  • 4.2 ovsdb node 2 set ovs manager to 10.254.1.201 - PASS (tick)
  • 4.3 Check ovsdb node 1 manager is 10.254.1.201 - PASS (tick)
  • 4.4 Check ovsdb node 2 manager is 10.254.1.201 - PASS (tick)
  • 4.5 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 - PASS (tick)
  • 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 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.254.1.201 - PASS (tick)
  • 3.2 ovsdb node 2 set ovs manager to 10.254.1.201 - PASS (tick)
  • 3.3 Check ovsdb node 1 manager is 10.254.1.201 - PASS (tick)
  • 3.4 Check ovsdb node 2 manager is 10.254.1.201 - PASS (tick)
  • 3.5 Check default br-int bridge on ovsdb node 10.254.1.200 - PASS (tick)
  • 3.6 Check default br-int bridge on ovsdb node 10.254.1.201 - PASS (tick)
  • 3.7 Check default vxlan port on ovsdb node 10.254.1.200 - PASS (tick)
  • 3.8 Check default vxlan port on ovsdb node 10.254.1.201 - PASS (tick)

Case 4: - PASS

  • 4.1 ovsdb node 1 set ovs manager to 10.254.1.201 - PASS (tick)
  • 4.2 ovsdb node 2 set ovs manager to 10.254.1.201 - PASS (tick)
  • 4.3 Check ovsdb node 1 manager is 10.254.1.201 - PASS (tick)
  • 4.4 Check ovsdb node 2 manager is 10.254.1.201 - PASS (tick)
  • 4.5 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 - PASS (tick)
  • 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)
  • No labels