Date: Fri, 29 Mar 2024 10:48:46 +0000 (UTC)
Message-ID: <1908537755.1075.1711709326403@ip-10-30-146-46.us-west-2.compute.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_1074_1278085403.1711709326400"
------=_Part_1074_1278085403.1711709326400
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
FUNCgroup at 21 Apr 2019 12:55:30=20
commit 1990278de6f59d84cd81aebe84135050122b056b (HEAD -] onos-2.0, origin/o=
nos-2.0)
Author: Thomas Vachuska [tom@opennetworking.org]
AuthorDate: Mon Apr 15 09:42:24 2019 -0700
Commit: Thomas Vachuska [tom@opennetworking.org]
CommitDate: Mon Apr 15 09:46:35 2019 -0700
Replaced test mock with existing adapter in archetypes.
Case 1: Pull onos branch and build onos on Teststation. - PASS
For loading from params file, and pull and build the latest ONOS package=
- 1.1 Constructing test variables - PASS :tick:
Case 2:=
Starting up 1 node(s) ONOS cluster - PASS
Set up ONOS with 1 node(s) ONOS cluster
- 2.1 Apply cell to environment - PASS :tick:
- 2.2 Uninstalling Atomix - PASS :tick:
- 2.3 Uninstalling ONOS package - PASS :tick:
- 2.4 Creating ONOS package - PASS :tick:
- 2.5 Installing Atomix - PASS :tick:
- 2.6 Installing ONOS package - PASS :tick:
- 2.7 Set up ONOS secure SSH - PASS :tick:
- 2.8 Checking ONOS service - PASS :tick:
- 2.9 Starting ONOS CLI sessions - PASS :tick:
- 2.10 Checking ONOS nodes - PASS :tick:
- 2.11 Checking ONOS applications - PASS :tick:
Case 3: Compare ONOS Topology view to Mininet topology - PASS
Compare topology elements between Mininet and ONOS
- 3.1 Copy Mininet topology file - PASS :tick:
- 3.2 Setup Mininet Topology - PASS :tick:
- 3.3 Assign switch to controller - PASS :tick:
- 3.4 Comparing Mininet topology to ONOS topology - PASS :tick:
- 3.5 Create hosts and start scapy - No Result :warning:
- 3.6 Start scapy components - PASS :tick:
Case 5: Verify Group of type All are successfully Added - PASS
Install a Group of type ALL Verify the Group is Added Add a flow using t=
he group Send a packet that verifies the action bucket of the group
- 5.1 Add Group using Rest api - PASS :tick:
- 5.2 Check groups are in ADDED state - PASS :tick:
- 5.3 Adding flow with Group using rest api - PASS :tick:
- 5.4 Testing Group by sending packet using Scapy - PASS :tick:
Case 6: Delete the Group and Flow added through Rest api - PASS
- 6.1 Deleting Group and Flows - No Result :warning:
- 6.2 Deleting the created flow by deviceId and flowId - PASS :tick:
- 6.3 Deleting the created group by deviceId and appCookie - PASS :tick:<=
/li>
Case 7: Verify Group of type INDIRECT are successfully Added - PAS=
S
Install a Group of type INDIRECT Verify the Group is Added Add a flow us=
ing the group Send a packet that verifies the action bucket of the group
- 7.1 Add Group using Rest api - PASS :tick:
- 7.2 Check groups are in ADDED state - PASS :tick:
- 7.3 Adding flow with Group using rest api - PASS :tick:
- 7.4 Testing Group by sending packet using Scapy - PASS :tick:
Case 6: Delete the Group and Flow added through Rest api - PASS
- 6.1 Deleting Group and Flows - No Result :warning:
- 6.2 Deleting the created flow by deviceId and flowId - PASS :tick:
- 6.3 Deleting the created group by deviceId and appCookie - PASS :tick:<=
/li>
Case 10: Stop Mi=
ninet and Scapy - PASS
Stopping the current mininet topology to start up fresh
- 10.1 Stopping and Removing Scapy Host Components - PASS :tick:
- 10.2 Stopping Mininet - PASS :tick:
Case 100: - PASS
------=_Part_1074_1278085403.1711709326400--