Neutron's Agents

General Agent module mainly by Neutron API, core plugin (such as Linux bridge Plugin,ovs plugin, etc.), XX Agent scheduler, XX agent, XX driver (DNSMASQ) constitute .

In the control node neutron agent-list, you can view all the agents

1.neutron-l3-agent,neutron-vpn-agent

Run on the network node, responsible for handling three layers of things such as routing, and so on, the two conflicting, only need to open a process

2.neutron-openvswitch-agent

Run on all OpenStack nodes, responsible for interacting with Openvswitch to handle two levels of things. Connect control nodes, network nodes, and computer points.

Code: Neutron.plugins.openvswitch.agent.ovs_neutron_agent:main

3.neutron-lbaas-agent

Running on network nodes, dealing with loadbanlance related things

4.neutron-fwaas-service, that the service is not considered agent, without its own process, running in vpn-agent

5.neutron-metadata-agent

Runs on the network node, processing the metadata request issued by Cloud-init in the host, Neutron-metadata-agent will bring these requests from the Neutron-ns-metadata-proxy program or Qdhcp-xxx namespace that the Qrouter-xxx namespace process brings up Neutron-ns-metadata-proxy The process is forwarded to the metadata-server contained in the NOVA-API.

See the other side of the article http://niusmallnan.github.io/_build/html/_templates/openstack/metadata_server.html

6.neutron-metering-agent

Metering agent for the tenant network to provide three-tier network traffic data metering services.

7.neutron-dhcp-agent

Running on the network node, the tenant network is provided with a 3-tier DHCP service, i.e. the IP address is dynamically allocated, and a metadata request service is also provided.

The entrance to the neutron-dhcp-agent is Neutron.agent.dhcp_agent:main, similar to the startup mode of L3-agent, which starts with the service The manager class is dhcpagentwithstatereport, reporting the status of Dhcpagent.

Neutron's Agents