Return 409 for second firewall creation

Second firewall creation returns 500, but it is an expected behavior
of firewall reference implementation and an internal server error
should not be returned.

Change-Id: I9f537b238007d35172e2504591d9d3568ba3a41a
Closes-Bug: #1301105
(cherry picked from commit 9df867c672bfb3f80511086c889b744113c56604)
Set ns_name in RouterInfo as attribute

Closes-Bug: #1302007
Change-Id: I02a9b92eea06010569d3d9c5a987e69f89b23be5
(cherry picked from commit ceee7b4ac9d027499dfd2568868f1192bfb77879)
Merge "Return 409 for second firewall creation" into milestone-proposed
Merge "Set ns_name in RouterInfo as attribute" into milestone-proposed
Updated from global requirements

Change-Id: I73c3798ede53e2c4d936f997d9a502e1b5cfa462
Merge "Updated from global requirements" into milestone-proposed
Opening stable/icehouse

Bump version to next stable release on icehouse branch, and set
defaultbranch in .gitreview for convenience.

Change-Id: I70ddfb8cc70f9d7fca4ff63f95d5bd9c7fb7ef81
Added missing plugin .ini files to setup.cfg

Some plugin .ini configuration files were missing and hence not
installed via 'setup.py install'.

Conflicts:
	setup.cfg

Change-Id: I31f096e7fbf9f7a182ba8535ca8cadc4fecc6632
Partial-Bug: 1324487
(cherry picked from commit a75e156af64afb61f3ebf928eda132325e5a46f5)
Do not defer IPTables apply in firewall path

By default, iptables apply is deferred in L3 agent. For
external gateways, iptables is applied immediately (to
enable NAT for floating IP). Similarly, when firewall
is created/updated/deleted, iptable rules are applies
immediately.

Change-Id: I4f652a030ae23a71a2e20af2e8ef0ad5b882b80e
Closes-Bug: #1320775
(cherry picked from commit 6167cb55e2f62a645487d66e52b809c9599b3bb8)
Fix race condition with firewall deletion

In some cases when firewall is created and then deleted in short
period of time, there could be a race condition of firewall status
changes. Agent may change firewall status from PENDING_DELETE to ACTIVE
because the agent has just set it up on the backend.
Delete request then is not properly served and firewall remains in ERROR
state and can't be deleted at all.

To fix this changing status from PENDING_DELETE is not allowed.
Deleting firewall in ERROR state is allowed.

Change-Id: Iec3cfcb1e03b33dda8e1f10ca51bd9b61fa8030d
Closes-Bug: #1328162
(cherry picked from commit 58e6bb5893186517edafe1a4d51710c1362bc9cc)
Merge "Fix race condition with firewall deletion" into stable/icehouse
Updated from global requirements

Change-Id: I64dcc6f9552cf7f8b6ff3503923e9acc58e3f5bd
Merge "Do not defer IPTables apply in firewall path" into stable/icehouse
Added missing core_plugins symbolic names

Some plugins miss short symbolic name in setup.cfg, specifically Nuage
and Metaplugin.

Conflicts:
	setup.cfg

Change-Id: I0198ae98654bbdddf8f2ba8dd3b80d0d447d6341
Closes-Bug: 1324487
(cherry picked from commit 664bdcdc7d714bcdfe503db8f59c6a3f97668df2)
Merge "Added missing core_plugins symbolic names" into stable/icehouse
Bump stable/icehouse next version to 2014.1.2

Change-Id: Id7181755d3609c0ae91c2402b34f2de02c06a1f0
Merge "Bump stable/icehouse next version to 2014.1.2" into stable/icehouse
Updated from global requirements

Change-Id: I24c366cc4bdac1f635968136f46dd8b850dba8b4
Updated from global requirements

Change-Id: I1b725d6e6d154ed4211cf866bb0b4c7d9a76dafc
Set python hash seed to 0 in tox.ini

New tox (>=1.7.0) sets a random python hash seed by default. This is
generally good for testing because it will help keep projects working
regardless of the hash seed, but neutron unittests don't currently pass
with a random hash seed so set it to the python default seed.

This change will allow us to use new tox again and remove the
restriction on tox<=1.6.1 to run unittests.

Note this change will need to be backported to the stable branches to
keep unittests there working with new tox as well.

Change-Id: If151efeb8caae3111515191e238d6e6ae491cd44