Red Hat Bugzilla – Bug 1008512
[RFE] QoS support is missing from CLI, SDK and REST API
Last modified: 2016-02-10 15:19:37 EST
Description of problem:
It's impossible to run commands for QoS through Rest API, SDK and CLI
There is no support for QoS in SDK, CLI and Rest API
There should be support for QoS in SDK, CLI and Rest API
Adding an attachment that steps through a QoS use case supporting this RFE.
The use case comes from a Public Sector RFP requirement defining minimum VM bandwidth at 100Mbps, with the ability to add bandwidth in 100Mbps increments. The proposed response would leverage the QoS capability to define QoS profiles for 100Mbps, 200Mbps, 300Mbps, etc. up to <Max>Mbps. In order to perform a change programmatically through the cloud self service portal, an API capability to list/change the profile for a given VM would be required.
Discussed with the RHEV Engineering team on 3/7/14, suggesting this post and attachment just added.
From following up with engineering, these capabilities are already in place:
There are 2 ways to get the desired vnic profile:
1. By querying api.getVnicProfiles() for a specific profile
2. By querying api.getNetworks().getNetwork(networkName).getVnicProfiles() which returns only the profiles of a specific network.
Changing from one profile to another:
VMNIC vnic = vm.getNics().get("nic1");
Example provided at the following URL:
Please let us know if this is insufficient, but it does appear as if this functionality does already exist in RHEV 3.3
Well you can't define the qos via api, see BZ 1078863
How can this be in status POST when none of the patches in BZ1078863
are merged? Where those replaced by different commits?
(In reply to Sven Kieske from comment #5)
> How can this be in status POST when none of the patches in BZ1078863
> are merged? Where those replaced by different commits?
POST means there are patches available. It does not mean the
issue is resolved.
fixed in vt3, moving to on_qa.
if you believe this bug isn't released in vt3, please report to email@example.com
If this bug requires doc text for errata release, please provide draft text in the doc text field in the following format:
The documentation team will review, edit, and approve the text.
If this bug does not require doc text, please set the 'requires_doc_text' flag to -.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.