Bug 1076705
| Summary: | RHEV 3.3 rhevm-shell can't change cluster policy to a custom policy | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Dave Sullivan <dsulliva> |
| Component: | ovirt-engine-restapi | Assignee: | Gilad Chaplik <gchaplik> |
| Status: | CLOSED ERRATA | QA Contact: | Lukas Svaty <lsvaty> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.3.0 | CC: | alukiano, bazulay, dfediuck, dsulliva, gchaplik, iheim, juan.hernandez, lbopf, mavital, mtessun, oramraz, rbalakri, rgolan, Rhev-m-bugs, rmohr, sherold, yeylon, ylavi |
| Target Milestone: | --- | ||
| Target Release: | 3.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | sla | ||
| Fixed In Version: | ovirt-engine-3.5.0_beta | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the Red Hat Enterprise Virtualization Manager Command Line Interface (rhevm-shell), which is built on top of the Python SDK, did not support assigning custom scheduling policies to a cluster. The same limitation existed in the REST API. Now, custom scheduling policies can be assigned using a reference, by name or by ID, to the new '/schedulingpolicies' collection. The new options are '--scheduling_policy-name' and '--scheduling_policy-id'. The example below assigns a custom policy (by ID) to 'mycluster':
# update cluster mycluster --scheduling_policy-id 00000000-0000-0000-0000-000000000000
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-11 17:59:11 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: | |||
| Bug Depends On: | 1062435, 1108601, 1108602 | ||
| Bug Blocks: | 1142923, 1156165 | ||
|
Comment 1
Juan Hernández
2014-03-17 09:45:26 UTC
VERIFIED in ovirt-rc1 verification steps: 1. Log to WA portal 2. Create new policy with name "foo" 3. on local machine: curl -X PUT -H "Accept: application/xml" -H "Content-Type: application/xml" -u admin@internal:123456 --cacert ca.crt -d "<cluster><scheduling_policy><name>foo</name></scheduling_policy></cluster>" https://super.secret.address.dot:443/api/clusters/00000001-0001-0001-0001-000000000349 4. refresh cluster tab (it might be necessary to wait for few seconds) and see in cluster edit tab changed policy 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. https://rhn.redhat.com/errata/RHSA-2015-0158.html |