EndpointMap always contains all services

Bug #1673042 reported by Steven Hardy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

Even though we have more control over composable roles/services, we still pass the entire EndpointMap to every service template (and elsewhere in t-h-t), and it's getting pretty large now.

We should look at a way (j2 rendering perhaps) to avoid the static translation from endpoint_data.yaml to endpoint_map.yaml, so it's generated dynamically, only for services that are actually enabled.

Steven Hardy (shardy)
Changed in tripleo:
status: New → Triaged
assignee: nobody → Steven Hardy (shardy)
milestone: none → pike-1
importance: Undecided → Medium
tags: added: ocata-backport-potential
Revision history for this message
Steven Hardy (shardy) wrote :

Actually j2 rendering doesn't work as we want to be able to use heat parameter_merge_strategies ref https://bugs.launchpad.net/tripleo/+bug/1635409 so we may need to consider a different approach

Steven Hardy (shardy)
Changed in tripleo:
assignee: Steven Hardy (shardy) → nobody
milestone: pike-1 → pike-2
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
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:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
importance: Medium → Undecided
status: Triaged → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.