diff options
| author |   Tim Rozet <trozet@redhat.com> | 2016-07-15 22:04:24 -0400 |
|---|---|---|
| committer | Tim Rozet <trozet@redhat.com> | 2016-07-18 16:35:00 -0400 |
| commit | 1f5bede73d99f89a3cf1ec5fae7b30cee454b6c8 (patch) | |
| tree | 79e4e8afde0585c07a98c770b79450d4dd24b8fb /lib/python/apex/common/constants.py | |
| parent | 88d5b2462933cce79cb059c81e007ec83ee2cd9e (diff) | |
Allows specifying nic order for overcloud nodes in network settings
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>
Diffstat (limited to 'lib/python/apex/common/constants.py')
| -rw-r--r-- | lib/python/apex/common/constants.py | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/lib/python/apex/common/constants.py b/lib/python/apex/common/constants.py index 8ed49ff7..dfed33f8 100644 --- a/lib/python/apex/common/constants.py +++ b/lib/python/apex/common/constants.py @@ -15,3 +15,4 @@ API_NETWORK = 'api_network' OPNFV_NETWORK_TYPES = [ADMIN_NETWORK, PRIVATE_NETWORK, PUBLIC_NETWORK, STORAGE_NETWORK, API_NETWORK] DNS_SERVERS = ["8.8.8.8", "8.8.4.4"] +ROLES = ['compute', 'controller'] |