<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi,<br>
<br>
On 12/06/2014 03:14 AM, Gaudenz Steinlin wrote:<br>
</div>
<blockquote cite="mid:874mtaul8h.fsf@meteor.durcheinandertal.bofh"
type="cite">
<pre wrap="">I'm not sure if I understand your concerns.</pre>
</blockquote>
<br>
I think it is the difference between<br>
<ul>
<li>having one distribution-managed configuration file per daemon
(like in /usr/share/<project>/<daemon>.conf)
containing the default log file, meaning 58 configuration files
(see the list at the end)</li>
<li>versus having it computed in the init-script instead (LOGFILE=/var/log/${PROJECT_NAME}/${NAME}.log)<br>
</li>
</ul>
I'm more inclined to have it explicitly put anyway because 58 files
is not that much, but as a developper too I can understand the
problem that it is a defactorised form. Maybe the best thing to do
would be to allow some templating in OpenStack configurations
themselves.<br>
<br>
Also note that using a small shell wrapper could be an idea too, as
systemd doesn't go against using shell scripts to launch service: it
simply enables us to avoid running (maybe 1ms?). The shell wrapper
could be generic and take 2 arguments : the project name and the
daemon name. This would allow us to avoid init-script when sysv init
is not in use, and using only one script means the system doesn't
have to load many files (it will be cached when the first openstack
daemon is started).<br>
<br>
List of configuration files required to manage the "one logfile per
daemon" logic, exclude /usr/share prefix:<br>
<br>
ceilometer/ceilometer-agent-central.conf<br>
ceilometer/ceilometer-agent-compute.conf<br>
ceilometer/ceilometer-agent-notification.conf<br>
ceilometer/ceilometer-alarm-evaluator.conf<br>
ceilometer/ceilometer-alarm-notifier.conf<br>
ceilometer/ceilometer-api.conf<br>
ceilometer/ceilometer-collector.conf<br>
cinder/cinder-api.conf<br>
cinder/cinder-backup.conf<br>
cinder/cinder-scheduler.conf<br>
cinder/cinder-volume.conf<br>
designate/designate-agent.conf<br>
designate/designate-api.conf<br>
designate/designate-central.conf<br>
designate/designate-sink.conf<br>
fuel-astute/astute.conf<br>
fuel-nailgun/nailgun-api.conf<br>
fuel-nailgun/nailgun-assassin.conf<br>
fuel-nailgun/nailgun-reciever.conf<br>
glance/glance-api.conf<br>
glance/glance-registry.conf<br>
heat/heat-api-cfn.conf<br>
heat/heat-api-cloudwatch.conf<br>
heat/heat-api.conf<br>
heat/heat-engine.conf<br>
ironic/ironic-api.conf<br>
ironic/ironic-conductor.conf<br>
keystone/keystone.conf*<br>
murano-agent/murano-agent.conf<br>
murano/murano-api.conf<br>
murano/murano-engine.conf<br>
neutron/neutron-dhcp-agent.conf<br>
neutron/neutron-l3-agent.conf<br>
neutron/neutron-lbaas-agent.conf<br>
neutron/neutron-metadata-agent.conf<br>
neutron/neutron-metering-agent.conf<br>
neutron/neutron-plugin-linuxbridge-agent.conf<br>
neutron/neutron-plugin-openvswitch-agent.conf<br>
neutron/neutron-server.conf<br>
neutron/neutron-vpn-agent.conf<br>
nova/nova-api.conf<br>
nova/nova-baremetal.conf<br>
nova/nova-cells.conf<br>
nova/nova-cert.conf<br>
nova/nova-compute.conf<br>
nova/nova-conductor.conf<br>
nova/nova-consoleauth.conf<br>
nova/nova-console.conf<br>
nova/nova-consoleproxy.nova-novncproxy.conf<br>
nova/nova-consoleproxy.nova-serialproxy.conf<br>
nova/nova-consoleproxy.nova-spicehtml5proxy.conf<br>
nova/nova-consoleproxy.nova-xenvncproxy.conf<br>
nova/nova-network.conf<br>
nova/nova-scheduler.conf<br>
sahara/sahara.conf<br>
tuskar/tuskar-api.conf<br>
tuskar/tuskar-manager.conf<br>
zuul/zuul-server.conf<br>
<br>
</body>
</html>