[docs] untagged network is not a hard requirement for floating net
Bug #1555858 reported by
Mike Scherbakov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
In Progress
|
High
|
Svetlana Karslioglu | ||
| Mitaka |
Fix Released
|
High
|
Svetlana Karslioglu | ||
Bug Description
https:/
Network topologies, supported by Fuel, are written in such a way that a use may think that those are the only possible combinations of networks and physical interfaces.
One of particular examples:
Port for the following networks:
Public/Floating (untagged)
In fact, it is not necessary to have untagged port for public/floating. So I think that documentation has explicitly state, that this is example configuration, but Fuel in fact allows ability to do it flexible.
There are certain limitations, but those should be listed separately.
| Changed in fuel: | |
| assignee: | nobody → Fuel Documentation Team (fuel-docs) |
| Changed in fuel: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| Changed in fuel: | |
| assignee: | Fuel Documentation Team (fuel-docs) → Svetlana Karslioglu (skarslioglu) |
| Changed in fuel: | |
| milestone: | 9.0 → 10.0 |
Revision history for this message
| Fuel Devops McRobotson (fuel-devops-robot) wrote Fix proposed to mos/mos-docs (master) | #1 |
| Changed in fuel: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Fuel Devops McRobotson (fuel-devops-robot) wrote Fix merged to mos/mos-docs (master) | #2 |
To post a comment you must log in.
Fix proposed to branch: master
Change author: Svetlana Karslioglu <email address hidden>
Review: https:/