From: Alexandru Avadanii Date: Tue, 2 Jan 2018 04:36:07 +0000 (+0100) Subject: Update git submodules X-Git-Tag: opnfv-6.0.0~2200 X-Git-Url: https://gerrit.opnfv.org/gerrit/gitweb?a=commitdiff_plain;h=096d01376c5681279559d45a82c3acfd4cf33f0c;p=opnfvdocs.git Update git submodules * Update docs/submodules/fuel from branch 'master' - [baremetal] Retire mas01 NAT Isolate networks by retiring NAT on mas01; also cutting direct internet access from cluster nodes that are not facing the public network (prx, cmp). NOTE: Since we are removing mas01 NAT, VCP VMs (except prx which have public IPs) and kvm nodes (cmp also have public IPs) will no longer have direct internet connectivity. Cluster deployment and operations will work without it, but if it is required for different reasons, the MaaS proxy could be enabled by uncommenting the /etc/enviroment section in: - cluster.baremetal-mcp-pike-common-ha.include.proxy.yml JIRA: FUEL-317 Change-Id: I5ed8b420296b27df34a54ec1ebd7b7cf58041425 Signed-off-by: Alexandru Avadanii - [patch] Use keystoneclient to check project ID Another prerequisite for decoupling public network from Openstack internal management network (upstream won't fix it for Pike): - port fix from [1] for using the internal network when connecting to keystone during project ID validation in nova, instead of going through public endpoint (and using SSL). [1] https://bugs.launchpad.net/nova/+bug/1716344 Change-Id: Ic9a307df9af78fcd58cbcc07b5e62a7e07cc8d7d Signed-off-by: Alexandru Avadanii - [patch] keystone: Use v3 for admin endpoint Now that v2 API is obsolete, also switch 'admin' endpoint to v3 (previously it was kept back for OCL compatibility). Change-Id: I9775d59d5e6b93d7351157f7550a0dd7114bee2f Signed-off-by: Alexandru Avadanii --- diff --git a/docs/submodules/fuel b/docs/submodules/fuel index f5a14b9a0..9a6e655e0 160000 --- a/docs/submodules/fuel +++ b/docs/submodules/fuel @@ -1 +1 @@ -Subproject commit f5a14b9a0a33ad4e76ebfdf099a544ac87fcd963 +Subproject commit 9a6e655e0b851ff6e449027c01ac1a66188b0064