summaryrefslogtreecommitdiffstats
path: root/config/network
AgeCommit message (Collapse)AuthorFilesLines
2017-03-12Add support for odl_l3-fdioFeng Pan1-4/+2
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> (cherry picked from commit 7d994a3c3e18227c26bf58049e4d5780144ecf98)
2017-03-09Adding "Real Time KVM" supportdavidjchou1-5/+5
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>
2017-02-18Add support for odl-fdio scenarioFeng Pan1-0/+221
Changes: - Kernel parameters are now set through first-boot.yaml during deployment. No custom images will be built. Note that all nodes will be configured the same way, we only use compute's kernel parameter settings currently (from deploy settings file) - Add support for VPP interface type in network settings file, it is now possible to specify vpp_interface type and uio_driver for tenant nic in network settings file. A new example config, network_settings_vpp.yaml is added. - Add support for odl_l2-fdio scenario. Limitations: - Physical NIC names must be specified in network settings file, numbered nic names such as nic1 are not supported for fdio scenarios. - The same kernel parameters will be configured for all nodes. The paramters will be taken from compute kernel parameter section in deploy settings file. opnfv-tht-pr: 104 opnfv-puppet-tripleo-pr: 12 os-net-config-pr: 3 Change-Id: Ie9d6151e6e58d11da3c66fbcabe4a0886c3fa152 Signed-off-by: Feng Pan <fpan@redhat.com>
2016-12-02Fixes using single network (previously called flat) for deployTim Rozet3-0/+6
Also contains various network parsing fixes. JIRA: APEX-361 Change-Id: I5e40ed67267d5ded85adc2982a8726ebbceaeae5 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-11-29Renames 'usable_ip_range' to 'overcloud_ip_range'Tim Rozet3-12/+12
'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>
2016-10-25Clarifies ip ranges in network settingsTim Rozet3-68/+59
Also includes other various fixes. JIRA: APEX-292 Change-Id: I5e8cedce5af43544963c1e7de582e7646b1c841a Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-10-20Revert "Add ability to configure allowed vlan ranges in deploy configuration"Dan Radez1-1/+0
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>
2016-10-17Add ability to configure allowed vlan ranges in deploy configurationPeng Liu1-0/+1
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>
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>