ironic/releasenotes/notes/limit-memory-consumption-c7949a49853ba83d.yaml
Sharpz7 949387bd80 [codespell] Fixing Spelling Mistakes
This is the first in a series of commits to add support for codespell. This is continuning the process completed in ironic-python-agent.

Future Commits will add a Tox Target, CI support and potentially a git-blame-ignore-revs file if their are lots of spelling mistakes that could clutter git blame.

Change-Id: Id328ff64c352e85b58181e9d9e35973a8706ab7a
2024-02-12 19:58:56 +00:00

24 lines
1.0 KiB
YAML

---
features:
- |
The ``ironic-conductor`` process now has a concept of an internal
memory limit. The intent of this is to prevent the conductor from running
the host out of memory when a large number of deployments have been
requested.
These settings can be tuned using
``[DEFAULT]minimum_required_memory``,
``[DEFAULT]mimimum_memory_wait_time``,
``[DEFAULT]minimum_memory_wait_retries``, and
``[DEFAULT]minimum_memory_warning_only``.
Where possible, Ironic will attempt to wait out the time window, thus
consuming the conductor worker thread which will resume if the memory
becomes available. This will effectively rate limit concurrency.
If raw image conversions with-in the conductor is required, and a
situation exists where insufficient memory exists and it cannot be waited,
the deployment operation will fail. For the ``iscsi`` deployment
interface, which is the other location in ironic that may consume large
amounts of memory, the conductor will wait until the next agent heartbeat.