Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1365731 - How to get oVirt node CPU type by using oVirt API or CLI ?
Summary: How to get oVirt node CPU type by using oVirt API or CLI ?
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-node
Classification: oVirt
Component: legacy-ovirt-node
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
: ---
Assignee: Fabian Deutsch
QA Contact: Ying Cui
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-10 05:51 UTC by Evan
Modified: 2016-08-11 02:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-10 07:58:52 UTC
oVirt Team: Node
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Evan 2016-08-10 05:51:01 UTC
Description of problem:
I use yum installed vdsm , how to get oVirt node  "CPU type" parameter ?

Comment 1 Fabian Deutsch 2016-08-10 07:58:52 UTC
Does

# vdsClient -s 127.0.0.1 getVdsCapabilities

provide what you need?

At least I do not see a bug here. please use the mailing list for questions.

Comment 2 Evan 2016-08-11 02:56:39 UTC
(In reply to Fabian Deutsch from comment #1)
> Does
> 
> # vdsClient -s 127.0.0.1 getVdsCapabilities
> 
> provide what you need?
> 
> At least I do not see a bug here. please use the mailing list for questions.

OK,thanks!


Note You need to log in before you can comment on or make changes to this bug.