summaryrefslogtreecommitdiffstats
path: root/config/network
AgeCommit message (Collapse)AuthorFilesLines
2016-09-22migrating to proposed common network settings fileDan Radez3-306/+568
- 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-31IPv6 fixes for network settings and post deployFeng Pan1-0/+18
This patch contains the following: - Add dns and nic information in network settings file - Add ipv6 option for find_ip function in common-functions.sh - Change neutron commands to handle IPv6 during post deploy, skip NAT configuration if IPv6 is configured. - Fix an error in python library when generating floating ip range. JIRA: APEX-130 Change-Id: I27da7f7a714f42ee827be7091fcb1a6d89a0aae8 Signed-off-by: Feng Pan <fpan@redhat.com>
2016-07-19Allows specifying domain name for overcloud/undercloudTim Rozet1-0/+3
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>
2016-07-18Allows specifying nic order for overcloud nodes in network settingsTim Rozet1-0/+10
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-06-28Adding VLAN supportDan Radez2-1/+105
JIRA: APEX-136 JIRA: APEX-30 Change-Id: I7cbbe11f4c1f1455dba253733c78fe8dc215de97 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-06-14Add IPv6 network settings file.Feng Pan1-0/+123
JIRA: APEX-130 Change-Id: Ic00c36b84de274b43c2555108d78aef307a85499 Signed-off-by: Feng Pan <fpan@redhat.com>
2016-06-08Enabling DNS server assignment in entwork settingsDan Radez1-0/+3
Change-Id: Ibb30129ca52392cd152b6af61e0545ba47153bda Signed-off-by: Dan Radez <dradez@redhat.com>
2016-03-23updating vm creation for virt deploymentDan Radez1-0/+100
- 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>