Uploaded image for project: 'Virtualization Strategy'
  1. Virtualization Strategy
  2. VIRTSTRAT-488

Multi-sessions remote console

XMLWordPrintable

    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • 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 
       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 
       The Kubernetes API must not be overloaded with the additional connections This will probably mean to move the connections to a connection broker instead 
       The console session must not be terminated on live migration  
           

      (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

      1. 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>

       

              dholler@redhat.com Dominik Holler
              rsdeor Ronen Sde-Or
              Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: