metering driver default value is different in code and config file

We defined the metering driver is IptablesMeteringDriver in config,
but in code, the driver is NoopMeteringDriver.

Change-Id: Ia4fb6751e8a9919f844ef27a303e2fa95b46670e
Closes-Bug: #1360958
Datacenter moid should not be tuple

Remove the comma, because it will convert the string to tuple
Closes-bug: #1362480

Change-Id: I2debb76bae26fe3d437a431f2946f66a1cbe6851
Adding mechanism driver in ML2 plugin for Nuage Networks

This patchset introduces basic ml2 driver for nuage.
In Juno release, mechanism driver will support basic
L2 functionality as a stepping stone to enhance
it in later releases.

Implements blueprint: ml2-mech-driver-nuage
Change-Id: Idae4f88f3d21526f377ec0f81377cb90b9fc14e4
Make SecurityGroupsRpcCallback a separate callback class

RPC has a version of itself. In Neutron a plugin implements
several RPC interface, so a single RPC version doesn't work.
In Mixin callback class approach, RPC versioning depends on
each plugin implementation and it makes harder to maintain
RPC version appropriately. This patch series replaces mixin
RPC callback of server side with a separate class.

This commit handles server-side callback of security group
RPC interface.
* The server-side callback of Security group RPC is moved to
  api/rpc/handler and db/securitygroups_rpc_base now only
  contains a mixin class to add agent-based security group
  implementation with db operations.
* get_port_from_device method in server-side callback class
  is moved to a mixin class of plugin implementation
  (SecurityGroupServerRpcMixin) because it involves DB lookup
  and is tightly coupled with plugin implementation rather
  than RPC interface definition.

Most unit tests for SGServerRpcCallBackTestCase were skipped
in the base class before, but now they are no longer skipped.

The following items will be planned in later patches
to avoid drastic changes in a single patch.
* Merge security group RPC API and agent callback classes in
  agent/securitygroups_rpc into api/rpc/handlers/securitygroup_rpc
* Remove completely duplicated db access code in get_port_from_device
  and get_port_and_sgs

Partial-Bug: #1359416
Change-Id: Ia6535217d2e3b849a95667c1b53dd09675002892
Apic drivers enhancements (second approach): L2 refactor

- refactor to leverage Client's transactional capabilities
- General refactor to improve the driver's reliability

Implements blueprint: apic-driver-enhancements

Change-Id: I4deb171381e62e70818218957d82b5e27954aeb9
Merge "Apic drivers enhancements (second approach): L2 refactor"
Merge "Adding mechanism driver in ML2 plugin for Nuage Networks"
Merge "Make SecurityGroupsRpcCallback a separate callback class"
Cisco DFA ML2 Mechanism Driver

Part 1:
This commit contains changes to support ML2 mechanism driver for Cisco
DFA. For more details please see the blueprint which has more description and
link to document with requirements.

Part 2: Changes in OVS neutron agent.
(http://review.openstack.org/110065)

Part 3: DFA extension driver.
(http://review.openstack.org/111761)

Part 4: DFA config profile service plugin.
(http://review.openstack.org/111863)

Change-Id: Ib53b6705948e1ed75059b85d8809562d9bb63f65
Partially Implements: blueprint ml2-mechanism-driver-for-cisco-dfa
Support for extensions in ML2

The current ML2 plugin supports only extensions defined in the plugin and it
does not support any extensions in the mechanism drivers. The changes in this
commit allows mechanism drivers to define new extensions.

Change-Id: I28da19fabf6de2e9f0d687f875aaaa24c8bbc4f0
Implements: blueprint extensions-in-ml2
Merge "Datacenter moid should not be tuple"
Merge "metering driver default value is different in code and config file"
Merge "Cisco DFA ML2 Mechanism Driver"
Merge "Support for extensions in ML2"