summaryrefslogtreecommitdiffstats
path: root/lib/python/apex/network_settings.py
AgeCommit message (Collapse)AuthorFilesLines
2017-03-09Adding "Real Time KVM" supportdavidjchou1-1/+1
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>
2016-12-20Adds declaring disk device to use on overcloud nodesTim Rozet1-6/+2
Now in inventory file a user can declare 'disk_device' which will allow the user to specify which disk on their overcloud server to use for installation. The variable can be a comma delimited list, which will search in order post-introspection for the first device on the node that exists. The default disk used will be sda for deployments. Currently defining a per node disk is not supported by OSCLI, so although defined that way in Apex inventory, only the last definition will be used for all nodes. Other changes include: - Various fixes in inventory parsing - Makes bash writing a common function - Introspection now enabled for baremetal deployments JIRA: APEX-296 Change-Id: I330d91eb17408ccfceb7a99c25edbae5ce6d848d Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-12-02Fixes using single network (previously called flat) for deployTim Rozet1-13/+15
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 Rozet1-1/+1
'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-19Use ntp parameter from network_settingsFeng Pan1-0/+3
Right now we use a ntp_server parameter set in deploy.sh, but since new network_settings file contains ntp information already, we can use those values instead. JIRA: APEX-266 Change-Id: I717af80b967971ea9111002d657972efd94a163a Signed-off-by: Feng Pan <fpan@redhat.com>
2016-10-07Fix dns server setting parsingFeng Pan1-1/+1
JIRA: APEX-294 Change-Id: I4b9aed3fc2ea35a918203a0edc995b73020d122c Signed-off-by: Feng Pan <fpan@redhat.com>
2016-09-27Removing --flat and network_isolation variablesDan Radez1-2/+1
VLAN support allows a set of nodes with a single nic to deploy removing the need for --flat. flat was not well maintained or tested. Change-Id: Ieae1c2350c83544ce50048b44300fa0b8e68dd43 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-09-22migrating to proposed common network settings fileDan Radez1-153/+163
- 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-09-20Handling file loads and tmp dirs differentlyDan Radez1-1/+1
Change-Id: I602279b30b035cfc667e4ee9b83905a638440abb Signed-off-by: Dan Radez <dradez@redhat.com>
2016-08-09Making NetworkSettings a dictDan Radez1-64/+86
Change-Id: Ib7fc4e9ca543a4c678576ea2119fa606ece0095c Signed-off-by: Dan Radez <dradez@redhat.com>
2016-07-31IPv6 fixes for network settings and post deployFeng Pan1-2/+2
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/+4
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/+48
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-30Syntax updates and new testsDan Radez1-6/+3
- syntax updates to match pep8 standards - tests to cover apex_python_utils.py Change-Id: Ifac06fdbb97266f1b574b20610979b6965d6dd55 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-06-28Adding VLAN supportDan Radez1-0/+5
JIRA: APEX-136 JIRA: APEX-30 Change-Id: I7cbbe11f4c1f1455dba253733c78fe8dc215de97 Signed-off-by: Dan Radez <dradez@redhat.com>
2016-06-17Fixes setting dns server for undercloudTim Rozet1-0/+5
JIRA: APEX-177 Change-Id: I6ee95a3c525fb58699fb3af795a66639f217214c Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-06-10Defaults dns server netenv settingsTim Rozet1-0/+3
Change-Id: I3936eae693ab8bea8de3826653aad6081ddc8d96 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-06-02Migrates network environment parsing to pythonTim Rozet1-0/+266
Change-Id: Ibaf20a2960a9f4b5e3f256fbed12a61d7606a967 Signed-off-by: Tim Rozet <trozet@redhat.com>