Bug 973339 - Up front coverage of PackStack networking decisions and requirements.
Up front coverage of PackStack networking decisions and requirements.
Status: CLOSED CURRENTRELEASE
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Getting_Started_Guide (Show other bugs)
3.0
Unspecified Unspecified
high Severity high
: ---
: 4.0
Assigned To: Deepti Navale
ecs-bugs
: Documentation, Triaged
Depends On:
Blocks: 1011085
  Show dependency treegraph
 
Reported: 2013-06-11 13:53 EDT by Stephen Gordon
Modified: 2014-01-05 22:42 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-01-05 22:42:39 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Stephen Gordon 2013-06-11 13:53:21 EDT
> * 4.2 - We need an upfront discussion of the decisions that need to be
> made, at least for the networking service. We need to explain the choice
> between quantum and nova networking, how its selected, and then
> throughout the section show which options apply to nova vs quantum
> networking. With quantum, we need to similarly cover the choice of
> plugins and which options apply to each plugin. Also, for quantum (or
> nova's VlanManager), we need to at least mention the need for a switch
> that trunks a range of VLANs if doing a multi-node deployment.

Acknowledged, but I think this is an area where we are really struggling for traction. It's easier to say "contrast Nova vs Quantum" than it is to actually do it.

Note You need to log in before you can comment on or make changes to this bug.