Open Stack

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.

	-Sean

-- 
Sean Dague
http://dague.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 482 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140502/6f6908f9/attachment.pgp>