Re: [Engine-devel] Floating Disks implementation in REST-API
In the interest of moving forward, let's agree that, since there
seems to be an overwhelming majority for option 1 (see below),
then if by the start of next week (i.e Monday, April 23)
no one will object to option 1, I will start the implementation.
Thanks,
Ori.
Current summary:
There are four options for Floating-Disks modelling:
two that were previously discussed, and two that were
recently added by Livnat, using PUT. See full list of
options below.
Itamar, Geert, Einav & Ori are currently pro option #1
(if anyone changed his mind - please say so).
Does anyone strongly prefer another option, or can we
move forward with option #1?
Thanks,
Ori.
1)
POST
/api/vms/{vm:id}/disks
<disk id="{disk:id}"/> => attach disk
DELETE
/api/vms/{vm:id}/disks/{disk:id}
<disk><detach>true</detach><disk> => detach disk
2)
POST
/api/vms/{vm:id}/disks
<disk id="{disk:id}"/> => attach disk
DELETE
/api/vms/{vm:id}/disks/{disk:id}/detach => detach disk
3) PUT
/api/vms/{vm:id}/disks
(update on the disks collection) => attach + detach
4) PUT
/api/disks/{disk:id}
(update on the vm-id's of disk) => attach + detach
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel