Hi, I am deploying a openstack cluster with several compute nodes on CentOS 6.4 with Neutron/Quantum and network_type vlan based on these guides:
http://docs.openstack.org/trunk/openstack-network/admin/content/under_the_hood_openvswitch.html https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst http://openstack.redhat.com/Neutron_with_OVS_and_VLANs In my setup I have a "controller" that runs everything plus additional compute nodes (and I plan to remove the compute service from the controller). I have had an issue with reaching guest VM instances when they are spawned on compute nodes other the controller and discovered that while the l3-agent deployed on the controller was added to the router, adding the other l3 agents, e.g. quantum l3-agent-router-add 789a77fd-52ff-44be-afea-27d26a8cd3d3 router01 resulted in the following error displayed in the openvswitch log: 2013-09-04 19:44:24 ERROR [quantum.api.v2.resource] create failed Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/quantum/api/v2/resource.py", line 82, in resource result = method(request=request, **args) File "/usr/lib/python2.6/site-packages/quantum/extensions/agentscheduler.py", line 88, in create body['router_id']) File "/usr/lib/python2.6/site-packages/quantum/db/agentschedulers_db.py", line 187, in add_router_to_l3_agent router_id=router_id, agent_id=id) RouterSchedulingFailed: Failed scheduling router 295450ba-597f-4526-970c-f9e9ec79206a to the L3 Agent 789a77fd-52ff-44be-afea-27d26a8cd3d3. Could anyone help me by pointing to its cause? I've filed a bug on this, there are more details in its description: https://bugs.launchpad.net/neutron/+bug/1220611 Thanks, /Nicolae.
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
