openstack-resource-agents

Resource agents assume a single config file

Bug #1648008 reported by Thomas Bechtold
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openstack-resource-agents
Confirmed
Undecided
Unassigned

Bug Description

Most of the resource agents use "--config-file" which resets the default config-files from oslo.config. So you can not use service specific config files (eg /etc/nova/nova-api.conf ) for the services.
Best would be to start the services without any --config-file/--config-dir switch given and just rely on the defaults from oslo.config .

Revision history for this message
Thomas Bechtold (toabctl) wrote :

Note: --config-dir is not used by any resource agent so with that you could use multiple config snippets. So maybe this bug is invalid but I still feel it would be an improvement to not give any --config-* options to the service during startup.

Revision history for this message
Adam Spiers (adam.spiers) wrote :

@toabctl You are right - this is one of the reasons that I wanted to change the RAs to wrap around systemd services. Then the decision about which config files/dirs to use would be delegated to each distro, and the RAs wouldn't need any knowledge about that. So it would remove duplicated logic, and the RAs could focus on their main value add, which is service-level monitoring. It would be great if you could read this whole thread and let me know if you have any thoughts on it:

http://lists.clusterlabs.org/pipermail/developers/2016-November/000383.html

Changed in openstack-resource-agents:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.