Bug 918087
| Summary: | Quantum external network doesn't support vlans using provider network | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ofer Blaut <oblaut> | |
| Component: | doc-Release_Notes | Assignee: | Bob Kukura <rkukura> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ofer Blaut <oblaut> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 2.0 (Folsom) | CC: | breeler, chrisw, lpeer, ppyy, rkukura, sgordon, ykaul | |
| Target Milestone: | rc | Keywords: | Documentation, Triaged | |
| Target Release: | 2.1 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Release Note | ||
| Doc Text: |
Two different mechanisms are available for connecting a quantum-l3-agent to an external network. The first, using an external bridge (typically br-ex) only applies to the openvswitch plugin. The second, using a provider external network, applies to both the openvswitch and linuxbridge plugins.
Using a provider external network involves creating a provider network with external connectivity, creating a subnet on that provider network describing the external network's IP addressing and gateway, and deploying the quantum-l3-agent with external_network_bridge turned off in /etc/quantum/l3-agent.ini. The following steps can be followed to configure a router with a provider VLAN as its external network:
quantum net-create <external_network_name> --router:external True --provider:network_type vlan --provider:physical_network <physical_network_name> --provider:segmentation_id <external_VLAN_tag>
quantum subnet-create --gateway <external_gateway_IP> --allocation-pool start=<external_IP_start>,end=<external_IP_end> --disable-dhcp <external_network_name> <external_network_CIDR>
quantum router-create router1
quantum router-gateway-set router1 <external_network_UUID>
quantum router-interface-add router1 <private_subnet_UUID>
quantum-l3-setup --plugin <plugin_name>
openstack-config --set /etc/quantum/l3_agent.ini DEFAULT external_network_bridge ""
openstack-config --set /etc/quantum/l3_agent.ini DEFAULT router_id <router_UUID>
service quantum-l3-agent start
chkconfig quantum-l3-agent on
Note that <external_gateway_IP> must be within <external_network_CIDR>, and that <external_IP_start> and <external_IP_end> must specify a range for floating IPs within <external_network_CIDR> that does not include <external_gateway_IP>.
A flat network can be used as the external provider network by substituting the following net-create command:
quantum net-create <external_network_name> --router:external True --provider:network_type flat --provider:physical_network <physical_network_name>
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 953395 (view as bug list) | Environment: | ||
| Last Closed: | 2013-05-17 14:39:55 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: | 953395 | |||
|
Description
Ofer Blaut
2013-03-05 13:04:04 UTC
This may just be a documentation issue. Setting the l3_agent's external_network_bridge to the empty string should enable a provider external network to be used with the openvswitch or linuxbridge plugin. I'll check to see if this works on my multi-node setup. I do expect this to work with the existing code, and will update this BZ to a docs issue and provide the details when I've verified it works. Hi Bob, any Doc Text for this yet? I assume this bug can also be set to Doc Type; Release Note once it is confirmed a doc issue. OK, I've finally verified that provider external networks do work with openvswitch. Other issues such as BZ 919181 had been preventing my tests from succeeding previously. Also note that the documented br-ex external network approach is not available for the linuxbridge plugin, so using a provider external network is the only option with linuxbridge and is an available option for openvswitch. I'll add doc text describing using a provider external network for both openvswitch and linuxbridge. The following commands were used to create a router with vlan 185 on physnet1 as its external network: quantum net-create lab-185 --router:external True --provider:network_type vlan --provider:physical_network physnet1 --provider:segmentation_id 185 quantum subnet-create --gateway 10.16.123.254 --allocation-pool start=10.16.123.100,end=10.16.123.110 --disable-dhcp lab-185 10.16.123.0/24 quantum router-create router1 quantum router-gateway-set router1 0f20bf1b-6060-4b66-968d-9f61c8067944 quantum router-interface-add router1 26073a79-cef8-43d7-b282-5bf0ac8979cf quantum-l3-setup openstack-config --set /etc/quantum/l3_agent.ini DEFAULT external_network_bridge "" openstack-config --set /etc/quantum/l3_agent.ini DEFAULT router_id 1a347492-bd87-4676-ae17-823a66e190ab Draft release note text has been added. Note that although this bug is currently filed against doc-Release-Notes, this information needs to be incorporated into the Getting Started Guide for future releases. Removing external tracker bug with the id 'https://bugs.launchpad.net/quantum/+bug/1056437' as it is not valid for this tracker |