On 06/20/2013 02:07 PM, Christophe Fergeau wrote:
Hey Itamar,
On Wed, Jun 19, 2013 at 06:00:47PM +0300, Itamar Heim wrote:
> On 06/19/2013 04:33 PM, Tomas Jelinek wrote:
>> Hi all,
>>
>> for the non plugin invocation of the console
(
http://www.ovirt.org/Features/Non_plugin_console_invocation) the dynamicMenu property is
not usable to enrich the SPICE client menu.
>>
>> This feature is about requesting this menu using oVirt's REST API and than
calling it back once some item from this menu has been selected.
>>
>> The oVirt's feature page with specific details:
http://www.ovirt.org/Features/Foreign_Menu_Using_REST
>>
>> Any comments are more than welcomed.
>
> Why are we putting the logic of the menu into the REST API?
> can't the menu be builded by client based on getting the list of
> ISO's and current CD?
The client needs a way to get the list of available ISOs in order to build
the menu, as well as a way to let the engine know when the user clicked on
an ISO in the menu. One way of doing that is to have the menu stuff exposed
in the REST API. Another way would be to expose the list of ISOs in the
REST API (I'd have a slight preference for that I think).
that's my preference as well, and the REST API should already do that today:
- get list of ISOs of available in a DC (the one the VM is in)
- ability to change the CD of the VM
Or do you have anything in mind for the client to get the list of
ISOs
available to the engine?
my preference is to provide the data, not the semantics of the menu.
iiuc, we are on the same page.
Christophe