[docs] Ops guide network planning should be improved

Bug #1448926 reported by Bogdan Dobrelya on 2015-04-27
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
High
Fuel Documentation Team
6.0.x
High
Fuel Documentation Team
6.1.x
Undecided
Fuel Documentation Team
7.0.x
Undecided
Fuel Documentation Team
8.0.x
High
Fuel Documentation Team

Bug Description

This comes from https://bugs.launchpad.net/mos/+bug/1447619/comments/7

The documentation should recommend users to plan the networking capacity carefully, which is:
* either to put management and private (i.e. tenant) tagged/GRE networks at different physical interfaces
* or configure QoS/management traffic prioritization for a single bond interface case.

Changed in mos:
importance: Undecided → Medium
milestone: none → 6.1
assignee: nobody → Fuel Documentation Team (fuel-docs)
description: updated
Dmitry Borodaenko (angdraug) wrote :

Medium priority bugs are not backported to old releases, postponed to 7.0, marked Won't Fix for 6.0.x.

Changed in mos:
status: New → Confirmed
milestone: 6.1 → 7.0
milestone: 7.0 → none
assignee: Fuel Documentation Team (fuel-docs) → nobody
Changed in mos:
milestone: none → 7.0
Mike Scherbakov (mihgen) wrote :

Raised to High priority as it affects all deployments including 6.1. Users must be aware of technical limitations of GRE in current Fuel reference architecture, otherwise it would lead to broken operations OpenStack (user won't be able to create / shutdown VMs / attach volumes /etc.).

We would also need to document a manual workaround: how to transfer GRE traffic to other physical interface.

Changed in mos:
importance: Medium → High
assignee: nobody → Fuel Documentation Team (fuel-docs)
milestone: 7.0 → 6.1
description: updated
Bogdan Dobrelya (bogdando) wrote :

Updated the description as we have the GRE traffic layout bug fixed https://bugs.launchpad.net/fuel/+bug/1285059

description: updated
tags: added: docs
no longer affects: mos/7.0.x
Changed in mos:
milestone: 6.1 → 8.0
status: Confirmed → New
tags: added: area-docs
tags: added: non-release
Alexey Stupnikov (astupnikov) wrote :

MOS6.0 is no longer supported, moving to Won't Fix.

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

Other bug subscribers