[openstack-dev] [neutron] [ml2] Configuration file sections for MechanismDrivers

Andre Pech apech at aristanetworks.com
Tue Aug 6 01:51:32 UTC 2013

Hey Kyle,

We're currently going with the second option you describe - having separate
configuration files per mechanism driver, and passing these in on the
command line when starting Neutron. This feels much cleaner than putting
all configuration options into the ML2 config file, especially as the
number of mechanism drivers grows.


On Mon, Aug 5, 2013 at 1:22 PM, Kyle Mestery (kmestery)
<kmestery at cisco.com>wrote:

> While working on the OpenDaylight ML2 MechanismDriver, one thing which
> cropped up was configuration file options for MechanismDrivers and were
> those should be stored. I was initially of the opinion we should put all
> configuration sections into the ml2 configuration file, but this could get
> crowded, and would make the sample one confusing. The other option is to
> create them in separate configuration files per-MechanismDriver, and pass
> those on the command line when starting the Neutron server. This keeps
> things tidy from the perspective that you would only need to modify the
> ones you plan to run with Ml2.
> So my question is, which route do people prefer here?
> I'll have to make some changes to the ML2 devstack configuration to
> support this no matter which way we go forward, as it currently doesn't
> support the concept of separate configuration sections for MechanismDrivers.
> Thanks,
> Kyle
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130805/dbfd4582/attachment.html>

More information about the OpenStack-dev mailing list