Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add NUMA topology information to BMH status.hardware #1818

Open
hardys opened this issue Jul 8, 2024 · 5 comments
Open

Add NUMA topology information to BMH status.hardware #1818

hardys opened this issue Jul 8, 2024 · 5 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@hardys
Copy link
Member

hardys commented Jul 8, 2024

User Story

As a user I would like to have access to NUMA topology information for pre-configuration of performance critical workloads, e.g cluster hardware information can be used at the deployment phase to optimally configure workloads such as telco network functions.

Detailed Description

IPA has a plugin which can collect the relevant information:

https://docs.openstack.org/ironic-python-agent/latest/_modules/ironic_python_agent/numa_inspector.html

So when the related information is available it would be good to propagate it to the BMH status.hardware

/kind feature
@metal3-io-bot metal3-io-bot added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Jul 8, 2024
@dtantsur
Copy link
Member

dtantsur commented Jul 8, 2024

BMH status.hardware

is deprecated, you mean the HardwareData resource.

I also think we need a design proposal for this one since it extends the API.

@hardys
Copy link
Member Author

hardys commented Jul 8, 2024

BMH status.hardware

is deprecated, you mean the HardwareData resource.

I also think we need a design proposal for this one since it extends the API.

Oops yes I copied status.hardware since it was mentioned in the slack conversation - agreed a design proposal makes sense for this to clarify the API addition.

@Rozzii
Copy link
Member

Rozzii commented Jul 10, 2024

/triage accepted

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Jul 10, 2024
@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 8, 2024
@Rozzii
Copy link
Member

Rozzii commented Oct 9, 2024

/remove-lifecycle stale
/lifecycle frozen

@metal3-io-bot metal3-io-bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
Metal3 - Roadmap
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
4 participants
@dtantsur @hardys @Rozzii @metal3-io-bot