[openstack-dev] [packaging][neutron] --config-dir vs. --config-file

Ihar Hrachyshka ihrachys at redhat.com
Mon Apr 13 15:59:55 UTC 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/13/2015 05:42 PM, Matthew Thode wrote:
> We already do this somewhat in gentoo (at least for some daemon 
> initialization stuff) in /etc/conf.d/$DAEMON_NAME.conf.  Adding a 
> --config-dir option to that would be very simple.  Gentoo at least
> will also make the first --config-dir option (/etc/neutron)
> optional as well since we have some users that would like that
> level of separation.

I am not sure you want to pass the whole /etc/neutron as --config-dir
to your services since the directory may contain lots of files that
are irrelevant to the service in question. That's why RDO went with
per service directory + global /etc/neutron/neutron.conf.

> 
> In the mean time, do we install configs to those locations by
> default? I'm not seeing that as a subdir of etc in the neutron
> repo.
> 

If you ask about /etc/neutron/conf.d/, then no, so far it's RDO only.
As for l3 agent config dirs to load advanced services configuration
files on demand, we just link to appropriate configuration files
located in default /etc/neutron/... locations from there:

https://github.com/openstack-packages/neutron/blob/f20-master/openstack-
neutron.spec#L604

/Ihar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJVK+f7AAoJEC5aWaUY1u57OYAIAKHiX6BtE0MBflbMuGEQoQRM
O6EqNM8YVC/lBi+u5VvTv7l9UMATtV9aI8/EJs3LU6w/UMj8jl4fiITVJ4T/pWNg
rNb1TkePeM4ut7eCusEkqBupwYl0aCu/UQaDo2ZQ7zUUYgKIS1A39bkhTn9ihRQC
edumZt63UmTjEEgJTNflypf9BB+85uB3Li7AQJdu96q9dfZFpcswCBLVCs9kColj
FSeBpElrApcC2C2uSkPBIkaOkKexMWMYj1h4nsdQ6qGZmpFptpCa646jYYa9tYgP
zeTscF5JDY7lxqi71eHwNRfZCmSgQsR4pDfwA9UBuJDLKdLIOnIW+JMN9FyqNfY=
=4GT5
-----END PGP SIGNATURE-----



More information about the OpenStack-dev mailing list