Change-Id: I4bffae0227c26445c8e6aeee8ecc3b7ffbcf4c36

Change-Id: If9552cad4ab733190ab83d3ae259e88a4a49ad6d

re-enable webui testcases

Change-Id: I9919dba466cbadb378020aaae9b5bfc89a9804f1

* Adding support in test infra to retrieve SRIOV data
* Adding testcase to verify  vf exhaustion and reuse
* Adding test case to verify ping with large mtu

Change-Id: I4fe99a36c3693b38ef940a52f089fc09e32dbd9a

Change-Id: I3b0eb00cfca214cceaedc67787049344307fc8d9

Change-Id: I4785cfc633e760bdd6854dc6c0126a2aff61ed10

Change-Id: I720862b58e2030c93c4523eeb9270c6b5712bcc0

…case." into R3.0

Change-Id: I8232618c1fbf3cfbc8bc876c1109ca4df4d97091

Change-Id: I2037bcd0b72c76ecfd679d7b49dc4d2bfba6e1d0

Ipam creation takes the name of the parent project
from it's connections which points to the admin project.
Changing it to take project name from the parent project
of the calling script, if available.

Change-Id: I86a31e2bbe28cdcb2262f52179d95d4d77306fa0

Change-Id: I823584570c8be297e0e1d7d5332dfe228e85e39f

Change-Id: Ibe921f8e87eb4d4897e1610f42c826a4a274f380

Change-Id: I6f0c6253b56c572e52a132a2820c9e8e7691bdfe

There were old files of flow related tests which
were duplicate of tests under serial_scripts/system_test/flow_tests.
So, entire serial_scripts/flow_tests is being removed and one of the
recent test case comitted to this directory "test_flow_scenarios.py"
is being moved under serial_scripts/system_test/flow_tests.

Change-Id: Idc159036cac1b5f7f4a7ddf19fc9af2680840a67

Removing assumption of vcenter server name

Fixing regression result mail subject issue
Setting SCRIPT_TS from run_tests.sh if not triggered from JENKINS
Change-Id: If56c9c22a17c81244505392cca09e076a51ac884

return false if intf uve doesnt have ip address or vn, so that retry
for vm verification in opserer kicks in. This is intermittently seen
 in ci sanity tests.

Change-Id: Icc36b76337eba295455effe56243fd686d086e07

* Adding the test case to test the handling of broadcast traffic
by vrouter

* Test case broadcast ping from one compute. Monitor on other compute
that it is receving the packet and not sending a copy back.

* It is targeting to verify scenario mentioned in bug 1545229

Change-Id: I1fa410a649ab6079442b2df5fde81250e6203986

1)Added code to get,set forwarding mode to vnc_api_test
2)created test suite to test forwarding modes at global_config and vn level
3)Changes to vm_test to skip some verifications when forwarding mode is set to L2

Change-Id: I8b4d06684634611c333aa80b3e7abc1644f21a2d

… of vcenter server name" into R3.0

…ddress or vn, so that retry for vm verification in opserer kicks in. This is intermittently seen in ci sanity tests." into R3.0

Change-Id: Iaca668e25037c462bef2f05f8ba5f1e0e3f19a18

Server-manager db post 3.0 doesn't come with
pre-configured tags. So adding a routine to add
these tags ro SM db explicitly.

Change-Id: I5da70500257158f85df3539fe750f1eed8c83381

Review comments incorporated

Change-Id: Ifbb2c90ad502e831113f0a84b9324d1c6ba9a188

Even after deletion of dynamic VGW, route does not get
deleted. Because of this subsequent cases fail in
regression. Making them separate test suite.

Change-Id: I19fcd7a7e9b2f866d002c97492a8df137aa09e51

…nto R3.0

TC covered -

test_verify_config_networking_ipams,
test_verify_config_networking_virtual_networks,
test_verify_config_services_service_instances

Change-Id: I4cbce99b39500c20a4880aa3f89abb65f0678c22

Removing vpc tag from so that they no longer runs in sanity.
Change-Id: I0f122c46b246a9a402adac8e801f23efc967ab65

 - Added checks to confirm if the services have exactly 1 "active"
   service
   when they could be possibly active or backup.

 - Adding a main function. Will be using the script in run_tests.sh file
   for checking the health of the cluster before running our sanity.

Change-Id: I2607f32c6ce2496577157ab19eaabe31a6108c29
Closes-Bug: #1554388

Change-Id: I491b3a28429d16f05fe929821edede9910744328

    Adding initial test cases to verify contrail alarms

Change-Id: I1db6977fe3c88d4ef5d5264422b6a6b452a491a7

Change-Id: I8810db476883e8381914787f06ca0e0b8450a483

* Use ContrailStatus checks after contrail-api restart
  instead of waiting 30 sec
* Update create_floatingips() and delete_floatingips()
  based on recent test code changes
* No need to retry in _create_vn_orch()
* Handle VN creation failure case due to quota check in
  VNFixture
* While testing quota values, consider any existing objects
  in the admin project while setting the limits
* Create unique SG rules in create_multiple_secgrp_rule()
* Always query neutron on call to get_lb_pool()
* Handle the case of ‘contrail-device-manager’ not present
  in the contrail-status command output

Conflicts:
	fixtures/vn_test.py

Change-Id: I63761fb814cadf7e4b4405a778ca9e9baaabca71

Description: Test to validate SCTP flow setup between
        Test steps:
                1. Run SCTP traffic between 2 VM across VN connected through FIP
                2. Verify the Ingress and Egress flow.
        Pass criteria: SCTP egress and ingress flow setup properly.

Change-Id: Iaac6ec2e985a753006c16ea023af70c7c250bd93

Conflicts:
	tcutils/util.py

Change-Id: I3a692a8fd7855fd059c5095999172b02872b420f

Currently each test suite creates its own projects/users
In production test environments, the admin would allocate
a specific project where the tests are expected to run
(stackUser, stackPassword and stackTenant in sanity_params.ini)

If tenant_isolation is enabled and admin credentials are
mentioned in sanity_params.ini, the existing behavior will
be seen

Corresponding fab code changes : https://review.opencontrail.org/16483

Change-Id: I13e5d0983472b1a8f9d2ecdd6f79e5df043ee04b

Change-Id: Ic4d108429742ffe2a351c940fd08e77f6e4f7b2b

Change-Id: Iba13f03cc7cc8d416e7a5b98a439d0b59aa1a6c4

Change-Id: I047627e1ce9b04eeb5538b776d15955efe2520ec

… level" into R3.0

* Adding sanity case to test SCTP flow setup
* Adding sanity case to test underlay multicast traffic handling.
* Adding sctp  traffic image to sanity.
Change-Id: Ia5b5a57c01cfb05d55bbc75670be9bfc5d817a2c

Adding the missing proc get_two_different_compute_hosts  leftover
in last commit

Change-Id: I5b6557cf229f1d8913dffcfb3ab06a1bdada8cd5

1]. For the same ASN as Global ASN, the range is b/w 1-8000000
2]. For different ASN, the range is b/w 1-4294967295

Change-Id: I3945496696f9fbc84180f0df60fe4e117bec22dd

An ARP request/response packet with zero source IP address need to be
treated as Gratuitous ARP packet. This test case verifies that ARP
packets with all zeros as source IP are recieved by the VMs present on
different compute nodes.
This test case verifies the issue1513793.

Change-Id: Ib35efdb739691f52b453b477ee56a3277edcbc06

  - Added testcases for checking ecmp hash updation
  - Testcases for checking hash precedence
  - Testcases for in-network, in-network-nat and transparent
  - Testcases for services restart along with hash updation

Change-Id: I19326ab595b56ef5cd043e8b4f8902715257329f
Closes-Bug: #1575482

* Correct the broken call to create_port() in neutron/base.py
* While adding a host route in subnet, use the right IP

Change-Id: I096cf9a8d5bb517f71a80dbe708040f16a5cb979

This will change contrail-test code to split in two repos -
contrail-test and contrail-test-ci

contrail-test-ci : this repo contain all common code and stable test
code which can be released to the customer environments.
contrail-test: This repo contain rest of the testcases.

Note: At this moment contrail-test still contain some common code which
may need to be refactored later

closes-Bug: 1577713

Change-Id: I2e41452d417635ac224a39d75bc0dd2858e7d74d

Change-Id: I10b38e993087d6acd63294802e4ed85823d7fc05

…nning testcase

change test module to test_v1
Change-Id: I026622592c63fa3f3d10cae702608aba5e5b5513

Incorporated review comments

Change-Id: I1aa5b71509c8eb029f82d5e5c1edf2393e9843ee

cluster

 - Present script will be split into 2 classes. 1st will work on both
   control and mx(inherently it will test DM). The new class will run
   only on control nodes without configuring mx at all, even if present in
   the topology. This is done to accomodate running md5 tests with the
   constraint that mx DM can only work with one cluster at a time.

Change-Id: Ie520e6c7b0213355f6998620fc6e2aee0c15e1d2
Closes-Bug: #1465219

    Adding intf mirroring tests for the following :
        -src vm in vn1, mirror vm in vn1, and dst vm in vn2
        -src vm in vn1, mirror vm in vn3, and dst vm in vn2
        -src vm, dst vm and mirror vm all are in vn1
        -src vm in vn1, dst vm in vn2, and mirror vm in vn2

Each of below test cases (compute node combinations) has above 4 VN combinations : Total 20

Sanity:

test_intf_mirroring_1:  src vm, dst vm and analyzer vm on different CNs

Regression :

test_intf_mirroring_2: src vm, dst vm and analyzer vm on same CN

test_intf_mirroring_3: src vm, dst vm on same CN and analyzer vm on different CN

test_intf_mirroring_4:  src vm, analyzer on same CN and dst vm on different CN

test_intf_mirroring_5: dst vm, analyzer vm on same CN and src vm on different CN

Change-Id: Id35d988e820c89334c06ccb4f69e6d71f52dff96

…fore running testcase" into R3.0

…nto R3.0

Currently, default DNS records for VMs are being searched in
first control node. This is not a right approach as records are
saved in control node assigned by discovery server.
Thus, we need to search for associated DNS server with that
agent and then search for records in that Control node.
Chnage has been made in multiple test cases.

Closes-Bug: 1579740
Change-Id: I709d8b8aca271e0ab8b3faf9aa21a9c95f6be93b

…to R3.0

…the cluster" into R3.0

Change-Id: I0e29cd189670c3b9ad0dc1e0e61e52408db252e9

Base testcase name has changed to BaseTestCase_v1. Updatiing the same for encap test.
Change-Id: I61c8ade156f620c6b9522d1146955f24edc0952c

1]. Null check for rt in the RTGroup Table

Change-Id: I0034ea6081b7886c4bdd12e9bf5f80cae62988a3

Change-Id: Ie40bb63881fe8565d58d541fd4a170af56ec28ad

Change-Id: Ide68fdb03cf783da3d9d33adf8f0f60ce254b1e2

Change-Id: I8ea450399f33524d21bd7daf38fcbf38e60259b8

Change-Id: I0f07fd49d7d01b3ea146e02469d5fb9254985746

…ver" into R3.0

…r checking ecmp hash updation - Testcases for checking hash precedence - Testcases for in-network, in-network-nat and transparent - Testcases for services restart along with hash updation" into R3.0

…nto R3.0

Change-Id: I6275823402e381198a9472500973919372790be3

…R3.0

Computing next hop id proeprly for fetching flow record to handle
single node scenario

Change-Id: Ia6aeb527e7e1ebafd3a303b27f13d1b1cb97f659

between 2 flows. This correction addresses that change.

The tollerence level upper limit is being changed from 10%
to 40% in case of max vrouter flows configured. This is in
conjuction to the fact that 20-30 extra flows are acceptable
than the upper % limit set on the vrouter.

Change-Id: I2397406f8d0430314f906e0764790825fb4440e9

  - Added basic testcases for checking xmpp auth status
  - Testcases for checking server vs agent auth precedence
  - Testcases for adding/ deleting auth.

Change-Id: I379a2993f6a0dc883741fd4bf67c5856d5f7f52f
Closes-Bug: #1565411