This patch adds a new configuration variable for the timeout on
ovs-vsctl commands, and sets the default timeout to 10 seconds.
This is aimed at allowing users to tune the agents in order to avoid
timeout errors on their deployments.
Change-Id: I73ea0d0de49a4b4a118bc2d68ad9c093ea122717
Closes-Bug: #1254520
With this patch a l3 agent can handle
any networks by setting the neutron
parameter external_network_bridge
and gateway_external_network_id to
empty.
Related-Bug: #1234750
Related-Bug: #1194350
Change-Id: Id260a239df23951da730513f40cda490002effc3
Adds a configuration option to tell the network agents to delete
namespaces when they are no longer in use. The option defaults to
False so that the agent will not attempt to delete namespaces in
environments where this is not safe.
This has been working well in deployments where iproute2 has been
patched with commit 58a3e8270fe72f8ed92687d3a3132c2a708582dd or it is
new enough to include it without being patched.
Change-Id: Ice5242c6f0446d16aaaa7ee353d674310297ef72
Closes-Bug: #1250596
Related-Bug: #1052535
The default for send_arp_for_ha was 3 and is now 0.
This patch changes the comment in l3_agent.ini to
show the new default.
Change-Id: I77370350ffee6ad7b94aa7db341c062ebc0b7d89
This change renames everything to Neutron while providing backwards
compatible adjustments for Grizzly configuration files.
implements blueprint: remove-use-of-quantum
Change-Id: Ie7d07ba7c89857e13d4ddc8f0e9b68de020a3d19
This is a l3-agent version of 349aa3ef35.
The combination of the plugin without agent extension support
and L3NATAgentWithStateReport results in an error:
"AttributeError: No such RPC function 'report_state'".
This patch changes l3_agent_manager to be L3NATAgent instead of
L3NATAgentWithStateReport since all plugins do not support
L3NATAgentWithStateReport and having this as the default breaks
all current deployments that upgrade source without changing
their config files.
Fixes bug 1139726
Change-Id: Ibb5c04c89bfad741ec43a372cbf97445f7b3d76c
Fixes bug 1105523
The patch set adds 2 new functions:
1. register_root_helper - this enables all wanting to use
the root_helper variable. This is under the section AGENT.
2. get_root_helper - this is a helper function that returns the
root_helper. This should be used when the application used to
have the root_helper defined under the section DEFAULT. This
ensures backward compatability.
Change-Id: Iba72c4fc89ba5329ea045483287012f82b306250
Bug 1089223
RyuInterfaceDriver is eliminated, so update the example of
dhcp_agent.ini, l3_agent.ini for Ryu plugin and other OVS
based plugins.
Change-Id: Icc95c213ecd96946bd5a90d5d60df88c94cc1454
On one hand, we sync router data (including routers,
their gw ports, interfaces and floatingips) from l3_agent
to quantum server periodically if needed.
On the other hand, we notify l3 agent from quantum server when
we delete or update a router's stuff, such as floating IP,
interface and gwport and router itself.
blueprint rpc-for-l3-agent
bug #1080286
Change-Id: I60f3081975fc7164b22f9e9fa941e702a3f4c663
fixes bug 1086012
A prior change incorrectly removed the sample state_path from the
l3_agent config file. This change adds the correct sample value to the
file.
Change-Id: I10455706442c004e5d0337834b5baa3b794af5e7
fixes bug 1085249
This patch sets the default state_path to match a reasonable deployment
value instead of the devstack default.
Change-Id: Ib0c10621d91760588a68a62df8a60682d780e015
blueprint metadata-overlapping-networks
Adds Metadata for guest VMs running on Qunatum networks. This requires
a companion patchset for Nova to test.
Change-Id: I524c6fdcd6a44e46da08395fd84c1288052a69ea
Fixes bug 1042046
Sending gratuitous ARPs when a external router or a floating
IP was added in order to facilitate HA.
I am using iputils-arping package to send ARP packets. You will need
to install iputils-arping on Ubuntu and iputils on Fedora/RHEL/CentOS.
Arping locates in /usr/bin/arping on Ubuntu and locates in /sbin/arping
on Fedora/RHEL/CentOS.
Change-Id: I125dbc57b90027dc5e99ff0a5d6877843a0b02a5
bug #1042028
Allows user to invoke L3-agent in a way that limits the agent to
implementing only routers associated with a particular external network.
Thus, it is possible to have a deployment with multiple external networks,
since you can run one agent per external network.
Also makes l3-agent pay attention to router admin_state_up field.
Change-Id: Ia79d29301530718bc381c8e5a9d197de9452bce2
Fixes bug 1042104
The fix follows the patch that was done on the DHCP agent to enable
the user to configure the usage of namespaces. In the event that
namspaces are disabled the agent is limited to running only one
router. The agent needs to define the router_id that is supported.
The process in this case is:
1. create router
2. start agent with router id
Change-Id: I2a71dc009c5aea285ff9f903b3faa99b0c9f820f
Fix bug 1037815
Summary: Copy/paste the essential parts of the rootwrap
mechanism from nova/cinder into quantum. This includes
the core changes to filter.py and wrapper.py which deal
with loading filters from files pointed to by
rootwrap.conf
Detailed changes:
Transliterate the old rootwrap/*-agent.py files to
new format, and put the results in etc/quantum/rootwrap.d
Delete the *-agent.py files.
Add conf to point to etc/quantum/rootwrap.d
Add a unit test cribbed from nova to exercise the filter
mechanism
Add a unit test to exercise the actual filtered execution
Note that as written, this patch does not set the default
execute mechanism (in the agent .ini files) to rootwrap,
leaves it as sudo. That can be done in a followon
change, or in distro specific packaging.
Note also that there is still work to do around finishing
and testing the filter specs themselves. We've decided
that that is out of scope for this patch.
Change-Id: I9aba6adc5ba40b6145be5fa38c5ece3b666ae5ca
bp quantum-l3-fw-nat
router & floating IP API calls, plugin db, and agent implemented
and unit tested
Change-Id: I6ee61396d22e2fd7840aa2ff7d1f6f4a2c6e54d4
Jenkins