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

[UI] Provide an option to change runStrategy of VM

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • CNV User Interface
    • None
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected

      Feature Overview

      An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

      runStrategy provides the ability to define whether a VM should automatically restart in cases it is stopped or crashed. This will allow users to set that behavior from the UI 

      Goals
      Provide high-level goal statement, providing user context and expected user outcome(s) for this Initiative

      • Who benefits from this feature, and how? This will allow users to have better control on when a VM should automatic restart. This will also create a consistent behavior of VMs auto start regardsless of the why they were shutdown 
      • What is the difference between today’s current state and a world with this feature? Today VMs that are created from the CLI or are set to start after creation will have this set to "Always". VMs that are created with the UI but are not set to start after creation are set to "Halted". On top of that, VM that are shutdown from within the guest may automatically restart when they are set to "Always". This will allow users to set the automatic start method to all supported values as different customers may have different expectation of this

      Requirements

      Requirement Notes isMvp?
           
           
           
           
           

      (Optional) Use Cases

      How will the user interact with this feature? 
      Which users will use this and when will they use it?

      • Need to be able to set this on the entire cluster, at a single VM level and on multiple VMs at ones

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

       

      User Experience Considerations

      Provide information that needs to be considered and planned so that the user experience will meet customer needs. These could include impacts to the UI or other areas of the user experience, as well as user research needs. Please add the 'UXD' component to this JIRA if there are User Experience considerations. Initial completion during Refinement status.
      <your text here>

              mschatzm@redhat.com Matan Schatzman
              rsdeor Ronen Sde-Or
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: