networking-notes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Irina Povolotskaya |
Bug Description
Currently there's a number of networking architecture diagrams and explanations available in MOS/Fuel docs, but "all of them are more of less ugly, outdated, and wrong" (c) not me. It would be nice if Docs team could review and fix (or redo) them. My wishlist for what I'd like to see in diagrams is below:
- List (legend) + scheme of all logical networks with following info:
-- What it's used for
-- How is it implemented (OVS bridge + name, VLAN/untagged/
-- How bridges are interconnected and mapped to eth/bond interfaces
- Examples of how user can map logical networks to physical NICs (2 typical setups - 2 NICs per server, 4 NICs per server)
- Hacks and temporary solutions (like Ceph public traffic going through br-mgmt)
It's quite possible that >2 diagrams are needed. OVS bridges are interconnected differently in VLAN and GRE modes. Also, physical and logical network perspective may be hard to fit on a single drawing.
Last but not least, I suggest that it's time to make an effort and make all terminology consistent across fuel-library, Fuel UI and documentation. For example:
Example 1:
There's a network called Private on "Configure interfaces" screen. The same network is called "Internal" on "Networks" screen and in documentation. Finally, in documentation http://
Example 2:
Storage network is explained by the following piece:
"Storage Network
Part of a cluster's internal network. It is used to separate storage traffic (Swift, Ceph, iSCSI, etc.) from other types of internal communications in the cluster. The Storage network is usually on a separate VLAN or interface, isolated from all other communication.". The description is vague and mostly wrong. In current implementation Storage network should be called Storage Replication, it carries only replication traffic from Ceph or Swift. Ceph public traffic, in turn, is dispatched through br-mgmt (so, goest through Management network) - while this is not fixed in Product this should be clearly explained in documentation.
Also, none of the diagrams outline Ceph, only "Cinder node".
Changed in fuel: | |
assignee: | nobody → Fuel Documentation Team (fuel-docs) |
status: | New → Confirmed |
importance: | Undecided → Medium |
milestone: | none → 6.1 |
tags: | added: docs |
Changed in fuel: | |
importance: | Medium → High |
Changed in fuel: | |
assignee: | Fuel Documentation Team (fuel-docs) → Irina (ipovolotskaya) |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
My take on networking diagram + explaining legend (also not perfect and not entirely accurate) can be found here - https:/ /docs.google. com/a/mirantis. com/drawings/ d/1AREI2rIoEYDp g1sWxtPvAKNXEVI sYhrhMqaysE3bAK I/edit