-
Notifications
You must be signed in to change notification settings - Fork 5
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
Use virt-who --print for getting Hypervisors data instead of Satellite #20
Comments
mossicrue
added a commit
to mossicrue/katello-attach-subscription
that referenced
this issue
Oct 26, 2018
mossicrue
added a commit
to mossicrue/katello-attach-subscription
that referenced
this issue
Nov 30, 2018
evgeni
pushed a commit
that referenced
this issue
Dec 7, 2018
fixed in 3821d6a |
mossicrue
added a commit
to mossicrue/katello-attach-subscription
that referenced
this issue
Apr 19, 2019
mossicrue
added a commit
to mossicrue/katello-attach-subscription
that referenced
this issue
Apr 19, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If custom facts of an hypervisor aren't available from Satellite, eg: hypervisors socket data are reported by virt-who but are stored only in candlepin DB and not stored in foreman DB / Satellite DB (BZ1638814), we can call
virt-who --print
to retrieve custom facts that aren't present via API.virt-who --print
returns a json containing an array of hypervisor dictionary which has infacts
sub-dictionary the data we are looking for.We can use
cpu.cpu_socket(s)
field to retrieve the number of sockets of an hypervisor and use this value as workaround of the solution I provided on issue #5.The text was updated successfully, but these errors were encountered: