Make fuel-devops independent from a single database
Libvirt network bridges that are created by fuel-devops on the host got their names according to the ID in the fuel-devops database.
If different fuel-devops instances will use different databases, then there will be a name collisions because of the same ID numbers in the different databases.
For interact with libvirt network bridges, fuel-devops uses UUID, not bridge names.
- To avoid bridge name collisions, fuel-devops should generate an unique bridge names and check if this name is already used by the libvirt on the host.
This also will help to use different versions of fuel-devops framework that have different database schemes, or use multiple instances of sqlite database instead of single postgresql service.
Blueprint information
- Status:
- Not started
- Approver:
- Aleksandra Fedorova
- Priority:
- Undefined
- Drafter:
- Dennis Dmitriev
- Direction:
- Needs approval
- Assignee:
- Dennis Dmitriev
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
-
9.0
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Allow create DB-independed libvirt networks
Addressed by: https:/
Allow create DB-independed libvirt networks
Addressed by: https:/
Allow create DB-independed libvirt networks
Gerrit topic: https:/
Addressed by: https:/
Add blocking traffic in network or interface
Addressed by: https:/
Do not use database ids in bridge and interface names
Addressed by: https:/
Take offline node device names into account in get_allocated_
Addressed by: https:/
Take offline node device names into account in get_allocated_
Addressed by: https:/
Use libvirt generated bridge and interafece names
Addressed by: https:/
Use libvirt generated bridge and interafece names
Addressed by: https:/
Set network bridge names manually
