[openstack-dev] [neutron] explanations on the current state of config file handling
Sean Dague
sean at dague.net
Sun May 4 12:04:36 UTC 2014
On 05/03/2014 03:53 PM, gustavo panizzo <gfa> wrote:
> On 05/02/2014 11:09 AM, Mark McClain wrote:
>>
>> To throw something out, what if moved to using config-dir for optional configs since it would still support plugin scoped configuration files.
>>
>> Neutron Servers/Network Nodes
>> /etc/neutron.d
>> neutron.conf (Common Options)
>> server.d (all plugin/service config files )
>> service.d (all service config files)
>>
>>
>> Hypervisor Agents
>> /etc/neutron
>> neutron.conf
>> agent.d (Individual agent config files)
>>
>>
>> The invocations would then be static:
>>
>> neutron-server —config-file /etc/neutron/neutron.conf —config-dir /etc/neutron/server.d
>>
>> Service Agents:
>> neutron-l3-agent —config-file /etc/neutron/neutron.conf —config-dir /etc/neutron/service.d
>>
>> Hypervisors (assuming the consolidates L2 is finished this cycle):
>> neutron-l2-agent —config-file /etc/neutron/neutron.conf —config-dir /etc/neutron/agent.d
>>
>> Thoughts?
>
> i like this idea, it makes easy to use configuration manager to setup
> neutron, also it fits perfectly with real life where sometimes you need
> more than one l3 agent running on the same box
Question (because I honestly don't know), when would you want more than
1 l3 agent running on the same box?
-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/20140504/2c1e713c/attachment.pgp>
More information about the OpenStack-dev
mailing list