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