Bug 950662 - FlatDHCP networking with multiple physical hosts needs better documentation.
Summary: FlatDHCP networking with multiple physical hosts needs better documentation.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Installation_and_Configuration_Guide
Version: 2.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.0
Assignee: Stephen Gordon
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-10 15:14 UTC by Nikola Dipanov
Modified: 2016-04-22 05:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-13 15:01:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Nikola Dipanov 2013-04-10 15:14:46 UTC
Description of problem:

bz #917370 raised the issue that FlatDHCP networking with more physical host is something we should have documented better. it doesn't seem to fit in the getting started guide as the topic might be too broad.

However it may be useful to have more details on this particular type of networking setup (FlatDHCP single-host network with multiple compute nodes), as this is likely to be a very common "proof-of-concept" deployment for customers.

Ideally it would be a topic covered in a larger networking guide.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Bruce Reeler 2013-05-02 22:49:11 UTC
Steve G: Reading BZ 917370 and http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-flat-dhcp-networking.html ,
this bugfix may be more properly located in Inst & Config Guide?

Comment 3 Stephen Gordon 2013-06-13 15:01:19 UTC
I *think* we've rectified this in the grizzly documentation, we're now largely concentrating on OpenStack Networking but we have provided a better reference architecture for multi-node deployment.


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