2793ab34d2
Currently, we have a problem because the unregistration happens in the "post deploy" phase, which works fine when the top-level stack is being deleted, but not when the ResourceGroup of servers is being scaled down, because then the normal "post deploy" update ordering is respected and we try to unregister after the corresponding server has been deleted. So, instead, register/unregister each node inside the unit of scale, e.g the role template being scaled down, which is possible via the new NodesExtraConfig interface, which means unregistration will take place at the right time both on stack delete and on scale-down. Change-Id: I8f117a49fd128f268659525dd03ad46ba3daa1bc
23 lines
612 B
YAML
23 lines
612 B
YAML
# Note this can be specified either in the call
|
|
# to heat stack-create via an additional -e option
|
|
# or via the global environment on the seed in
|
|
# /etc/heat/environment.d/default.yaml
|
|
parameter_defaults:
|
|
rhel_reg_activation_key: ""
|
|
rhel_reg_auto_attach: ""
|
|
rhel_reg_base_url: ""
|
|
rhel_reg_environment: ""
|
|
rhel_reg_force: ""
|
|
rhel_reg_machine_name: ""
|
|
rhel_reg_org: ""
|
|
rhel_reg_password: ""
|
|
rhel_reg_pool_id: ""
|
|
rhel_reg_release: ""
|
|
rhel_reg_repos: ""
|
|
rhel_reg_sat_url: ""
|
|
rhel_reg_server_url: ""
|
|
rhel_reg_service_level: ""
|
|
rhel_reg_user: ""
|
|
rhel_reg_type: ""
|
|
rhel_reg_method: ""
|