summaryrefslogtreecommitdiffstats
path: root/lib/python/apex/network_settings.py
AgeCommit message (Collapse)AuthorFilesLines
2016-11-02Add import copy for copy(...) in network_setting.pyTomofumi Hayashi1-0/+1
In colorado branch, copy(...) in network_setting.py is failed due to missing "import ..." statement. This change is required only for colorado because master branch has been taken care of APEX-262 code change. JIRA: APEX-262 Change-Id: I5b3c9e14a980c98fd1bf387db88e5f6894511d18 Signed-off-by: Tomofumi Hayashi <tohayash@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>