Bug 1020408
| Summary: | PRD34 - [RFE] CFME would like to have RHEV emit events for Remote Console Connect | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Greg Blomquist <gblomqui> |
| Component: | ovirt-engine | Assignee: | Oved Ourfali <oourfali> |
| Status: | CLOSED ERRATA | QA Contact: | meital avital <mavital> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.2.0 | CC: | acathrow, ecohen, gblomqui, gklein, iheim, lbopf, lpeer, mavital, michal.skrivanek, oourfali, Rhev-m-bugs, sbonazzo, sherold, yeylon |
| Target Milestone: | --- | Keywords: | FutureFeature, Improvement |
| Target Release: | 3.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | virt | ||
| Fixed In Version: | ovirt-3.4.0-beta2 | Doc Type: | Enhancement |
| Doc Text: |
Red Hat Enterprise Virtualization Manager now raises events when a user connects or disconnects from a virtual machine console session.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-09 15:00:21 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1009120, 1078909, 1142926 | ||
|
Description
Greg Blomquist
2013-10-17 15:35:57 UTC
Will add a SetVmTicket event, which will be triggered, as mentioned in the bug description, when the user clicks the console button in the web UI. bear in mind setVmTicket doesn't mean the console is actually opened. You can ask for the ticket but then simply do not open the viewer Is that good enough? Michal and Oved, I think that setVmTicket might be enough. But, I'd like to understand a little more. Does the user actually take two separate actions? For instance, 1) request vm ticket, 2) connect to the console? Or, is this all triggered from the same action in the UI? If it's all the same action, then I think that setVmTicket is fine. in UI it's a single action invoking two different things, setVmTicket and then the actual console invocation(or .vv file download expecting user to associate and launch the application with it). In normal circumstances it should always happen together, but it may not if you do this programmatically or if the app launch phase fails That makes sense. SetVmTicket should be fine, then. Thanks! SetVmTicket is "user requested to access the VM" and we set the ticket. user may or may not actually connect to the console after that (which can be detected based on the ClientIP field changing iirc) If that's more accurate then I can add a new event for a client IP change, specifying that a user has connected (assuming the address isn't empty). (In reply to Oved Ourfali from comment #7) well, it's more accurate but not really reliable as the guest may not be running the guest agent. The ticket should be good enough as long as it's clear what it means (requested access vs actual connect) Or maybe have two events? Not sure if it's of any use in CFME though I'll just add both of them. The SetVmTicket log entry today says: user admin@internal initiated console session for VM new_vm1 The new one will say that the user is connected / disconnected. That way we're covered in all the cases, and CFME can use either both of them, or just one of them. Verified according to those bugs: https://bugzilla.redhat.com/show_bug.cgi?id=953540 https://bugzilla.redhat.com/show_bug.cgi?id=1039862 https://bugzilla.redhat.com/show_bug.cgi?id=1016844 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0506.html |