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

Use virt-who --print for getting Hypervisors data instead of Satellite #20

Closed
mossicrue opened this issue Oct 25, 2018 · 1 comment
Closed

Comments

@mossicrue
Copy link
Contributor

mossicrue commented Oct 25, 2018

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 in facts sub-dictionary the data we are looking for.

"facts": {
  "hypervisor.type": "VMware ESXi",
  "cpu.cpu_socket(s)": "4",
  "hypervisor.cluster": "cluster_name",
  "hypervisor.version": "6.5.0"
}

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.

@evgeni
Copy link
Member

evgeni commented Dec 7, 2018

fixed in 3821d6a

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

No branches or pull requests

2 participants