[docs] untagged network is not a hard requirement for floating net

Bug #1555858 reported by Mike Scherbakov on 2016-03-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Svetlana Karslioglu
Svetlana Karslioglu

Bug Description

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

Fix proposed to branch: master
Change author: Svetlana Karslioglu <email address hidden>
Review: https://review.fuel-infra.org/20869

Changed in fuel:
status: Confirmed → In Progress

Reviewed: https://review.fuel-infra.org/20869
Submitter: Michele Fagan <email address hidden>
Branch: master

Commit: 085896ba4b171d94a83dbfce5976a3652270b693
Author: Svetlana Karslioglu <email address hidden>
Date: Wed May 18 21:33:50 2016

Modified the networking topologies section

Removed ambiguity about the networking topologies by describing
that the networking topologies in this section are recommended,
however a user can change the networking configuration as needed
to address his/her needs.

Change-Id: I0da08f62c29c28ff05429fc00485a56da3974e4c
Closes-bug: 1555858

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers