Separate Configuration from Freescale SDN ML2 mechanism Driver

[Trinath Somanchi]

In the current implementation, CRD configuration is existing within the code of ML2 mechanism driver.
When any other plugin/driver need to use this configuration needs to duplicate the complete configuration.
So the CRD configuration options are to be moved to a separate file to be used with other plugin/drivers.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/120722

[Kyle Mestery (mestery)]

Per my own confusion, moving back to Juno-RC1.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/120722
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=485c174fc7e52e697d1d73a96cd924c2e3a04414
Submitter: Jenkins
Branch: master

commit 485c174fc7e52e697d1d73a96cd924c2e3a04414
Author: Trinath Somanchi <email address hidden>
Date: Wed Sep 17 12:52:14 2014 +0530

    Separate Configuration from Freescale SDN ML2 mechanism Driver

    - In the current implementation, CRD configuration is existing
      within the code of ML2 mechanism driver.

    - When any other plugin/driver (like, Freescale FWaaS Plugin) need
      to use this configuration, it needs to duplicate the complete configuration.

    - So the CRD configuration is moved to a separate file for use
      in other plugin/drivers.

    - Unit testing of this MD is also updated.

    Closes-Bug: #1368033

    Change-Id: I488fee47803a494aae9df42f9c59fffa9843e727