Ensure puppet dns config done after networking config
In some labs, the puppet manifest application during
config_controller results in the ::platform::network class
being applied after the ::platform::dns class. This causes the
/etc/resolv.conf file to be wiped (when the
apply_network_config.sh is run by the ::platform::network
class).
The fix is to introduce a dependency to ensure that the
networking config is completed before the dns config is done.
In kubernetes deployments, a DNS server is required to locate
the registry servers used to download the kubernetes images.
Currently, when config_controller is run, the 8.8.8.8
nameserver is used, with no way to change it. Some users
need to specify their own name server to be used during
the execution of config_controller.
This change allows the user to specify up to three DNS
servers when running config_controller interactively or with
a config file. If using a config file, add the following
section to the config file (only one nameserver is required,
but up to three are allowed):
commit f0b393f30952aa226976c33b9ff9241283fab207
Author: Kevin Smith <email address hidden>
Date: Thu Jan 17 07:09:35 2019 -0500
Kubernetes Neutron VIM Host Management Refactoring
Rework neutron system host management to operate on agent states
rather than an extended host entity, as it was agreed with the
neutron team that a new host level entity was not desired in the
neutron core.
This commit modifies the neutron override values to accommodate
the above.
Current config_controller for containerization pulls kubernetes
images from public container registry. This requires controller
to access internet. If a host network is behind a proxy, there
is no chance to setup docker proxy configuration during config_
controller, therefore, kubernetes images are not accessible.
Docker proxy configuration questions were added to require users
input http/https proxy and no proxy settings. The docker proxy
configurations are added to service_parameter table in sysinv.
http-proxy.conf is the proxy info file required by docker daemon,
generated by docker puppet manifest. It consists of the user
input docker proxy configuration.
Tests:
AIO-SX: public k8s images accessible
AIO-DX: public k8s images accessible
AIO-SX without k8s config: config_controller successfully
Support 'True' and 'False' input for system commands
add args choice 'True' and 'False' for https_enabled and sdn_enabled
in 'system modify' and for dynamic in 'system network-add' command
to support input 'True' and 'False'.
make https_enabled and sdn_enabled to lower case in sys-api controller
commit 1a502b9151fadb93ae6fdc667a72f978133ed9e5
Author: John Kung <email address hidden>
Date: Thu Jan 17 21:55:19 2019 -0500
Create DataNetworks modelling in System Configuration
Introduce the DataNetwork api, client, model to allow modelling of the
physical data network, with the following attributes: datanetwork_name
mtu datanetwork_type (flat, vlan, vxlan)
VxLAN specific attributes
- port_number
- multicast_group
- ttl
- mode ('dynamic' default, or 'static')
The system data network may then be assigned to interface.
This is part of the Story to "Move neutron provider network modelling
to system configuration".
The interface api is currently made compatible with current usage to
allow specifying datanetwork (formerly providernetwork).
The following new CLI commands and corresponding api are exposed: datanetwork-add Add a datanetwork. datanetwork-delete Delete a datanetwork. datanetwork-list List datanetworks. datanetwork-modify Modify a datanetwork. datanetwork-show Show datanetwork details. interface-datanetwork-assign Assign a datanetwork to an interface. interface-datanetwork-list List datanetwork interfaces. interface-datanetwork-remove Remove an assigned datanetwork from an interface. interface-datanetwork-show Show interface datanetwork details.
'system datanetwork-add' must be run where
'neutron providernetwork-create'.
Reviewed: https:/ /review. openstack. org/633788 /git.openstack. org/cgit/ openstack/ stx-config/ commit/ ?id=23f303132c9 e69a16f2e0b1b63 483c49fcfd11a1
Committed: https:/
Submitter: Zuul
Branch: f/stein
commit 3cc2f5e1fb70159 473eefe4e5141db 4eab8c92b0
Author: Al Bailey <email address hidden>
Date: Mon Jan 28 09:50:25 2019 -0600
Change version of python-ldap to work with new setuptools
setuptools 40.7.0 does not work with python-ldap 2.5.2
Added unit tests to verify the code calling the python-ldap
functions.
Closes-Bug: 1813668 4d2e03032282e26 8cb2189775d
Change-Id: I1e5c0bb7ec603d
Signed-off-by: Al Bailey <email address hidden>
commit c4f63232dc88bd8 eae5698b104011c bc7d7f98ea
Author: Bart Wensley <email address hidden>
Date: Mon Jan 28 13:17:00 2019 -0600
Ensure puppet dns config done after networking config
In some labs, the puppet manifest application during controller results in the ::platform::network class resolv. conf file to be wiped (when the network_ config. sh is run by the ::platform::network
config_
being applied after the ::platform::dns class. This causes the
/etc/
apply_
class).
The fix is to introduce a dependency to ensure that the
networking config is completed before the dns config is done.
Change-Id: Ie4a8b67e5eb359 4f5c21e22f8014d 2b8162a0758
Related-bug: 1812449
Signed-off-by: Bart Wensley <email address hidden>
commit de474bc41c2691b a86b60bb6e1088d dc382deaa3
Author: Bart Wensley <email address hidden>
Date: Thu Jan 24 16:33:41 2019 +0000
Revert "Add docker proxy configuration for kubernetes".
This change broke the installation of kubernetes system (config_controller --kubernetes) when no docker proxy was specified.
This reverts commit e4086a073b7f661 d4014061f255251 20c27ea679.
Change-Id: I8343741a50fa08 57fde9dfe0ee8f8 1de80a0ff13
commit d96ce5291c78c37 1e132813a514a1f b6e0994850
Author: Bart Wensley <email address hidden>
Date: Thu Jan 24 07:22:05 2019 -0600
Allow DNS server configuration for kubernetes
In kubernetes deployments, a DNS server is required to locate
the registry servers used to download the kubernetes images.
Currently, when config_controller is run, the 8.8.8.8
nameserver is used, with no way to change it. Some users
need to specify their own name server to be used during
the execution of config_controller.
This change allows the user to specify up to three DNS
servers when running config_controller interactively or with
a config file. If using a config file, add the following
section to the config file (only one nameserver is required,
but up to three are allowed):
[DNS] 1=8.8.8. 8 2=8.8.4. 4 3=9.9.9. 9
NAMESERVER_
NAMESERVER_
NAMESERVER_
Change-Id: I59556138a11c6f 627f45886a2da6b 8a1ad9d89e1
Closes-bug: 1812449
Signed-off-by: Bart Wensley <email address hidden>
commit f0b393f30952aa2 26976c33b9ff924 1283fab207
Author: Kevin Smith <email address hidden>
Date: Thu Jan 17 07:09:35 2019 -0500
Kubernetes Neutron VIM Host Management Refactoring
Rework neutron system host management to operate on agent states
rather than an extended host entity, as it was agreed with the
neutron team that a new host level entity was not desired in the
neutron core.
This commit modifies the neutron override values to accommodate
the above.
Story: 2003857 d17abafe337af71 d0caf9c40da
Task: 26669
Depends-On: I441fcf3c186f68
Change-Id: I85943d5b6f421f 4ef379694f21ad2 d758bb5f38a
Signed-off-by: Kevin Smith <email address hidden>
commit 386750136ccdb9d 2b8240ccf68fc0f 0258824939
Author: Sun Austin <email address hidden>
Date: Thu Jan 24 10:10:05 2019 +0800
[Devstack] remove etc/sysinv/ crushmap. bin install in devstack
https:/ /review. openstack. org/#/c/ 629512/ removed crushamp.bin
so remove this bin file in devstack accordingly.
Depends-on: https:/ /review. openstack. org/632897 a2b3a6a5fb11436 0361429e664
Change-Id: I743dd6de2c5351
Signed-off-by: Sun Austin <email address hidden>
commit e4086a073b7f661 d4014061f255251 20c27ea679
Author: Mingyuan Qi <email address hidden>
Date: Thu Jan 17 22:42:50 2019 +0800
Add docker proxy configuration for kubernetes
Current config_controller for containerization pulls kubernetes
images from public container registry. This requires controller
to access internet. If a host network is behind a proxy, there
is no chance to setup docker proxy configuration during config_
controller, therefore, kubernetes images are not accessible.
Docker proxy configuration questions were added to require users
input http/https proxy and no proxy settings. The docker proxy
configurations are added to service_parameter table in sysinv.
http-proxy.conf is the proxy info file required by docker daemon,
generated by docker puppet manifest. It consists of the user
input docker proxy configuration.
Tests:
AIO-SX: public k8s images accessible
AIO-DX: public k8s images accessible
AIO-SX without k8s config: config_controller successfully
Story: 2004710
Task: 28741
Change-Id: I9d301d105f9fe5 e388a29dee03957 514b9b44fa7
Signed-off-by: Mingyuan Qi <email address hidden>
commit 2b2782efb6ea2ef c4816fe67287c8a 0515916352
Author: sunausti <email address hidden>
Date: Mon Jan 21 01:04:02 2019 +0000
Support 'True' and 'False' input for system commands
add args choice 'True' and 'False' for https_enabled and sdn_enabled
in 'system modify' and for dynamic in 'system network-add' command
to support input 'True' and 'False'.
make https_enabled and sdn_enabled to lower case in sys-api controller
Closes-bug: 1812268
Change-Id: If6411852edfc97 0ee1d749e4d4ccb 8d045767bbc
Signed-off-by: sunausti <email address hidden>
commit 1a502b9151fadb9 3ae6fdc667a72f9 78133ed9e5
Author: John Kung <email address hidden>
Date: Thu Jan 17 21:55:19 2019 -0500
Create DataNetworks modelling in System Configuration
Introduce the DataNetwork api, client, model to allow modelling of the
datanetwork_ name
datanetwork_ type (flat, vlan, vxlan)
physical data network, with the following attributes:
mtu
VxLAN specific attributes
- port_number
- multicast_group
- ttl
- mode ('dynamic' default, or 'static')
The system data network may then be assigned to interface.
This is part of the Story to "Move neutron provider network modelling
to system configuration".
The interface api is currently made compatible with current usage to
allow specifying datanetwork (formerly providernetwork).
The following new CLI commands and corresponding api are exposed:
datanetwork- add Add a datanetwork.
datanetwork- delete Delete a datanetwork.
datanetwork- list List datanetworks.
datanetwork- modify Modify a datanetwork.
datanetwork- show Show datanetwork details.
interface- datanetwork- assign
Assign a datanetwork to an interface.
interface- datanetwork- list
List datanetwork interfaces.
interface- datanetwork- remove
Remove an assigned datanetwork from an interface.
interface- datanetwork- show
Show interface datanetwork details.
'system datanetwork-add' must be run where -create' .
'neutron providernetwork
Tests Performed:
AIO Sanity
Sanity 2-controller, 2-compute
Sanity Storage lab
Interface Profile create and apply
Containers deployment
Change-Id: I630f90768647db b414a60978bf8f8 f641496afd5
Story: 2004455
Task: 28324
Signed-off-by: John Kung <email address hidden>