Open Stack

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

+1 for making single config the norm

I think it's not just devstack/grenade that would benefit from this.
Variance in the plugin configuration patterns is a fairly common
complaint I hear from folks deploying OpenStack, and going to a single
config would likely make that easier.  I think it probably benefits
distributions too.  There have been several issues with distro init
scripts not properly supplying all the necessary --config-file
arguments to Neutron services because they're not uniformly pattered.
 Many distros take their cues from the sample config files (e.g.
https://github.com/openstack/neutron/tree/master/etc/ ), so ideally we
could unify things there early in the Juno cycle to give packagers
time to adapt.  The config management tool communities on StackForge
(Puppet/Chef/etc) would likely also benefit from greater uniformity as
well.

At Your Service,

Mark T. Voelker

On 05/02/2014 11:24 AM, Salvatore Orlando wrote:
> Technically we don't need anything in neutron to migrate to a
> single config files if not rearrange files in ./etc For devstack,
> iniset calls to plugin-specific configuration files should then be
> adjusted accordingly. I think we started with plugin specific
> configuration files because at that time it looked better to keep
> "common" arguments separated from the plugin-specific ones.
> 
> From what I gather this could and should be achieved together with
> the config file generation work. I recall having seen somebody
> (don't remember who) volunteer for that on IRC.
> 
> Salvatore
> 
> 
> 
> 
> On 2 May 2014 15:18, Kyle Mestery <mestery at noironetworks.com 
> <mailto:mestery at noironetworks.com>> wrote:
> 
> On Fri, May 2, 2014 at 6:39 AM, Sean Dague <sean at dague.net 
> <mailto:sean at dague.net>> wrote:
>> Some non insignificant number of devstack changes related to
>> neutron seem to be neutron plugins having to do all kinds of
>> manipulation of extra config files. The grenade upgrade issue in
>> neutron was
> because of
>> some placement change on config files. Neutron seems to have *a
> ton* of
>> config files and is extremely sensitive to their
>> locations/naming,
> which
>> also seems like it ends up in flux.
>> 
>> Is there an overview somewhere to explain this design point?
>> 
>> All the other services have a single config config file
>> designation on startup, but neutron services seem to need a bunch
>> of config files correct on the cli to function (see this process
>> list from recent grenade run -
>> http://paste.openstack.org/show/78430/ note you will
> have
>> to horiz scroll for some of the neutron services).
>> 
>> Mostly it would be good to understand this design point, and if
>> it
> could
>> be evolved back to the OpenStack norm of a single config file for
>> the services.
>> 
> I think this is entirely possible. Each plugin has it's own 
> configuration, and this is usually done in it's own section. In 
> reality, it's not necessary to have more than a single config file,
> as long as the sections in the configuration file are unique.
> 
> I'd like to hear from other Neutron developers on this as well. We 
> could propose this change for Juno to migrate to a single config
> file if everyone agrees.
> 
> Thanks, Kyle
> 
>> -Sean
>> 
>> -- Sean Dague http://dague.net
>> 
>> 
>> _______________________________________________ OpenStack-dev
>> mailing list OpenStack-dev at lists.openstack.org
> <mailto:OpenStack-dev at lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>> 
> 
> 
> _______________________________________________ OpenStack-dev
> mailing list OpenStack-dev at lists.openstack.org 
> <mailto:OpenStack-dev at lists.openstack.org> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> 
> _______________________________________________ OpenStack-dev
> mailing list OpenStack-dev at lists.openstack.org 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTY8xWAAoJELUJLUWGN7CbGyIQAMZq6zDu9wvYRIJgafgRY3MK
TR1cGqlljchEzSCHw6kF7/s6JdlVbRruBHELPmIUpvStDlyc4gUdVNatqq/cbn2S
Kp0LwXcZ+kATTKP0AgzpjYWJawwuVGvlXvmgMMvSkG7sJ2U6RIhjDLLjBkAFBulN
bT+KRhfPjFjicW1UdAvQbT5xNkXk7pU1/+Uvo5v776CTeDkJ2VUVtDP9SpOMAKmv
i+ykOmKrpIaw634ThvVE7dYkg4TKf4xacnM0GO+HTJ98uKSK4VOIwGTCg7QAM5/p
QCc/Uy8LttKsc5NtTyCfU/37zOp3n0PynS3avNMioTk7Z78Xw5oQ131BAj5A4YrE
H+Kto8OThjRSApdSnAY6kUvO2+6UGCdiIKq/HsicbCHB4DzNtduyMap9Bm0DtJz5
/f6BmKhDNXIdtK3wks0YPMH43dUWcvL529IFO7pBOqucTCA91Pyji3FXPUN/IoDV
v7tpbtMuDkyV+0fmY1GDj0jT8qVdcOnkiirHZPujtvC6PrwpMPWKui1iAwqUFZxh
Og1iAMYwBm/rBn+3xg3tgn9zJJ1/W+HwROdUbhYOo8yg7l4Oc1wRMM68U+5HC6Iw
01VMs7fiH9qVd/3OgF8IHL/zgiKIFRKDZql3m/MX6cI838zpHfrbenXE1EeZUGCc
jF5b+OeEhw5QOY0n6w2f
=eoSD
-----END PGP SIGNATURE-----