ac8d5919d8
We introduce a new ServiceNetMap resource which enables some more flexible mappings between the services and their networks. Specifically this patch means: 1. ServiceNetMap no longer has to specify the entire list of all services, operators may if they wish, but a subset is now valid where you want to accept the defaults for some services (the defaults are now accessible via the ServiceNetMapDefaults parameter. 2. We can map some keys which don't fit a pattern that enables conversion from CamelCase to snake_case which is required for compatibility with the service_names in puppet/services* This should be backwards compatible, and in future when we remove internal dependency on the CamelCase names, we could also enable operators to specify e.g heat_api_network in ServiceNetMap which would be more consistent. Change-Id: Ib60198adf76bb69ffbafbfac739e356d153f6194 Partially-Implements: blueprint custom-roles |
||
|---|---|---|
| .. | ||
| README.md | ||
| update-from-keystone-admin-internal-api.yaml | ||
| update-from-overcloud-compute-hostnames.yaml | ||
| update-from-publicvip-on-ctlplane.yaml | ||
This directory contains Heat environment file snippets which can be used to ensure smooth updates of the Overcloud.
Contents
update-from-keystone-admin-internal-api.yaml To be used if the Keystone Admin API was originally deployed on the Internal API network.
update-from-publicvip-on-ctlplane.yaml To be used if the PublicVirtualIP resource was deployed as an additional VIP on the 'ctlplane'.