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

bug 1513086: add cores per socket to OpenStack cloud inventory parser #341

Merged
merged 1 commit into from
Aug 29, 2018

Conversation

sseago
Copy link
Contributor

@sseago sseago commented Aug 29, 2018

https://bugzilla.redhat.com/show_bug.cgi?id=1513086

For OpenStack cloud, cpu_cores_per_socket was always set to 1 in the legacy refresh_parser
since OpenStack flavors only have a single "number of CPUs" param. The new inventory
parser was not setting this param at all, though, leaving it as nil.

https://bugzilla.redhat.com/show_bug.cgi?id=1513086

For OpenStack cloud, cpu_cores_per_socket was always set to 1 in the legacy refresh_parser
since OpenStack flavors only have a single "number of CPUs" param. The new inventory
parser was not setting this param at all, though, leaving it as nil.
@sseago
Copy link
Contributor Author

sseago commented Aug 29, 2018

Note that if this PR needs to be backported to gaprindashvili it's not a clean backport. To work on gaprindashvili we also need to modify app/models/manageiq/providers/openstack/inventory_collection_default/cloud_manager.rb which has been deleted on master, so that change wasn't needed for this to work on master.

@miq-bot
Copy link
Member

miq-bot commented Aug 29, 2018

Checked commit sseago@4d0c9df with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
1 file checked, 0 offenses detected
Everything looks fine. 🏆

@aufi
Copy link
Member

aufi commented Aug 29, 2018

Looks good to me, merging!

@aufi aufi merged commit 2371c85 into ManageIQ:master Aug 29, 2018
@aufi aufi added the bug label Aug 29, 2018
@aufi aufi added this to the Sprint 94 Ending Sept 10, 2018 milestone Aug 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants