summaryrefslogtreecommitdiffstats
path: root/tests
AgeCommit message (Collapse)AuthorFilesLines
2017-03-24Fixes OVS DPDK scenariosTim Rozet1-6/+3
This fixes nosdn OVS DPDK scenarios to work with OVS 2.6. It also adds support for the ODL DPDK scenario. OVS DPDK configuration is done during preconfig on compute nodes. All nodes make use of first boot script to get kernel params like hugepages. The network settings are modified to use real nic names for the virtual network settings file. This is required due to a timing bug with os-net-config and using first-boot script. The network settings file also contains the UIO driver to use with DPDK. JIRA: APEX-314 opnfv-tht-pr: 117 Change-Id: I46b6fca71ecec38981968133ba2411f64d7c6445 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-03-12Add support for odl_l3-fdioFeng Pan1-1/+2
This patch adds support for ODL L3 FDIO scenario. Introduces a new deploy settings parameter, odl_routing_node, to indicate the routing node's hostname. This parameter will only be used for this scenario. Change-Id: I8df3eb701299007761c6cec42c4ca318b124a0b8 opnfv-tht-pr: 108 os-net-config-pr: 4 Signed-off-by: Feng Pan <fpan@redhat.com> (cherry picked from commit 7d994a3c3e18227c26bf58049e4d5780144ecf98)
2017-03-10Merge "Updating repository for code containing the smoke tests"Tim Rozet1-1/+1
2017-03-09Adding "Real Time KVM" supportdavidjchou1-3/+6
Adding the support to run the "Real Time KVM" kernel in the compute node(s) to reduce the network latency caused by the virtualization of the network functions. Since the current "Real Time KVM" kernel doesn't support physical to logical network interface mapping yet, we need to use the real physical interface name rather than the logical interface name for all compute interfaces in network_settings.yaml. Also updates tests for the network settings changes and fixes a bug where interface was being queried on the controller nics before it interfaces were validated. JIRA: APEX-128 Change-Id: Iccb6c9fbdcf7e3b482f4283039ef17c38e0a6df7 Signed-off-by: davidjchou <david.j.chou@intel.com> Signed-off-by: Tim Rozet <trozet@redhat.com> Signed-off-by: Dan Radez <dradez@redhat.com>
2017-03-08Updating repository for code containing the smoke testsspisarski1-1/+1
ci/run_smoke_tests.sh is currently pulling the test code from the CableLabs repository. Now that OPNFV owns that code, we should now be sourcing that from gerrit.opnfv.org. JIRA: FUNCTEST-754 Change-Id: Ib4cd5f3596a891a94383a452eaa78c951d063bf8 Signed-off-by: spisarski <s.pisarski@cablelabs.com>
2017-01-26[BGPVPN] Remove l2 in Name; Enable ODL BoronNikolas Hermanns1-2/+2
Since Boron ODL servers always the l3 usecase so the l2 differentiation does not make sense anymore. Depends: https://gerrit.opnfv.org/gerrit/27605 Change-Id: I8bb55387001dfc81845134639ab4e913072f9a27 Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
2017-01-13Merge "Adding installation of ansible and dependencies to host attempting to ↵Tim Rozet1-1/+1
execute <apex>/ci/run_smoke_tests.sh. Also fixed the filename that contains the test stdout/stderr output from snoke-tests.out to smoke-tests.out"
2016-12-21Merge "Adds declaring disk device to use on overcloud nodes"Dan Radez1-0/+20
2016-12-20Adds declaring disk device to use on overcloud nodesTim Rozet1-0/+20
Now in inventory file a user can declare 'disk_device' which will allow the user to specify which disk on their overcloud server to use for installation. The variable can be a comma delimited list, which will search in order post-introspection for the first device on the node that exists. The default disk used will be sda for deployments. Currently defining a per node disk is not supported by OSCLI, so although defined that way in Apex inventory, only the last definition will be used for all nodes. Other changes include: - Various fixes in inventory parsing - Makes bash writing a common function - Introspection now enabled for baremetal deployments JIRA: APEX-296 Change-Id: I330d91eb17408ccfceb7a99c25edbae5ce6d848d Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-12-15Adding installation of ansible and dependencies to host attempting to executespisarski1-1/+1
<apex>/ci/run_smoke_tests.sh. Also fixed the filename that contains the test stdout/stderr output from snoke-tests.out to smoke-tests.out JIRA: APEX-373 Change-Id: I7ef68ae09c100e4e7466a10bb8e22279d9a6b41e Signed-off-by: spisarski <s.pisarski@cablelabs.com>
2016-12-14remove odl sdnvpn config fileNikolas Hermanns1-1/+2
Change-Id: I78bbc34aff1d00b4113cfb2ebedf7e24e317a358 Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
2016-11-11Merge "Migrate to stable/newton"Tim Rozet1-11/+11
2016-11-11Migrate to stable/newtonTim Rozet1-11/+11
os-odl_l2_nofeature is now deprecated since new netvirt only supports odl_l3. JIRA: APEX-299 Change-Id: I3557ecb85fa4cd11bba96aa9410e56a8e8cceb00 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-11-03Fixed smoke tests that broke during a refactor of the snaps-provisioning ↵spisarski3-17/+9
project. Change-Id: I8a7ee68690156fd12f36baaf72774e2eb711312c Signed-off-by: spisarski <s.pisarski@cablelabs.com>
2016-10-03Moved smoke test repository and changed input arguments.spisarski2-2/+2
Change-Id: I3cba4df26b9c533cc408c0482cbeaae292960ee5 Signed-off-by: spisarski <s.pisarski@cablelabs.com>
2016-09-27Removing --flat and network_isolation variablesDan Radez3-31/+30
VLAN support allows a set of nodes with a single nic to deploy removing the need for --flat. flat was not well maintained or tested. Change-Id: Ieae1c2350c83544ce50048b44300fa0b8e68dd43 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-09-22migrating to proposed common network settings fileDan Radez6-520/+183
- proposed in genesis https://wiki.opnfv.org/display/genesis/Common+Network+Settings - This patch updates the network_settings files in the config/network dir and updates the associated bash, python and python tests relative to the new yaml structure and nomenclature used in the proposed settings file JIRA: APEX-262 Change-Id: Ib0dc9d0f21465b38f2a53cff20f71fb9230bfc48 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-09-20Handling file loads and tmp dirs differentlyDan Radez2-6/+15
Change-Id: I602279b30b035cfc667e4ee9b83905a638440abb Signed-off-by: Dan Radez <dradez@redhat.com>
2016-09-07moving inventory file parsing to pythonDan Radez2-0/+68
Change-Id: Ib03728e8ffe9c65044b32b4348e9c1c88862c6e3 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-08-30Adds ability to power off nodes in cleanTim Rozet3-6/+108
Now if an inventory file is provided to clean, those nodes will be powered off. JIRA: APEX-250 Change-Id: I2d78285717726c3d1c9d7d88c38e706d4617e337 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-08-24adding more network_environment.py testsDan Radez1-3/+95
- increasing required test coverage to 90% - also consolidating some repeated code into functions Change-Id: I6b582478c509c24fce43224a516414e1ead6c8e4 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-08-24Merge "converiting the deploy settings obj to a dict"Tim Rozet1-2/+15
2016-08-24adding more test coverage for apex_ip_utils.pyDan Radez1-4/+35
Change-Id: Ice02b4eabffc49f47185978b5068676ef095a647 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-08-23converiting the deploy settings obj to a dictDan Radez1-2/+15
The deploy settings values are embedded in a dictionary inside a generic object. This patch makes the deploy settings object a dictionary so the values can be accessed directly without having to unnecessarily drill down through an empty object to the dict that holds the content intended to be managed by the deploy settings object. - adding tests to cover DeploySettings 100% Change-Id: I4ba625cd7b51cfb6c1f91c74f1d332d1e3dd9a8e Signed-off-by: Dan Radez <dradez@redhat.com>
2016-08-22removing enabled_network_list as an argument to network envDan Radez1-2/+1
NetworkSettings Object is being rendered and passed to net env object already. We can get the enabled network list from the network settings object instead of passing it in as an arg. Basically just removing duplicate arguments to the network env object. Change-Id: I828c60878a0432cae2b37c08ae1896dce49071d0 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-08-11Making NetworkEnvironment a dictDan Radez1-2/+2
Change-Id: I983f4483b328268413d4ec66c753f1219d59fd27 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-08-10Merge "Making NetworkSettings a dict"Dan Radez1-2/+2
2016-08-09Making NetworkSettings a dictDan Radez1-2/+2
Change-Id: Ib7fc4e9ca543a4c678576ea2119fa606ece0095c Signed-off-by: Dan Radez <dradez@redhat.com>
2016-08-04Fix network_isolation argparse issueFeng Pan1-1/+1
JIRA: APEX-222 Change-Id: I435852fbe1597bf03f617dc14a6718de699b648f Signed-off-by: Feng Pan <fpan@redhat.com>
2016-08-03Adds configuring vpp/hc on all nodesTim Rozet1-1/+3
Changes include: - starting vpp with pci addr of tenant nic - setting performance options for fdio scenario - creates nosdn fdio scenario (needs newtorking-vpp, etc) - starts HC if ODL is used opnfv-tht-pr: 46 JIRA: APEX-133 Change-Id: Ie7a7f1418b94dfb82255ec9aebc550a955dd696a Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-07-19Merge "Allows specifying nic order for overcloud nodes in network settings"Dan Radez5-4/+489
2016-07-18Allows specifying nic order for overcloud nodes in network settingsTim Rozet5-4/+489
Currently there is no way to specify logically or physically the nic order to be used on overcloud nodes. We always hardcode to use nic1 for admin network, nic2 for private, etc. This patch allows a user to not only decide which logical nics to use for which network, but also specify physical interface names if they need to. This is done on a per role basis, due to tripleO limitation. So a user is able to specify nic order/names for compute and controller roles separately. If a user specifies nic order, they must specify it for all networks other than admin network. We assume if admin network is unspecified it uses "nic1", so that name is reserved in this case. A user is also allowed to specify a mixture of logical and physical names, for example "nic2" and "eth3" on another network. JIRA: APEX-151 Change-Id: Ie9d4abb463cf8f8788913cb4bcf9486830adc449 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-07-15Merge "Scripts for running smoke tests on the undercloud VM. Tested against ↵Tim Rozet4-0/+34
Apex Brahmaputra as I have had many issues getting a Colorado environment up and running."
2016-07-14add onos SFC feature config filebob zhou1-1/+2
add os-onos-sfc-ha.yaml for onos sfc function deployment. opnfv-tht-pr: 27 JIRA: APEX-172 Change-Id: I07d708d201ef1d97efbfffd5aca85d8a284f7c96 Signed-off-by: bob zhou <bob.zh@huawei.com>
2016-07-06Scripts for running smoke tests on the undercloud VM.spisarski4-0/+34
Tested against Apex Brahmaputra as I have had many issues getting a Colorado environment up and running. Moved Ansible playbooks and scripts from ci/smoke_tests/ to tests/smoke_tests/ Rebase to master... Change-Id: I09273de659c76d32ccfb74a548dabf7f84c65d6d Signed-off-by: spisarski <s.pisarski@cablelabs.com>
2016-06-30Syntax updates and new testsDan Radez4-14/+95
- syntax updates to match pep8 standards - tests to cover apex_python_utils.py Change-Id: Ifac06fdbb97266f1b574b20610979b6965d6dd55 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-06-14Fixes unit testsTim Rozet1-13/+23
Change-Id: If6a8366dec49cff85ba94c13e70a1796e7b6ca47 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-06-10converting apex ip_utils unit tests to noseDan Radez7-90/+304
Change-Id: I54205d217807fd5499a71571ef8bed7c684fe944 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-06-07Enabling python coverage tests in build.shDan Radez2-9/+76
Change-Id: Iececedb03a60dd0bfc1ad6ef1275f6a0427350eb Signed-off-by: Dan Radez <dradez@redhat.com>
2016-06-02Migrates network environment parsing to pythonTim Rozet1-1/+1
Change-Id: Ibaf20a2960a9f4b5e3f256fbed12a61d7606a967 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-05-28Adding python tests and updating for conventionsDan Radez1-0/+23
- adding tests dir with a script to run python coverage - adding main funtion to python per convention - replacing underscores with dashes in CLI params per convention Change-Id: I6f64174278e2a2e93eacdb7bee09aac49ce15d29 Signed-off-by: Dan Radez <dradez@redhat.com>