[RFE] Handling SIGHUP on Ironic services
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Wishlist
|
Ruby Loo |
Bug Description
It's a common practice for daemons handle the SIGHUP signal as a trigger for server's reconfiguration, specially reloading configuration files. Currently neither the Ironic conductor or Ironic API server does support it.
The oslo.service library [0] already have implemented support for services to handle this signal, the same for the oslo.config library [1][2] which added support for "mutable" configuration options which are configurations that are meant to be reloaded dynamically. One example of use case would be to operators to enable/disable the debug log without having to restart the services.
This RFE is about adding the signal handlers and only reloading the mutable options already defined in other libraries (such as oslo.log, which defines "debug" as mutable). For Ironic configuration, we can submit further patches later adding mutable where it does make sense.
Note: SIGHUP does not work on Windows*
[0] http://
[1] https:/
[2] http://
Changed in ironic: | |
importance: | Undecided → Wishlist |
tags: | added: rfe |
Changed in ironic: | |
assignee: | nobody → Lucas Alvares Gomes (lucasagomes) |
Changed in ironic: | |
status: | New → In Progress |
tags: | added: needs-spec |
Changed in ironic: | |
assignee: | Lucas Alvares Gomes (lucasagomes) → nobody |
Changed in ironic: | |
status: | In Progress → Triaged |
status: | Triaged → Confirmed |
Changed in ironic: | |
assignee: | nobody → Ruby Loo (rloo) |
tags: |
added: rfe-approved removed: needs-spec rfe |
Hi! That's a great idea. We've discussed it on the meeting, and there are enough unclear bits to warrant a spec. Please post one, if you don't mind. Thanks!