
In the Open vSwitch agent, the Agent id is currently based off the mac address of the br-int. Userspace only Open vSwitch derivatives such as Intel's DPDK Accelerated Open vSwitch do not currently create a tap device in the kernel to back the ovs bridges local port. This limitation prevents reuse of the OpenVSwitch agent between both switches. To enable reuse of the ovs agent with Intel's DPDK Accelerated Open vSwitch, the proposal is to change the generation of the agent_id to use the hostname, instead of the mac address of the br-int. For several plugins such as the nec,mlnx,hyperv and onconvergence agents the hostname is used to create the agent id. Using the hostname will normalise the agent_id between these 5 neutron agents, additionally log readability will also be improved, if log aggregation is preformed across a cluster as it will be easier to identify which node the log is from. the hostname is retrived from cfg.CONF.host Closes-Bug: #1323259 Change-Id: I9abfac17a74d298f1a17a0931fc98ac00234ac0b
# -- Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
# -- External Resources:
The homepage for Neutron is: http://launchpad.net/neutron . Use this site for asking for help, and filing bugs. Code is available on github at <http://github.com/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
Neutron Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/
Neutron API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/
The start of some developer documentation is available at: http://wiki.openstack.org/NeutronDevelopment
For help using or hacking on Neutron, you can send mail to <mailto:openstack-dev@lists.openstack.org>.