Roles and groups in granular deployment is a different entities
Bug #1553113 reported by
Stanislaw Bogatkin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Won't Fix
|
Medium
|
Fuel Sustaining | ||
| Newton |
Confirmed
|
Medium
|
Fuel Sustaining | ||
Bug Description
In a task-based deployment 'roles' and 'groups' entities is the same. But in granular (role) deployment they are completely different. It leads us to bugs like this: [0]. There is need to make them equal like in task-based deployment.
| Changed in fuel: | |
| status: | New → Confirmed |
| tags: | added: tech-debt |
| tags: | removed: team-bugfix |
| tags: | added: team-enhancements |
| Changed in fuel: | |
| assignee: | Fuel Python Team (fuel-python) → Ilya Kutukov (ikutukov) |
| Changed in fuel: | |
| assignee: | Ilya Kutukov (ikutukov) → Fuel Python Team (fuel-python) |
Revision history for this message
| Ilya Kutukov (ikutukov) wrote | #1 |
Revision history for this message
| Alexey Shtokolov (ashtokolov) wrote | #2 |
| Changed in fuel: | |
| importance: | High → Medium |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
Here is a deployment graph from TestBlockDevice
When we calling _update_
If we are supposing that developer have made a mistake and defined roles instead of groups (see refer. bug) we should use roles as groups if no groups provided.
The green connections is the connections created using groups fields.
The red connections created using roles when groups are not found.
As you could see adding red lines (roles) creating loops in this graph making it's proper traversal impossible.
So i don't see easy way of substitution groups dependencies with roles in legacy orchestrator.