Hide Forgot
I believe that this feature is needed in an educational or training environment. It is vital for our environment as a College to have it or else we will need to look for another vendor for VDI. 1. Proposed title of this feature request: Instant View 2. Who is the customer behind the request? Account: name (acct #)477056 TAM customer: No SRM customer: No Strategic: No 3. What is the nature and description of the request? Provide a feature in rhev-manager that will allow spice to automatically remote into a VM without asking for a username or password using a unique url. In addition, have the VM launch in full screen by default. 4. Why does the customer need this? (List the business requirements here) 1. Lab CLTs complain that they need to prep the classroom each time by login into 24 PCs per classroom. Many CLTs have multiple classes to prep and can exceed 72 PCs. 2. Faculty and Staff need to have a transparent environment where they don't know that they are entering a virtual environment. The login will be handle by the preferred OS. 5. How would the customer like to achieve this? (List the functional requirements here) It should be handle by a unique url provided by rhev-manager once you tagged the VM to have "Instant View". The Instant View feature will by default open the spice in full screen via a web browser. 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. In rhev manager --> Virtual Machines --> select a VM --> click edit --> click console --> have a check mark with Instant View. When checked a url will appear next to it telling the user that this is the method to connect. When the user copies the url and paste it on a browser with the spice xpi plugin the remote viewer will open in full screen. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? No 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? RHEV 3.3 9. Is the sales team involved in this request and do they have any additional input? No and No 10. List any affected packages or components. I am not knowledgeable enough to know which packages or components will be affected. 11. Would the customer be able to assist in testing this functionality if implemented? Maybe, I will need to get some development equipment. Please check with me regarding this feature and I will do my best to test it out.
since they mention xpi and not activex, can i assume their clients are rhel 6? I'm not sure i understood the request. if they are already in the webadmin, clicking the VM, how is that different from just opening the console. is the idea to "bookmark" the url to allow later access without logging to rhev-m?
Let me ask the customer to confirm and I'll get back with you shortly.
"1. since they mention xpi and not activex, can i assume their clients are rhel 6? The client that I am using is rhel6. 2. if they are already in the webadmin, clicking the VM, how is that different from just opening the console. They are not in the webadmin because they will need to type a user name and password. The purpose of the request is to avoid seeing the portal and just have direct access to the VM. The end user does not need to know that the PC is virtualized. 3. is the idea to "bookmark" the url to allow later access without logging to rhev-m? bookmarking does not work. The end user still needs to enter a user name and password. I have tried several method of auto login but none have worked. Once the user logs into the user portal the console automatically opens the VM in full screen. By default you have full screen unchecked in the user portal." ---------------- The customer would like a way to connect to the VMs without a login whatsoever, as in their educational environment having to log each of the student computers into the admin/user portal and start the VM is very costly as far as time goes.
Something here might be of help to you. http://wiki.ovirt.org/How_to_Connect_to_SPICE_Console_Without_Portal
robert, i see two simple options: 1. they disable the ticketing 2. they do persistent ticketing both cases they'll need to use their own user portal - we have samples in python, java and ruby for a user portal. just to make sure i understand - they don't care at all which user connects to which vm, no security considerations, etc?
closing per no reply since september. please re-open if still relevant.