Use sushy simulator as a proper deamon (e.g. via gunicorn)
Bug #1751571 reported by
Ilya Etingof
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ironic |
Fix Released
|
Low
|
Aija | ||
| Sushy Tools |
Fix Released
|
Undecided
|
Aija | ||
Bug Description
Currently, both Redfish simulators work as an interactive processes (they keep attached to the controlling terminal). Alternatively, they can be invoked by gunicorn (can be seen in OpenStack CI jobs). This makes it hard to manage it by standard means, including starting it on system boot and restarting when it fails.
This bug is to add systemd units for the simulators perhaps invoking them through gunicorn.
| Changed in sushy-tools: | |
| assignee: | nobody → Aija (ajya) |
| Changed in sushy-tools: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to sushy-tools (master) | #1 |
Revision history for this message
| Dmitry Tantsur (divius) wrote Re: [RFE] Make simulators proper system daemons | #2 |
| summary: |
- [RFE] Make simulators proper system daemons + Use sushy simulator as a proper deamon (e.g. via gunicorn) |
| Changed in ironic: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in sushy-tools: | |
| status: | In Progress → Opinion |
| tags: |
added: gate removed: rfc |
| Changed in sushy-tools: | |
| status: | Opinion → In Progress |
| Changed in ironic: | |
| assignee: | nobody → Aija (ajya) |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on sushy-tools (master) | #3 |
| Changed in ironic: | |
| status: | In Progress → Fix Released |
| Changed in sushy-tools: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/