Bug 928815

Summary:	quantum-l3-agent can host only a single virtual router per node
Product:	Red Hat OpenStack	Reporter:	Bob Kukura <rkukura>
Component:	openstack-quantum	Assignee:	Bob Kukura <rkukura>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Rami Vaknin <rvaknin>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.1	CC:	breeler, chrisw, lpeer, oblaut, sgordon, yeylon, ykaul
Target Milestone:	rc	Keywords:	TestOnly, Triaged
Target Release:	3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	RHEL 6.4 does not support network namespaces. Therefore the use_namespaces configuration variable in /usr/share/quantum/quantum-dist.conf is set to False by default. Without using network namespaces, a node running quantum-l3-agent can only provide a single virtual router. One way to work around this issue is to deploy a separate quantum-l3-agent on a separate node for each virtual router that is created. For each quantum-l3-agent, set router_id in /etc/quantum/l3_agent.ini to the UUID identifying the virtual router that it hosts. This allows multiple virtual routers to be created. However, since administrative action is needed for each, self-service deployment of routers by tenants is not possible.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-28 14:19:57 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:	869004, 880142, 889264, 971672
Bug Blocks:	918057

Description Bob Kukura 2013-03-28 14:04:02 UTC

Description of problem:

The quantum-l3-agent uses the node's IP stack's routing functionality to implement virtual routers that route between different quantum subnets and, in conjunction with iptables, NAT route between these and external networks. The l3-agent-is designed to use network namespaces to provide multiple independent virtual routers per node, that do not interfere with each other or with routing of the node on which they are hosted. Due to the lack of network namespace support in RHEL 6.4, the RHOS quantum-l3-agent is limited to providing only a single virtual router per node.

In addition to this limitation, it is necessary to configure each quantum-l3-agent with the UUID identifying the router instance that it hosts. This complicates deployment, makes self-service provisioning of routers by/for tenants impractical.


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


How reproducible:


Steps to Reproduce:
1. Create virtual router
2. Configure quantum-l3-agent to host this router 
3. Create 2nd virtual router
  
Actual results:

The same quantum-l3-agent cannot be configured to host this router. A different quantum-l3-agent on a different node would need to be deployed for it.


Expected results:

A single deployed quantum-l3-agent should be able to host multiple virtual routers, and should not require configuration with the UUID(s) of the router(s) it hosts.


Additional info:

Comment 2 Bob Kukura 2013-04-02 14:55:32 UTC

*** Bug 923380 has been marked as a duplicate of this bug. ***

Comment 3 Bob Kukura 2013-04-05 22:06:15 UTC

Added draft known issue doc text for RHOS 2.1 release notes and/or KB.

Comment 6 Rami Vaknin 2013-06-05 10:34:09 UTC

Vetrified on Grizzly installed on RHEL6.4
# uname -r
2.6.32-358.6.2.openstack.el6.x86_64
# rpm -qa | grep quantum
python-quantumclient-2.2.1-1.el6ost.noarch
python-quantum-2013.1.1-9.el6ost.noarch
openstack-quantum-openvswitch-2013.1.1-9.el6ost.noarch
openstack-quantum-2013.1.1-9.el6ost.noarch


# quantum router-list
+--------------------------------------+---------+--------------------------------------------------------+
| id                                   | name    | external_gateway_info                                  |
+--------------------------------------+---------+--------------------------------------------------------+
| 3bf49320-606c-453c-8d8d-3ea9bb5e549c | router2 | null                                                   |
| 44bce74c-d31c-40ad-809e-32c286a88a75 | router1 | {"network_id": "cb57d2d7-0877-410f-a959-69651d6d593b"} |
+--------------------------------------+---------+--------------------------------------------------------+
# quantum router-port-list 3bf49320-606c-453c-8d8d-3ea9bb5e549c
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                          |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| 16901800-7609-4c16-851e-bc4b056de00b |      | fa:16:3e:64:ea:0b | {"subnet_id": "18c247bd-0d06-49c1-b678-ededa959fe80", "ip_address": "10.35.174.1"} |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
# quantum router-port-list 44bce74c-d31c-40ad-809e-32c286a88a75
+--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                           |
+--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+
| aba39692-3de6-46c0-bebd-841e908a6015 |      | fa:16:3e:39:5d:44 | {"subnet_id": "7da79f11-5ab5-4942-9998-2cbc196cc46c", "ip_address": "10.35.171.1"}  |
| b57d0a83-c2b1-4b6b-9841-a2d4741153d3 |      | fa:16:3e:a8:1d:8f | {"subnet_id": "b1d26af7-054e-4e70-83c3-275de6511565", "ip_address": "10.35.172.1"}  |
| d3bac191-470b-4b18-8c07-b80b9bdacade |      | fa:16:3e:49:59:20 | {"subnet_id": "dc5a2d0b-a702-4a91-82cc-84d98b73cd20", "ip_address": "10.35.170.10"} |
+--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+
# ip netns list
qdhcp-b80941b6-e119-4dd0-8c44-4a6e48b6b784
qrouter-3bf49320-606c-453c-8d8d-3ea9bb5e549c
qdhcp-1fa181dd-0b02-453d-9527-aaf9357f90c2
qrouter-44bce74c-d31c-40ad-809e-32c286a88a75
#