Uploaded image for project: 'OpenShift Top Level Product Strategy'
  1. OpenShift Top Level Product Strategy
  2. OCPPLAN-7587

Factory install of relocatable OpenShift and configure at customer location [ZTPFW]

    XMLWordPrintable

Details

    • False
    • False
    • ?
    • No
    • ?
    • ?
    • ?
    • 61
    • 61% 61%

    Description

      Feature Overview

      • As RH, I want to enable OpenShift to be deployed on a OEM partner's prescribed hardware in order to enable factory installations of OpenShift at scale.
      • As a RH OEM partner, I want to install OpenShift on my hardware devices at my factory, then ship the devices to end customers (for use at the edge), where the devices can be configured with minimal effort by a low-skilled technician.
      •  

      Goals

      • Install OpenShift at the factory, and deploy at customer location with minimum domain-specific (OpenShift or Kube) expertise required. 

       

      Requirements

      • This Section:* A list of specific needs or objectives that a Feature must deliver to satisfy the Feature.. Some requirements will be flagged as MVP. If an MVP gets shifted, the feature shifts. If a non MVP requirement slips, it does not shift the feature.
      Requirement Notes isMvp?
      CI - MUST be running successfully with test automation This is a requirement for ALL features. YES
      Release Technical Enablement Provide necessary release enablement details and documents. YES

      (Optional) Use Cases

      This Section:

      • Main success scenarios - high-level user stories
      • Alternate flow/scenarios - high-level user stories
      • ...

      Questions to answer...

      • ...

      Out of Scope

      • ...

      Background, and strategic fit

      This Section: What does the person writing code, testing, documenting need to know? What context can be provided to frame this feature.

      Assumptions

      • ...

      Customer Considerations

      • ...

      Documentation Considerations

      Questions to be addressed:

      • What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?
      • Does this feature have doc impact?
      • New Content, Updates to existing content, Release Note, or No Doc Impact
      • If unsure and no Technical Writer is available, please contact Content Strategy.
      • What concepts do customers need to understand to be successful in [action]?
      • How do we expect customers will use the feature? For what purpose(s)?
      • What reference material might a customer want/need to complete [action]?
      • Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available.
      • What is the doc impact (New Content, Updates to existing content, or Release Note)?

       

      References

      Attachments

        Issue Links

          Activity

            People

              julim Ju Lim
              tkatarki@redhat.com Tushar Katarki
              Scott Suehle Scott Suehle
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: