auto_enable_l3_ha should not be derived from ControllerCount
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Steven Hardy |
Bug Description
Right now we have the following defined in overcloud.j2.yaml:
{{role.
description: Number of {{role.name}} nodes to deploy
type: number
default: {{role.
This variable can be used to count the number of nodes for each role. For example, we have the following in puppet/
conditions:
auto_
and:
- not:
equals:
- get_param: ControllerCount - 1
- equals:
- get_param: NeutronEnableDVR
- false
With composable roles what we need is more of a per service instance count. So for example ServiceNovaApiC
The reason I need this is because in rabbitmq we want to set a policy to value equal to half the number of instances of Rabbitmq. Right now I am using ControllerCount, but that is not really correct in a composable roles architecture.
Changed in tripleo: | |
importance: | Undecided → High |
assignee: | nobody → Brent Eagles (beagles) |
We already have per-service lists of nodes in hiera, e.g see rabbitmq_node_names - so I think we should not derive service multiplicity via any of the Count parameters, and instead look at the len($service_ node_names) in puppet-tripleo?