[Kimchi-devel] [RFC] ticket of VM

[Aline Manera]

+1

Just one comment below

On 06/11/2014 07:33 AM, Sheldon wrote:
> Now I have send a patch V1, no more comments.
>
> These days, I talk with ZhengSheng about the ticket of VM.
>
> Now we are change our design as follow for we should care the VMs
> created by other tools.
>
> 1. make the ticket as the sub-resource of a VM.
> support GET(lookup) and PUT(update) method.
>
> 2. we will not set expire for ticket.
>
> 3. kimchi will set a initial random password for VM when create it.
>
> 4. PUT(update) method can set a password for a VM created by other tool.
> but if expire is set for this VM, kimchi will not change the password.
> or kimchi can change the password but not change the expire.

Why not let user update password and expire time?

>
> 5. when GET method to retrieve the password, if the VM is create by
> other-tools.
> And expire is set, kimchi raise http 400 error when timeout.
>
> 6. pass the ticket to vnc/spice websocket in cookie, not in URL.
> vnc/spice login page get the ticket from cookie.
>