summaryrefslogtreecommitdiffstats
path: root/build/nics-template.yaml.jinja2
AgeCommit message (Collapse)AuthorFilesLines
2016-12-02Fixes using single network (previously called flat) for deployTim Rozet1-3/+3
Also contains various network parsing fixes. JIRA: APEX-361 Change-Id: I5e40ed67267d5ded85adc2982a8726ebbceaeae5 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-09-22migrating to proposed common network settings fileDan Radez1-18/+18
- 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>
2016-07-19Merge "Allows specifying nic order for overcloud nodes in network settings"Dan Radez1-9/+8
2016-07-18Allows specifying nic order for overcloud nodes in network settingsTim Rozet1-9/+8
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-15Fixes public vlan network settingsTim Rozet1-1/+1
JIRA: APEX-201 Change-Id: I3ba8d5e38e203bb4f23679a3b91de97c591de146 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-07-13correction to a conditional in nic templateDan Radez1-1/+1
Change-Id: Ibed808350163379fcfa5178c78fabe2f47e491fc Signed-off-by: Dan Radez <dradez@redhat.com>
2016-06-30Fixes nic template renderingTim Rozet1-5/+16
Issue where in default network_settings, api_network is not specified. This means that the settings do not have api_network in its output, but the nic template checks to see if api_network vlan is native in its logic. This patch assumes a vlan will be numeric. A blank value or a value of 'native' will not be numeric therefore default is expanded to allow blank values as non-vlan networks. Also fixes controller to always have br-ex. Change-Id: Ibebb231901e653127175aef194eec708e8507da2 Signed-off-by: Tim Rozet <trozet@redhat.com> Signed-off-by: Dan Radez <dradez@redhat.com> Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-06-28Fixes multiple issues in ovs dpdkTim Rozet1-1/+1
Changes include: - Fixes nova schedulers to be an array instead of string - Fixes os-net-config to only run one time with dpdk nodes - Fixes br-phy creation to only happen on compute nodes opnfv-tht-pr: 32 Change-Id: Ic3ef9ba247535ed00e40fe3fc4f0e78ac7d01c1a Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-06-28Fixes IP failure during os-collect-config ping checkTim Rozet1-5/+6
Moves the (to be) dpdk interface to br-phy so that the ping check passes after os-net-config. The puppet then moves the interface off of br-phy before binding to dpdk. opnfv-tht-pr: 31 Change-Id: I803671831ea5fd2665a7fa1368a7175d3e0a845d Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-06-28Adding VLAN supportDan Radez1-0/+237
JIRA: APEX-136 JIRA: APEX-30 Change-Id: I7cbbe11f4c1f1455dba253733c78fe8dc215de97 Signed-off-by: Dan Radez <dradez@redhat.com>