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.

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

fix: update vm_cpu_sockets to vm_cpu_count for CPUs #253

Merged
merged 2 commits into from
Aug 22, 2022
Merged

Conversation

tenthirtyam
Copy link
Contributor

Summary of Pull Request

Updates vm_cpu_sockets to vm_cpu_count for CPUs. The project currently uses the variable vm_cpu_sockets for CPUs (see below); however, the value of the sockets is determined by dividing the number of CPUs by the number of cores per socket.

Signed-off-by: Ryan Johnson [email protected]

Type of Pull Request

  • This is a bugfix.
  • This is an enhancement or feature.
  • This is a code style / formatting update.
  • This is a documentation update.
  • This is a refactoring update.
  • This is something else.
    Please describe:

Related to Existing Issues

Closes: #252

Test and Documentation Coverage

  • Tests have been completed (for bugfixes / features).
  • Documentation has been added / updated (for bugfixes / features).

Breaking Changes?

  • Yes, there are breaking changes.
  • No, there are no breaking changes.

Updates `vm_cpu_sockets` to `vm_cpu_count` for CPUs. The project currently uses the variable `vm_cpu_sockets`  for CPUs (see below); however, the value of the sockets is determined by dividing the number of CPUs by the number of cores per socket.

#252

Signed-off-by: Ryan Johnson <[email protected]>
@tenthirtyam tenthirtyam added type/bug Bug priority/medium Priority Medium size/s Small labels Aug 22, 2022
@tenthirtyam tenthirtyam added this to the v22.08 milestone Aug 22, 2022
@tenthirtyam tenthirtyam self-assigned this Aug 22, 2022
@tenthirtyam tenthirtyam added the info/breaking-change Breaking Change label Aug 22, 2022
Updates `vm_cpu_sockets` to `vm_cpu_count` for CPUs. The project currently uses the variable `vm_cpu_sockets` for CPUs (see below); however, the value of the sockets is determined by dividing the number of CPUs by the number of cores per socket.

#252

Signed-off-by: Ryan Johnson <[email protected]>
@tenthirtyam tenthirtyam merged commit b8cf78f into main Aug 22, 2022
@tenthirtyam tenthirtyam deleted the fix/gh-252 branch August 22, 2022 21:18
tenthirtyam added a commit that referenced this pull request Aug 23, 2022
Updates `CHANGELOG.md` to include the breaking changes in #253.

Signed-off-by: Ryan Johnson <[email protected]>
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info/breaking-change Breaking Change priority/medium Priority Medium size/s Small type/bug Bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update vm_cpu_sockets to vm_cpu_count for CPUs
1 participant