Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
JIRA: SNAPS-10
Change-Id: Ice08276f683445c6eebcd28e2badc25135545fd4
Signed-off-by: spisarski <s.pisarski@cablelabs.com>
|
|
- updating RPM version numbers for Euphrates
- renaming ovs scenario to ovs_dpdk
JIRA: APEX-434
Change-Id: I75e1d96bd613ea04e2ffd12bd41b3a536ff75d7f
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
- updating docs to reference Euphrates
- removing the odl_l2-nofeature scenario, it's obsolete
- renameing odl_l3 to odl, it's default for odl now
- adding symlinks to files to _l3 files so CI doesn't break
will remote those once CI is updated to use new names
Change-Id: I9f2646fc5dac443042c5f4be8cca7d2df5dca663
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
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>
|
|
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>
|
|
|
|
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>
|
|
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>
|
|
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>
|
|
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"
|
|
|
|
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>
|
|
<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>
|
|
Change-Id: I78bbc34aff1d00b4113cfb2ebedf7e24e317a358
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
|
|
|
|
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>
|
|
project.
Change-Id: I8a7ee68690156fd12f36baaf72774e2eb711312c
Signed-off-by: spisarski <s.pisarski@cablelabs.com>
|
|
Change-Id: I3cba4df26b9c533cc408c0482cbeaae292960ee5
Signed-off-by: spisarski <s.pisarski@cablelabs.com>
|
|
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>
|
|
- 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>
|
|
Change-Id: I602279b30b035cfc667e4ee9b83905a638440abb
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Change-Id: Ib03728e8ffe9c65044b32b4348e9c1c88862c6e3
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
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>
|
|
- increasing required test coverage to 90%
- also consolidating some repeated code into functions
Change-Id: I6b582478c509c24fce43224a516414e1ead6c8e4
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
|
|
Change-Id: Ice02b4eabffc49f47185978b5068676ef095a647
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
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>
|
|
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>
|
|
Change-Id: I983f4483b328268413d4ec66c753f1219d59fd27
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
|
|
Change-Id: Ib7fc4e9ca543a4c678576ea2119fa606ece0095c
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
JIRA: APEX-222
Change-Id: I435852fbe1597bf03f617dc14a6718de699b648f
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
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>
|
|
|
|
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>
|
|
Apex Brahmaputra as I have had many issues getting a Colorado environment up and running."
|
|
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>
|
|
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>
|
|
- syntax updates to match pep8 standards
- tests to cover apex_python_utils.py
Change-Id: Ifac06fdbb97266f1b574b20610979b6965d6dd55
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Change-Id: If6a8366dec49cff85ba94c13e70a1796e7b6ca47
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I54205d217807fd5499a71571ef8bed7c684fe944
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Change-Id: Iececedb03a60dd0bfc1ad6ef1275f6a0427350eb
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Change-Id: Ibaf20a2960a9f4b5e3f256fbed12a61d7606a967
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
- 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>
|