Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
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>
|
|
JIRA: APEX-141
Change-Id: I9983ec5583100b7c536524a01e64bb6884b38d1d
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
JIRA: APEX-201
Change-Id: I3ba8d5e38e203bb4f23679a3b91de97c591de146
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Ibed808350163379fcfa5178c78fabe2f47e491fc
Signed-off-by: Dan Radez <dradez@redhat.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>
|
|
* changes:
Fixes IP failure during os-collect-config ping check
Adding VLAN support
|
|
JIRA: APEX-136
JIRA: APEX-30
Change-Id: I7cbbe11f4c1f1455dba253733c78fe8dc215de97
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
JIRA: APEX-133
opnfv-tht-pr: 29
Change-Id: I3080c91c3995ed946b902a75907ef11cb349fc33
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
JIRA: APEX-177
Change-Id: I6ee95a3c525fb58699fb3af795a66639f217214c
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-119
Change-Id: Ia66f2ef4c169187b0cb575b10292d02f530b9902
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
Change-Id: I8db0cc0f715e95414e20f8a1e4d49f8d77e7b9ae
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Change-Id: I3936eae693ab8bea8de3826653aad6081ddc8d96
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Changes include:
- Minor syntax fix to dataplane check
- Adds 'odl_version' to deploy options
- Builds ODL overcloud image with boron rpm included
- If user specifies 'boron' as odl_version then, package is upgraded on
overcloud image
Change-Id: I37436cb8cc4d6cff1fede6c13836f26a4cc57f49
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
Adds the dataplane deploy option, which can have values of
ovs, ovs_dpdk, or fdio. Currently does nothing
JIRA: APEX-119
Change-Id: I6c14a9c9d6887a325525d634052ea8300b30ee57
Signed-off-by: Michael Chapman <woppin@gmail.com>
|
|
Change-Id: Ibb30129ca52392cd152b6af61e0545ba47153bda
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Change-Id: Iececedb03a60dd0bfc1ad6ef1275f6a0427350eb
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
- Create additional NIC on virtual deployment if API network is enabled.
- Include API network in clean
- Change keystone admin api network to admin network. This should have
no effect when api network is disabled, as today's behavior is to
fall back to admin network anyway. However, when api network is
defined, we need to be able to reach overcloud from undercloud through
keystone admin api network.
Change-Id: Ib0aea4a0daeed5878793530c10d8f8a1bbe5fd72
Signed-off-by: Feng Pan <fpan@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>
|
|
Change-Id: I61efdac14066d2a3d7c3e3ff7f93f0fa2af3a857
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Add support for CPU pinning of libvirt guests and also
restricting host processes to selected CPUs via isolcpus.
Hugepage support is added using the same mechanism as
isolcpus, along with a perf scenario where all 3 performance
options are enabled.
Deploy options are now parsed in python
JIRA: APEX-127
JIRA: APEX-105
JIRA: APEX-106
Change-Id: I438e80fb88e596cc017595d43bc1efda1001325c
opnfv-tht-pr: 8
Signed-off-by: Michael Chapman <woppin@gmail.com>
|
|
Convert compute and controller NIC templates to jinja2 format.
Added support for IPv6 for those NIC templates. Existing IPv4
template generation behavior does not change.
The .template files are kept in tree for now, they will be
removed after VLAN changes are made.
Change-Id: I2ffc7c403af3659db780ece2bd9195cd62748f0c
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Changes:
- Implements network_settings.yaml file parsing in python.
- Adds support for both IPv4 and IPv6 in network_settings.yaml
- Adds support for api_network in network_settings.yaml
- Removes bash library functions for network related functions.
- Adds dependency to python34-yaml for apex-common package.
Note that support for ipv6 and api_network is not complete yet.
Proper configuriration of network environment and nic template
files will be added later.
Change-Id: I087f725dabedfef109c9de1f58ce2611da647e87
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Changes include:
- IP utility library in python 3 that supports both IPv4 and IPv6
address generation. This library currently includes a single
function of generating IP ranges or single IP for a given CIDR.
More functionality will be added at a later time to support
features such as IP address calculation.
- Updated common-function.sh to use python library to generate IP
ranges. All existing bash functions are preserved, so any
callers will get identical IP ranges as before.
- Add dependency to python3 for opnfv-apex-common package.
- Add python dependency to build.sh
No change is made to interface related functions.
Change-Id: Idc6998754f9f3c7a3868ec5b5768f3bb5f78cd90
Signed-off-by: Feng Pan <fpan@redhat.com>
|