diff options
| author |   Vratko Polak <vrpolak@cisco.com> | 2020-12-15 13:39:56 +0100 |
|---|---|---|
| committer | Vratko Polak <vrpolak@cisco.com> | 2020-12-17 12:28:57 +0000 |
| commit | a33b52ae0f255021d89307ebc694f6e907906151 (patch) | |
| tree | 133f7cc93cd5475d211982c952244e96a223ba59 /resources/libraries/robot | |
| parent | 37877d670e7e2d81673222b6c3d9e7649ccd5cd5 (diff) | |
PAPI: Cache connected client instances
Disconnect+connect cycle is expensive and slow.
This change tracks connected client instances
so later "connect" to the same target uses it.
Explicit disconnects are allowed (and executed before VPP ends),
but once again disconnected instances are cached and reused,
as creating a new instance is more expensive than just connect.
+ Add missing checks on interfaces being up to appropriate keyword.
+ Use appropriate keywords.
+ Add a comment explaining why a simpler keyword is not appropriate.
+ Improve VPP checks in containers.
+ Fix the vppctl check to actually work.
+ Add PAPI check to ensure VPP is really ready.
+ Delay/reorder checks to make them faster with multiple containers.
+ Leave some TODOs to improve various lifecycles later.
+ As we do not stop VPP in test/suite teardown:
+ One final disconnect is needed, added to __init__.robot teardowns.
- Import of the final disconnect keyword is ugly, but it works.
- We could use a hashable class for distinguishing node+socket pairs.
- Are we connecting to VPP inside VMs?
Change-Id: I49cd726740c3e8cae1591c7c84b85a447241228f
Signed-off-by: Vratko Polak <vrpolak@cisco.com>
Diffstat (limited to 'resources/libraries/robot')
| -rw-r--r-- | resources/libraries/robot/l2/l2_bridge_domain.robot | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/resources/libraries/robot/l2/l2_bridge_domain.robot b/resources/libraries/robot/l2/l2_bridge_domain.robot index 543c01c3ba..1726eb0ae6 100644 --- a/resources/libraries/robot/l2/l2_bridge_domain.robot +++ b/resources/libraries/robot/l2/l2_bridge_domain.robot @@ -595,6 +595,9 @@ | | ... | Memif interface to separate L2 bridge domain with one physical or | | ... | virtual interface to create a chain accross DUT node. | | +| | ... | This keyword does not wait for memifs to go up. +| | ... | Use the "for multiple chains" keyword for that functionality. +| | | | ... | *Arguments:* | | ... | - nf_chain - NF chain. Type: integer | | ... | - nf_nodes - Number of NFs nodes per chain. Type: integer @@ -800,6 +803,7 @@ | | ... | Add interface to bridge domain | | ... | ${dut2} | ${DUT2_${int}2}[0] | ${bd_id2} | | +| | Set interfaces in path up | | Show Memif on all DUTs | ${nodes} | | VPP round robin RX placement on all DUTs | ${nodes} | prefix=memif |