Bug 862208
Summary: | user cannnot take a vm from pool via restapi | |||
---|---|---|---|---|
Product: | [Retired] oVirt | Reporter: | Pieter Vogel <pvogel> | |
Component: | ovirt-engine-api | Assignee: | Michael Pasternak <mpastern> | |
Status: | CLOSED DUPLICATE | QA Contact: | ||
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | unspecified | CC: | acathrow, bazulay, dyasny, iheim, ykaul | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | virt | |||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 864438 (view as bug list) | Environment: | ||
Last Closed: | 2012-10-09 13:39:50 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: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 864438 |
Description
Pieter Vogel
2012-10-02 09:49:48 UTC
bug should be in: Product: Red Hat Enterprise Virtualization Manager component: ovirt-engine-restapi But I cann't move this bug. Hi Pieter, Can you please post request you have used against api and engine log? That is the problem. This is not possible via restapi. In the userportal a user can click on a pool to get a vm from that pool (take vm) then the userportal shows a machine from that pool (eg pool-01) then the user can click on that machine for a spice-connection. Via restapi we try it as follows: get as user a list of vm's This results in a list of vm's the user has rights on. but their is no pool visible. and of course we don't have a possibility to "take a vm" and give user rights on a vm from a pool. What we are missing in restapi: 1) howto see via restapi that a user has a userrole on a pool 2) take a vm from a pool (if a user didn't already have one) indeed. the rest api was originally developed for admins, and pool 'allocate' wasn't relevant for admins. now that user api was added, it was basedon the admin api, which didn't have this verb which should be added. http://lists.ovirt.org/pipermail/engine-devel/2012-October/002572.html *** This bug has been marked as a duplicate of bug 864438 *** |