Page History

...

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

commit 2102bfb72076dccffd91371b8f151c16a09d7491 5c82b0fb376075841863a93063abfa37a2f10463 (HEAD -] master, origin/master, origin/HEAD)
Author: Carmelo Cascone Daniele Moro [carmelo@opennetworkingdaniele@opennetworking.org]
AuthorDate: Fri Mon Dec 4 167 20:5456:24 30 2020 -0800+0100
Commit: Carmelo Cascone [carmelo@opennetworkingBrian O'Connor [bocon@opennetworking.org]
CommitDate: Sat Tue Dec 5 0115 17:0350:39 10 2020 +0000
Fabric.p4 cherry-picks from onos-2.2
Support arbitrary bit width action parameter and match field
--
(cherry picked from commit 8f6b5cdabf7828f6f7c017f288aad87c7bd0911a)
Backport fabric-tna dbuf support to v1model
(cherry picked from commit 4d1d67fa3abb4d7517e5836fbb82c899acffa951)
Update SPGW p4 namespace to match fabric-tna
(cherry picked from commit 35e4d196eb61104e7f96c62361a100bb454ee1cf)
Change-Id: I3230a508a601180060e1041d4369a54f519658e1 This commit goes into the direction of supporting user-defined types in P4Runtime.
The modification is focusing on supporting fields and params with arbitrary bit width, that is the
case of using a String with the p4runtime_translation annotation on the user-defined type.

Change-Id: I7db7a6d97211378ff78ab4f1b3734a0bec4558e6

Case 1: Starting up 3 node(s) ONOS cluster - PASS

...

• 100.1 Kill link between s1 and h1. - PASS
• 100.2 Check intent states - FAIL
• Not all Intents in installed state
• 100.3 Testing connectivity... - PASS
• 100.4 Re-adding link between s1 and h1. - PASS
• 100.5 Discover h1 using ping. - No Result
• 100.6 Check intent states - PASS
• 100.7 Testing connectivity... - PASS
• 100.8 Kill link between s2 and h2. - PASS
• 100.9 Check intent states - FAIL
• Not all Intents in installed state
• 100.10 Testing connectivity... - PASS
• 100.11 Re-adding link between s2 and h2. - PASS
• 100.12 Discover h2 using ping. - No Result
• 100.13 Check intent states - PASS
• 100.14 Testing connectivity... - PASS
• 100.15 Kill link between s3 and h3. - PASS
• 100.16 Check intent states - FAIL
• Not all Intents in installed state
• 100.17 Testing connectivity... - PASS
• 100.18 Re-adding link between s3 and h3. - PASS
• 100.19 Discover h3 using ping. - No Result
• 100.20 Check intent states - FAIL
Not all Intents in installed state
• PASS
• 100.21 Testing connectivity... - PASS
• 100.22 Kill link between s4 and h4. - PASS
• 100.23 Check intent states - FAIL
• Not all Intents in installed state
• 100.24 Testing connectivity... - PASS
• 100.25 Re-adding link between s4 and h4. - PASS
• 100.26 Discover h4 using ping. - No Result
• 100.27 Check intent states - FAIL
Not all Intents in installed state
• PASS
• 100.28 Testing connectivity... - PASS
• 100.29 Kill link between s5 and h5. - PASS
• 100.30 Check intent states - FAIL
• Not all Intents in installed state
• 100.31 Testing connectivity... - PASS
• 100.32 Re-adding link between s5 and h5. - PASS
• 100.33 Discover h5 using ping. - No Result
• 100.34 Check intent states - FAIL
Not all Intents in installed state
• PASS
• 100.35 Testing connectivity... - PASS
• 100.36 Kill link between s6 and h6. - PASS
• 100.37 Check intent states - FAIL
• Not all Intents in installed state
• 100.38 Testing connectivity... - PASS
• 100.39 Re-adding link between s6 and h6. - PASS
• 100.40 Discover h6 using ping. - No Result
• 100.41 Check intent states - PASS
• 100.42 Testing connectivity... - PASS

...

• 200.1 Delete s5. - PASS
• 200.2 Check intent states - FAIL
• Not all Intents in installed state
• 200.3 Testing connectivity... - FAIL
Connectivity failed.
• PASS
• 200.4 Add s5. - PASS
• 200.5 Reconnecting links on s5. - No Result
• 200.6 Check intent states - PASS
• 200.7 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

...