add example of basic "flat" scenario for quantum

Bug #1064643 reported by dan wendlandt
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
Critical
yong sheng gong

Bug Description

In the quantum admin guide, we show a basic use case of a flat network deployment: http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_flat.html

However, the actual set of quantum comments to set this up are non-trivial, so it would be good to have a basic example, that can be linked to from the basic use case. For content, we can use something like what Yong used to respond to this email:

http://<email address hidden>/msg17066.html

Note: we can also comment that for the flat use case the physical network topology is somewhat different than what is shown here: http://docs.openstack.org/trunk/openstack-network/admin/content/connectivity.html . specifically, there is no need to an external network, and instead the router is plugged into the data network directly. perhaps we should have two diagrams for physical topology.

Tags: quantum
Revision history for this message
Tom Fifield (fifieldt) wrote :

text from mail archive:

quantum.conf:

core_plugin = quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2

ovs_quantum_plugin.ini:
network_vlan_ranges = physnet1
enable_tunneling = False
bridge_mappings = physnet1:br-eth0
To create a shared provider network:

quantum net-create sharednet1 --shared --provider:network_type flat --provider:physical_network physnet1

Before we can run, create br-eth0:
sudo ovs-vsctl add-br br-eth0
sudo ovs-vsctl add-port br-eth0 eth0

we don't need br-ex since we don't use router and floatingip
 and br-tun since we don't use GRE.

Changed in openstack-manuals:
status: New → Incomplete
status: Incomplete → Confirmed
importance: Undecided → Medium
status: Confirmed → Triaged
dan wendlandt (danwent)
Changed in openstack-manuals:
importance: Medium → Critical
Changed in openstack-manuals:
assignee: nobody → yong sheng gong (gongysh)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-manuals (master)

Fix proposed to branch: master
Review: https://review.openstack.org/17184

Changed in openstack-manuals:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-manuals (master)

Reviewed: https://review.openstack.org/17184
Committed: http://github.com/openstack/openstack-manuals/commit/1e9315c628148c6f38baa0f8bff33b0ca95507b5
Submitter: Jenkins
Branch: master

commit 1e9315c628148c6f38baa0f8bff33b0ca95507b5
Author: gongysh <email address hidden>
Date: Fri Nov 30 15:08:17 2012 +0800

    Add flat network sample scripts

    Bug #1064643

    Change-Id: Iac810590ce1cd3e0079cf1203ee48fe4a1642472

Changed in openstack-manuals:
status: In Progress → Fix Released
Revision history for this message
Javier J. Salmerón García (javsalgar) wrote :

Hello everyone,

I have one question, what value must tenant_network_type have? vlan, local or none? Thank you

Revision history for this message
yong sheng gong (gongysh) wrote :

If tenant_network_type is not specified, it is defaulted into local. tenant_network_type is useful when we don't give provider:network_type via quantum client.

Revision history for this message
oliver hill (receiveresume) wrote :

After setting the flat network environment, i found that i can't ping my vm instance. And the "ovs-vsctl show" command shows there are only port "br-eth0" and port "eth0" on the bridge "br-eth0". I suppose there should be a port of vm attached to the bridge "br-eth0", isn't it?

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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