c7a97ce997
Adds the external_resource_vip_id property, which can be used to set an external_id for the port resource for the network VIP. Since the same template resource, port.network.j2.yaml is used for both VIP and normal ports on a network, we can't simply add jinja to that template that conditionally adds the external_id attribute because we don't know during the jinja2 phase if the template is for a VIP or not. Instead, we need to map the VIP resources to an entirely new template resource (external_resource_port.network.j2.yaml) so that we can set the external_id attribute just for the VIP ports. Change-Id: I27d3eeb11277004b00aa4d6a66014d5c71081c26 implements: blueprint split-controlplane-templates
10 lines
498 B
YAML
10 lines
498 B
YAML
---
|
|
features:
|
|
- Adds the ability to set ``external_resource_network_id`` for the network,
|
|
``external_resource_vip_id`` for the network VIP,
|
|
``external_resource_subnet_id`` for the subnet(s), and
|
|
``external_resource_segment_id`` for the segment(s) to network_data.yaml.
|
|
When setting these properties, the external_id attribute will be set on the
|
|
corresponding Heat resources. This causes Heat to not re-create these
|
|
resources and instead adopt them from outside the stack.
|