77c82f6645
The subnet property is added to puppet/role.role.j2.yaml as
`{{role}}ControlPlaneSubnet`. Roles with a different subnet specified
can be used to deploy a routed network architecture by using one
role per routed network.
When enabling the neutron segments plug-in to support routed-networks
the neutron IPAM code will defer ipallocation unless the port create
request contain enough details. (Ref: LP Bug: #1695740) By adding the
subnet to port create request this change enables tripleo deployment
on an undercloud with Neutron segments plug-in and routed networks.
This depends on a Heat change that improves network logic in server
resource to not replace the current port if new props match what is
on the current interface. Without this adding the subnet property on
update/upgrades would cause a port replacement, which in turn would
cause IPAM info in undercloud neutron to miss-match the deployed
overcloud nodes.
Depends-On: Iab75ec49b962617943017dcaf1b04b89f91a982e
Change-Id: I33804bfd105a13c25d6057e8414e09957939e8af
Implements: blueprint tripleo-routed-networks-deployment
34 lines
683 B
YAML
34 lines
683 B
YAML
heat_template_version: queens
|
|
|
|
parameters:
|
|
network:
|
|
type: string
|
|
default: ctlplane
|
|
name:
|
|
type: string
|
|
replacement_policy:
|
|
type: string
|
|
default: AUTO
|
|
ControlPlaneSubnet:
|
|
default: ctlplane-subnet
|
|
description: The name of the undercloud Neutron control plane subnet
|
|
type: string
|
|
|
|
resources:
|
|
|
|
ControlPlanePort:
|
|
type: OS::Neutron::Port
|
|
properties:
|
|
network: ctlplane
|
|
fixed_ips: [{subnet: {get_param: ControlPlaneSubnet}}]
|
|
name:
|
|
list_join:
|
|
- '-'
|
|
- - {get_param: name}
|
|
- port
|
|
replacement_policy: AUTO
|
|
|
|
outputs:
|
|
fixed_ips:
|
|
value: {get_attr: [ControlPlanePort, fixed_ips]}
|