Skip to content

scheduler: Log only for vmware hosts without aggregate in ShardFilter#616

Open
joker-at-work wants to merge 1 commit intostable/2023.2-m3from
scheduler-shard-filter-no-log-aggregate-non-vmware
Open

scheduler: Log only for vmware hosts without aggregate in ShardFilter#616
joker-at-work wants to merge 1 commit intostable/2023.2-m3from
scheduler-shard-filter-no-log-aggregate-non-vmware

Conversation

@joker-at-work
Copy link
Copy Markdown

The ShardFilter is not relevant for hosts that are not vmware-related, which is clear after the first check it does: checking if the request is for a vmware spec.

Since with KVM we can have a lot of hosts coming in which can create a lot of logs, disable logging for non-vmware hosts entirely. We previously already reduced the log-level for ironic nodes, because of non-relevance, but since we like to run with debug-level in prod, too, not logging anything is preferred to that.

Change-Id: I36b71949179c126762c9f8003e95ea0cf90ececb

grandchild
grandchild previously approved these changes Apr 1, 2026
@joker-at-work joker-at-work force-pushed the scheduler-shard-filter-no-log-aggregate-non-vmware branch from c3ff7bb to 113e78d Compare April 1, 2026 13:08
The ShardFilter is not relevant for hosts that are not vmware-related,
which is clear after the first check it does: checking if the request is
for a vmware spec.

Since with KVM we can have a lot of hosts coming in which can create a
lot of logs, disable logging for non-vmware hosts entirely. We
previously already reduced the log-level for ironic nodes, because of
non-relevance, but since we like to run with debug-level in prod, too,
not logging anything is preferred to that.

Change-Id: I36b71949179c126762c9f8003e95ea0cf90ececb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants