starlingx/config
Code Issues Proposed changes

ipv6 cluster networking support

Browse Source 
Addresses several issues with deploying IPv6 based network deployments:
  - kubelet node IP assignment for IP version detection
  - calico upversion to fix router ID generation from hash
  - calico configuration specific to IPv6
  - multus configuration specific to IPv6
  - ansible bootstrap playbook updates to wrap IPv6 addresses
  - ansible bootstrap updated to use Jinja2 templates
  - puppet configuration for platform services with IPv6 addresses
  - IPv4 and IPv6 IP forwarding sysctl setup
  - docker registry does not support URL encoded IPv6
  - armada does not support IPv6 address binding

NOTE:
The Puppet ERB templates were updated to maintain config_controller
functionality, but the files moved to Jinja2 templates should be removed
once config_controller is completely removed.

Change-Id: I815035c679e61250099c74b1239f19bcc72733a0
Depends-On: https://review.opendev.org/662292
Closes-Bug: #1830779
Signed-off-by: Matt Peters <matt.peters@windriver.com>
This commit is contained in:
Matt Peters
2019-05-28 14:29:49 -04:00
parent 4976f20b54
commit b2f66d01ac
39 changed files with 1458 additions and 261 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
controllerconfig/controllerconfig/scripts/controller_config
View File

@@ -288,11 +288,9 @@ start()
fatal_error "Unable to copy $CONFIG_DIR/registry-cert.crt to certificates dir"
fi
# this is management network for now
REGISTRY_IP=$(get_ip controller)
mkdir -p /etc/docker/certs.d/$REGISTRY_IP:9001/
chmod 700 /etc/docker/certs.d/$REGISTRY_IP:9001/
cp $CONFIG_DIR/registry-cert.crt /etc/docker/certs.d/$REGISTRY_IP:9001/registry-cert.crt
mkdir -p /etc/docker/certs.d/registry.local:9001/
chmod 700 /etc/docker/certs.d/registry.local:9001/
cp $CONFIG_DIR/registry-cert.crt /etc/docker/certs.d/registry.local:9001/registry-cert.crt
if [ $? -ne 0 ]
then
fatal_error "Unable to copy $CONFIG_DIR/registry-cert.crt to docker dir"