Network_data should dynamically render resource registry

Bug #1721038 reported by Tim Rozet on 2017-10-03
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Currently in TripleO the network_data.yaml file contains dynamic information about the definition of networks to be used in a deployment. It also includes an 'enabled' field to indicate whether or not a network is enabled. Today this information is used to render definitions of networks and ports in templates. However, it is not used to create the resource registry. This part is still required to do manually by including/modifying the network-isolation.yaml file. This creates an unnecessary step as the default resource registry could be set using network data.

This proposal is to change the rendering in overcloud.j2 and other files so that the default ports and networks will be rendered according to the network_data.yaml file. This means that a user will only have to modify the network_data file in order to declare a new network and enable isolation. If a user has some reason to override the dynamically generated resource registry, he/she will still be able to include via '-e network-isolation.yaml' to override the defaults as previously done.

Tim Rozet (trozet) on 2017-10-03
Changed in tripleo:
assignee: nobody → Tim Rozet (trozet)
milestone: none → queens-1
status: New → In Progress
importance: Undecided → Medium
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3

Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Reason: Per policy, this patch will be abandoned:

You can restore it at anytime if you think the patch will be updated.

Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
status: In Progress → Triaged
assignee: Tim Rozet (trozet) → nobody

Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Reason: Abandoning this patch per the TripleO Patch Abandonment guidelines ( If you wish to have this restored and cannot do so yourself, please reach out via #tripleo on freenode or the OpenStack Dev mailing list.

Changed in tripleo:
milestone: stein-1 → stein-2
Changed in tripleo:
milestone: stein-2 → stein-3
Changed in tripleo:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers