Bug 1324989

Summary:	[RFE] Allow saving Console Invocation in UserPortal
Product:	[oVirt] ovirt-engine	Reporter:	nicolas
Component:	Frontend.UserPortal	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.6.4.1	CC:	bugs, michal.skrivanek, nicolas, oourfali, rnori
Target Milestone:	---	Flags:	rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-10 13:13:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description nicolas 2016-04-07 19:00:29 UTC

Description of problem:

Each time a user logs in to the user portal and wants to start the console, if the desired console is not "Native client" (noVNC when VNC is the console, for instance), the Console Invocation field has to be changed each time.

Version-Release number of selected component (if applicable):
3.6.4.1

Steps to Reproduce:
1. Log in to the userportal
2. User wants to choose noVNC as default for a VM as console is VNC
3. Click on the [...] button on the chosen VM, select noVNC and save
4. Log out, re-log in and "Native client" is selected again.

Additional info:

I think storing selection on a per-user basis is an overkill, storing the option on a per-VM basis would be enough.

Comment 1 Michal Skrivanek 2016-04-08 09:23:01 UTC

(In reply to nicolas from comment #0)

it is supposed to be persisted already. It's in browser's store, so as long as you don't clean up all that and use the same user on same browser it should remain as last time. Is it the case?
Also, there is a global default ClientMode[Vnc|Spice|Rdp]Default you can change via engine-config

Comment 2 nicolas 2016-04-08 10:47:10 UTC

Ah, so it's stored in the browser. Now I tried it and it works, the problem is that I change my location often and access oVirt from different places, so I had the feeling that the choice was not being saved.

Maybe this could be stored in the DB so each machine has its own configuration? If you don't feel this is relevant you can close the BZ as it's indeed working good.

Thanks.

Comment 3 Michal Skrivanek 2016-04-08 12:17:30 UTC

Oved, do you track a server-side general storage for client-side settings?
(is "connect automatically" now done in such a way?)

Comment 4 Oved Ourfali 2016-04-09 06:57:48 UTC

Not sure. 
Ravi?

Comment 5 Ravi Nori 2016-04-10 12:40:52 UTC

We don't track all client-side settings, ssh public key and connect automatically are the only ones currently persisted in the user_profiles table in the database.

Comment 6 Yaniv Kaul 2016-04-10 13:13:59 UTC

(In reply to nicolas from comment #2)
> Ah, so it's stored in the browser. Now I tried it and it works, the problem
> is that I change my location often and access oVirt from different places,
> so I had the feeling that the choice was not being saved.
> 
> Maybe this could be stored in the DB so each machine has its own
> configuration? If you don't feel this is relevant you can close the BZ as
> it's indeed working good.
> 
> Thanks.

Nicolas - thanks. I think I'll close it for the time being - most of the users login from one or few locations - I don't think it's worth the effort to persist it all the way into the database.