Bug 1031048

Summary: [RFE] Make all features of oVirt useable via REST-API and Python-SDK
Product: [Retired] oVirt Reporter: Sven Kieske <s.kieske>
Component: ovirt-engine-apiAssignee: Michael Pasternak <mpastern>
Status: CLOSED NOTABUG QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3CC: acathrow, bazulay, iheim, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-15 19:17:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Sven Kieske 2013-11-15 14:26:26 UTC 
Description of problem:
Currently, some things can't be achieved by using the API.
So you must use the webadmin-console for some things (afaik).

Also, new features get developed, and don't get initial api-support, or it
isn't mentioned, e.g.:
http://www.ovirt.org/Features/Detailed_Host_Network_QoS

Version-Release number of selected component (if applicable):
3.3.1-2

How reproducible:
always

Steps to Reproduce:
1. Find a (new) cool oVirt Feature
2. Try if you can use it via REST-API


Actual results:
Most Features work, but some won't

Expected results:
All features work via REST-API

Additional info:
There are use cases of oVirt, where you can't use webadmin but
have to utilize the REST-API or at least some sort of CLI (Python-SDK or
oVirt-Shell).

For these use cases, features not accessible via API simply don't exist.

At least it should be clearly documented somewhere which features are supported
and which not (for downstream rhev that's the case, afaik).

It would be huge if we could implement a policy, that no feature
get's released without being usable via API.

Automated Testing also benefits from this, as you can test easier via API
in contrast to make tests via selenium/webadmin.

This bug could be used as a tracker bug, if accepted.

If you feel this needs more clarification or discussion, please feel free to raise this topic on IRC or via ML.

Keep up the great work.
Comment 1 Itamar Heim 2013-11-15 19:17:12 UTC 
Sven - we try to develop all features with API support, sometimes the API does arrive later.

I'm closing this for as it isn't specific, so hard to fix. i.e., please open a bug on specific gaps you find.

also, we're working on moving the gui to work over the REST API, which should make this 99% go away (I hope).