Add bgp suites with explicit shard leader location 97/56497/7
authorPeter Gubka <pgubka@cisco.com>
Thu, 4 May 2017 04:21:21 +0000 (06:21 +0200)
committerVratko Polák <vrpolak@cisco.com>
Fri, 5 May 2017 08:21:24 +0000 (08:21 +0000)
commit19fc3286c9488a9c3f310a8b7364d5f6c8d57a9c
tree3e294b6de2c91c0aa8d7d7755baf575df9d78286
parent0aeea6bf3fac214159cc0f59c4d5416abb4e2bab
Add bgp suites with explicit shard leader location

Suites add 300k prefixes when rib owner is on the same/different
odl node as default/topology (config and operational) shard
leader.

In PrefixcountKeywords.robot the http sessions are created with
timeout=40. It is due to a big size of the http response when
all 300k or 1M prefixes are requested for counting.

Change-Id: I2e816df917402af71f51fe093553a072cc44e2a9
Signed-off-by: Peter Gubka <pgubka@cisco.com>
csit/libraries/ShardStability.robot
csit/suites/bgpcep/bgpclustering/PrefixcountKeywords.robot
csit/suites/bgpcep/bgpclustering/singlepeer_pc_shm_300kroutes_shards_local.robot [new file with mode: 0644]
csit/suites/bgpcep/bgpclustering/singlepeer_pc_shm_300kroutes_shards_remote.robot [new file with mode: 0644]
csit/testplans/bgpcep-bgpclustering.txt