Bug 1078863

Summary:	[RFE] add rest api support for adding network qos entities
Product:	[Retired] oVirt	Reporter:	Sven Kieske <s.kieske>
Component:	ovirt-engine-api	Assignee:	Gilad Chaplik <gchaplik>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.4	CC:	bugs, dfediuck, gchaplik, gklein, iheim, lpeer, myakove, nyechiel, rbalakri, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sla
Fixed In Version:	ovirt-3.5.0_rc2	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-17 12:25:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sven Kieske 2014-03-20 12:57:48 UTC

Description of problem:

currently, you can't add network qos entities to a dc
from REST


Version-Release number of selected component (if applicable):
latest master I guess :)

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:

currently, you can't add network qos entities to a dc
from REST

Expected results:

you can add network qos entities to a dc
from REST

Additional info:

Comment 2 Sven Kieske 2014-04-30 09:24:37 UTC

Will this also implement the possibility to attach an existing network qos entity
(defined on DC level) to an existing or new vnic_profile and/or logical network via REST API?

Comment 3 Gilad Chaplik 2014-04-30 17:43:30 UTC

vnic_profile yes, logical network no.

qos on vnic for specific host's network, the profile includes qos and network.

Comment 4 Sandro Bonazzola 2014-10-17 12:25:17 UTC

oVirt 3.5 has been released and should include the fix for this issue.