Age | Commit message (Collapse) | Author | Files | Lines |
|
Also contains various network parsing fixes.
JIRA: APEX-361
Change-Id: I5e40ed67267d5ded85adc2982a8726ebbceaeae5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
'usable_ip_range' was confusing for a lot of users, and most thought it
encompassed all of the defined ranges in the network settings file (like
floating_ip_range and introspection_range). This renames it to be more
accurate.
JIRA: APEX-288
Change-Id: I2e106666df1bfd007f150279e2e0387a64cd0f48
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Also includes other various fixes.
JIRA: APEX-292
Change-Id: I5e8cedce5af43544963c1e7de582e7646b1c841a
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This reverts commit 3228f00248cda32671fb0e6a02059bea6ae66c99.
There is more settings that will need to added for the functionality this patch it intending to add. The JIRA will be updated and the feature will be worked on for Danube.
Change-Id: I258ba552cbb49e6fa188a8dffe860e8dac2e3f5f
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Add a new parameter 'vlan_id_range' for tenant vlan range, which can
set the 'network_vlan_ranges' for 'datacentre' network in ml2.ini on
both compute and controller.
Change-Id: I5c190fb2d5d582d0d5f56d4c18cf32502b758bd8
JIRA: APEX-272
Signed-off-by: Peng Liu <pliu@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>
|
|
Can be set by setting domain_name in network_settings. Defaults to
dummy opnfvapex.com.
JIRA: APEX-183
JIRA: APEX-182
Change-Id: Ib7c279a1c8432b8635f72e5cc667f16b9cd65159
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>
|
|
JIRA: APEX-136
JIRA: APEX-30
Change-Id: I7cbbe11f4c1f1455dba253733c78fe8dc215de97
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
Change-Id: Ibb30129ca52392cd152b6af61e0545ba47153bda
Signed-off-by: Dan Radez <dradez@redhat.com>
|
|
- replacing brbm with logical names br-netname
- replacing instack-virt-setup with tripleo scripts
JIRA: APEX-90, APEX-80
Change-Id: I58a15dee8de882e034c8af8a3368ca0647741b13
Signed-off-by: Dan Radez <dradez@redhat.com>
|