Explain variables precedence for t-h-t and down the road, in tripleo docs

Bug #1731426 reported by Bogdan Dobrelya on 2017-11-10
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
High
Unassigned

Bug Description

Related ML http://lists.openstack.org/pipermail/openstack-dev/2017-November/124415.html

Let's document parameters precedence for t-h-t and down the hill, which may involve or not things like: mistral workflows calling ansible playbooks upon downloaded configs.

Changed in tripleo:
milestone: none → queens-2
importance: Undecided → High
tags: added: documentation ux
tags: added: tech-debt
Changed in tripleo:
status: New → Triaged
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
Changed in tripleo:
milestone: stein-2 → stein-3
Changed in tripleo:
milestone: stein-3 → stein-rc1
Changed in tripleo:
milestone: stein-rc1 → train-1
Changed in tripleo:
milestone: train-1 → train-2
Changed in tripleo:
milestone: train-2 → train-3
Changed in tripleo:
milestone: train-3 → ussuri-1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers