Ask Your Question

Vikash Kathirvel's profile - activity

2019-01-31 07:25:52 -0500 received badge  Notable Question (source)
2019-01-31 07:25:52 -0500 received badge  Popular Question (source)
2018-03-13 09:12:53 -0500 received badge  Famous Question (source)
2018-03-13 09:12:53 -0500 received badge  Notable Question (source)
2018-02-12 09:37:50 -0500 received badge  Famous Question (source)
2017-06-21 15:44:15 -0500 received badge  Notable Question (source)
2017-06-16 09:25:20 -0500 received badge  Popular Question (source)
2017-06-01 04:42:02 -0500 asked a question Openstack query about DHCP agent

I am trying to setup Openstack Self Service networking with openvswtich with a 3 node setup.

My network node is running the following agents:

  1. DHCP agent
  2. L3 agent
  3. Metadata Agent
  4. Openvswitch agent

My Provider networks have an underlying physical network in 192.168.0.0/24 and there is a dhcp server running which provides IP in the range 192.168.0.100 to 192.168.0.200 through which my host interfaces get the IP.

The Openstack Docs mention

" Enabling DHCP causes the Networking service to provide DHCP which can interfere with existing DHCP services on the physical network infrastructure."

What does this mean? Can someone explain how the provider network architecture works with DHCP?

2017-05-31 20:22:23 -0500 received badge  Popular Question (source)
2017-05-31 07:15:40 -0500 received badge  Editor (source)
2017-05-31 07:09:21 -0500 commented question Openstack neutron l3 agent dead

@Bernd Bausch Yes, it is the only rpc failing, what is more baffling is it worked the first time and the last heartbeat even shows that it was alive a few days back, i have no idea what went wrong in the mean time. I will add the debug logs, please check if something makes sense.

2017-05-31 02:42:30 -0500 commented question Openstack neutron l3 agent dead

@Bernd Bausch The version is same, both are 9.2.0. It also worked the first time after i installed, after that i had to change some configuration to switch to openvswitch, and it stopped working.

2017-05-30 11:40:22 -0500 asked a question Openstack neutron l3 agent dead

I am trying a 3 node setup with 1 controller, 1 compute and 1 network node. I have configured the keystone, glance and nova services.

I am trying to configure the networking service, using openvswitch as the backend. I am running dhcp agent, metadata agent, openvswitch agent and the l3 agent in the network node.

All the services are running, however the l3 agent shows log:

2017-05-30 21:51:32.827 4362 ERROR neutron.common.rpc [req-a32bb78f-972b-4f77-9562-f6c223bf0013 - - - - -] Timeout in RPC method get_service_plugin_list. Waiting for 16 seconds before next attempt. If the server is not down, consider increasing the rpc_response_timeout option as Neutron server(s) may be overloaded and unable to respond quickly enough.
2017-05-30 21:51:32.828 4362 WARNING neutron.common.rpc [req-a32bb78f-972b-4f77-9562-f6c223bf0013 - - - - -] Increasing timeout for get_service_plugin_list calls to 240 seconds. Restart the agent to restore it to the default value.

And the openstack network agent list command shows l3 agent as dead all the other agents are alive and up.

I am only using two options in the l3_agent.ini

interface_driver = openvswitch

external_network_bridge =

Is there something else required? any help will be appreciated.

EDIT 1:

I have checked the versions both neutron-server and l3-agent are version 9.2.0.

And also, i remember it working first time after install, but then i had to restart the services to change configuration to use openvswitch and the problem started

EDIT 2:

Here are the debug logs:

2017-05-31 17:13:45.004 12612 INFO neutron.common.config [-] Logging enabled!
2017-05-31 17:13:45.005 12612 INFO neutron.common.config [-] /usr/bin/neutron-l3-agent version 9.2.0
2017-05-31 17:13:45.006 12612 DEBUG neutron.common.config [-] command line: /usr/bin/neutron-l3-agent --config-file /usr/share/neutron/neutron-dist.conf --config-dir /usr/share/neutron/l3_agent --config-file /etc/neutron/neutron.conf --config-dir /etc/neutron/conf.d/common --config-dir /etc/neutron/conf.d/neutron-l3-agent --log-file /var/log/neutron/l3-agent.log setup_logging /usr/lib/python2.7/site-packages/neutron/common/config.py:107
2017-05-31 17:13:45.085 12612 DEBUG oslo_messaging._drivers.amqpdriver [req-cfd85cea-7516-4ee3-9d05-3e7436846b68 - - - - -] CALL msg_id: da645eba066444cc8e1de41485b9922f exchange 'neutron' topic 'q-l3-plugin' _send /usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py:448
2017-05-31 17:14:45.054 12612 DEBUG oslo_concurrency.lockutils [-] Lock "_check_child_processes" acquired by "neutron.agent.linux.external_process._check_child_processes" :: waited 0.000s inner /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:270
2017-05-31 17:14:45.056 12612 DEBUG oslo_concurrency.lockutils [-] Lock "_check_child_processes" released by "neutron.agent.linux.external_process._check_child_processes" :: held 0.001s inner /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:282
2017-05-31 17:14:45.089 12612 ERROR neutron.common.rpc [req-cfd85cea-7516-4ee3-9d05-3e7436846b68 - - - - -] Timeout in RPC method get_service_plugin_list. Waiting for 41 seconds before next attempt. If the server is not down, consider increasing the rpc_response_timeout option as Neutron server(s) may be overloaded and unable to respond quickly enough.
2017-05-31 17:14:45.090 12612 WARNING neutron.common.rpc [req-cfd85cea-7516-4ee3-9d05-3e7436846b68 - - - - -] Increasing timeout for get_service_plugin_list calls to 120 seconds. Restart the agent to restore it to the default value.
2017-05-31 17:15:25.863 12612 WARNING neutron ...
(more)
2017-05-30 03:56:36 -0500 commented answer Openstack Flat Provider network with openvswitch

Hi, thanks for your response, but i have a 3 node setup, does it mean i need a br-ex in both network and compute node?

2017-05-26 07:57:28 -0500 received badge  Scholar (source)
2017-05-26 07:57:26 -0500 received badge  Supporter (source)
2017-05-25 16:31:53 -0500 asked a question Openstack Flat Provider network with openvswitch

I am using https://docs.openstack.org/newton/networking-guide/deploy-ovs-provider.html#deploy-ovs-provider (OVS provider networks) to deploy a flat provider network with openvswitch as the interface driver. Eventually i will move on to self-service networks based on VXLAN.

The docs mention that 2 networks are required, management and provider network. I understood the concept of management network, and my management network is a local 10.0.0.0/8 network with no internet access. But I am struggling to understand the concept of provider networks.

The aim is to provide external access to the instances, correct?

I can access the internet through a TP-Link tl wr941nd router, which provides me IP in the 192.168.0.0/24 network. But the docs mention that "an instance uses a provider (external) network that connects to the physical network infrastructure via layer-2 (bridging/switching). This network includes a DHCP server that provides IP addresses to instances.".

What does this mean? Does it mean that the provider network is the same as the one i use for my hosts to access the internet?