6b4d841d91
In spine-and-leaf TLS-e deployments as done in OSP13,
services are filter based on role networks when adding
metadata for nova-join. This filtering removes valid
services due to the fact that the roles network does'nt
match the global ServiceNetMap.
Add a role based parameter {{role.name}}ServiceNetMap
that can be used to override the ServiceNetMap per-role
when it's being passed to {{role.name}}ServiceChain and
the {{role.name}} resource group.
Related: RHBZ#1875508
Closes-Bug: #1904482
Change-Id: I56b6dfe8a0e95385e469d9eac97a0ec24e147450
(cherry picked from commit be6a844a79)
22 lines
975 B
YAML
22 lines
975 B
YAML
---
|
|
fixes:
|
|
- |
|
|
When deploying a spine-and-leaf (L3 routed architecture) with TLS enabled
|
|
for internal endpoints the deployment would fail because some roles are
|
|
not connected to the network mapped to the service in ServiceNetMap. To
|
|
fix this issue a role specific parameter ``{{role.name}}ServiceNetMap`` is
|
|
introduced (defaults to: ``{}``). The role specific ServiceNetMap parameter
|
|
allow the operator to override one or more service network mappings
|
|
per-role. For example::
|
|
|
|
ComputeLeaf2ServiceNetMap:
|
|
NovaLibvirtNetwork: internal_api_leaf2
|
|
|
|
The role specific ``{{role.name}}ServiceNetMap`` override is merged with
|
|
the global ``ServiceNetMap`` when it's passed as a value to the
|
|
``{{role.name}}ServiceChain`` resources, and the ``{{role.name}}``
|
|
resource groups so that the correct network for this role is mapped to
|
|
the service.
|
|
|
|
Closes bug: `1904482 <https://bugs.launchpad.net/tripleo/+bug/1904482>`_.
|