Glad it worked :)
I'll try to fill the gap, so maybe things will make more sense.
The API you dealt with has 2 basic services - Disk
In 4.3, once you're interested in a disk attached to a VM, the service you
need to use is *disk_attachment*.
(So the GET, PUT POST refers to the disk_attachment service).
Basically, in order to edit a disk (any disk), you need to attach it to a
VM (any VM), and only then update its parameters (name, interface, size,
Even if you want to edit a floating disk (a disk you've just created and
wants to change its name for instance), you need to attach it to a VM, edit
its name and then detach it from the VM back, so it will be floating again.
In 4.4, we've changed that behavior, so editing disks will be available
also for floating disks
That means that you can edit the disk "as disk", not necessarily attached
to a VM, and use the *disk* service.
So in your case, the service you need to use in order to update is
Now, regarding the provisioned_size field, on your GET request, you've
received the following response:
This means that the disk_attachment, the disk that attached to your VM,
also has a reference to the disk itself "as a disk".
By sending a GET request for
*/ovirt-engine/api/disks/f770c0d1-dd0d-40a8-a69a-a63d8db5c2cc*, you'll get
a response of the following form:
Here, you can see the disk's parameters.
So actually, by sending an update request of the form:
Means something like "go to the disk attachment of my VM, and update the
disk elements with the following fields and values".
Hope it makes more sense.
On Thu, Oct 7, 2021 at 9:27 AM <ovirt.org(a)nevim.eu> wrote:
although I don't see the elements there via GET, it really works,
lot. Karma +1 :-)
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: