-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
Not Selected
-
100% To Do, 0% In Progress, 0% Done
Feature Overview
Customers are looking for a way to have multiple concurrent sessions to the same VM. All sessions should have read / write access. The connection should remain open throughout the session and should not be affected by LiveMigration.
The connection should be available even if the VM is not connected to the network
Goals
The goal of this feature is to provide users stable connections to a VM, regardless how many other users are connected to the same VM. This connection should persist during LiveMigration of the VM within the same cluster.
- Multiple connections are used for things like VM troubleshooting, configuration etc.
- In the current implementation we set VNC to allow single remote connection. Any additional connection (even in the VM details page), disconnect the previous connection
Requirements
Requirement | Notes | isMvp? |
---|---|---|
Resolution does not change with disconnect/reconnect/multiple connect | This may be an issue for UI automation - specifically in Windows | Y |
The amount of connected Users to a single VM needs to be shown to all connected users that can write to the session | This is for security reason - e.g. opening a passowrd vault could reveal pws to all connected users | Y |
The Kubernetes API must not be overloaded with the additional connections | This will probably mean to move the connections to a connection broker instead | Y |
The console session must not be terminated on live migration | N | |
(Optional) Use Cases
How will the user interact with this feature?
Which users will use this and when will they use it?
- Include use case diagrams, main success scenarios, alternative flow scenarios. Initial completion during Refinement status.
<your text here>
Questions to answer...
Out of Scope
- High-level list of items that are out of scope. Initial completion during Refinement status.
<your text here>
**
Background, and strategic fit
Provide any additional context is needed to frame the feature. Initial completion during Refinement status.
<your text here>
Assumptions
- <your text here>
Customer Considerations
- Provide any additional customer-specific considerations that must be made when designing and delivering the Feature. Initial completion during Refinement status.
<your text here>
Documentation Considerations
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.
<your text here>
- is related to
-
CNV-59656 CNV - Option to connect multiple monitors/ VNC consoles for Openshift Virtualization VMs
-
- Refinement
-
-
CNV-63955 [Doc] scenarios for vnc and serial console
-
- New
-
-
CNV-60117 Regular VNC console disconnect, due to competing request between the VNC thumbnail, and a full screen VNC view.
-
- POST
-
-
CNV-64791 VNC Multi connection - tracker bug
-
- Closed
-
- relates to
-
CNV-59656 CNV - Option to connect multiple monitors/ VNC consoles for Openshift Virtualization VMs
-
- Refinement
-
-
CNV-59657 Option to connect multiple monitors/ VNC consoles for Openshift Virtualization VMs
-
- Closed
-
-
CNV-24222 Checking compatibility of Guacamole with VNC proxy service
-
- Closed
-
- split to
-
CNV-44596 Seamless Console Connectivity During Live Migration
-
- Refinement
-
- links to