Scenario: Classic with Linux Bridge in Networking Guide

Bug #1632512 reported by flintt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Expired
Undecided
Unassigned

Bug Description

1."Operational OpenStack Identity service with appropriate configuration in the <neutron.conf> file." The config file involved identity in compute node should be <nova.conf>?
2. In the images of network flow, the bridges of the vlan type in compute node should be <VLAN bridge> instead of <Tunnel bridge>.

-----------------------------------
Release: 0.9 on 2016-10-08 11:29
SHA: 2524fcf0770a8d50c0e06b42bbb65ebe27f6bc71
Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/networking-guide/source/scenario-classic-lb.rst
URL: http://docs.openstack.org/mitaka/networking-guide/scenario-classic-lb.html

Revision history for this message
John Davidge (john-davidge) wrote :

1. Appears to be correct. See: http://docs.openstack.org/mitaka/config-reference/networking/sample-configuration-files.html#neutron-conf

2. Which diagrams specifically? The page has multiple diagrams which use VLAN bridge and/or Tunnel bridge depending on the scenario.

Changed in openstack-manuals:
status: New → Incomplete
Revision history for this message
flintt (flintthuang) wrote :
Revision history for this message
John Davidge (john-davidge) wrote :

Both of those links return a 404 error. Can you link the the section of the page in which they appear?

Revision history for this message
Tom Fifield (fifieldt) wrote :
Revision history for this message
Darren Chan (dazzachan) wrote :

@fllinthuang, can you provide updated links?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openstack-manuals because there has been no activity for 60 days.]

Changed in openstack-manuals:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.