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 -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
