summaryrefslogtreecommitdiffstats
path: root/tests
AgeCommit message (Collapse)AuthorFilesLines
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>