Bug 973339
| Summary: | Up front coverage of PackStack networking decisions and requirements. | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Stephen Gordon <sgordon> |
| Component: | doc-Getting_Started_Guide | Assignee: | Deepti Navale <dnavale> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ecs-bugs |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.0 | CC: | alyoung, breeler, dnavale |
| Target Milestone: | --- | Keywords: | Documentation, Triaged |
| Target Release: | 4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-06 03:42:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1011085 | ||
> * 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.