OCP/Telco Definition of Done
Feature Template descriptions and documentation.
<--- Cut-n-Paste the entire contents of this description into your new Feature --->
<--- Remove the descriptive text as appropriate --->

Feature Overview

Unify installation experience of cluster 0.

an easy to use mechanism which will allow the user to install OCP cluster via a UI and API in a consistent manner with ACM and OCM.

Goals (WIP - open topics)

• Scope installation types - offline disconnected vs connected install
• Single/multi-cluster - is the node becoming part of the cluster or simply deploys multiple clusters
• platform type - BM/Virt/Cloud/hybrid
• UPI/IPI
• Distribution - RHCOS live vs Podman

Requirements

• Installation of all OCP deployment types multi-node, compact, RWN, SNO.
• 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.

(Optional) Use Cases

This Section:

• As a telco integrator i would like to install cluster from an unprivileged jumphost
• As a enterprise  IT admin, i would like to install my hub or standalone cluster in a disconnected environment
• As an integrator i would like to install many standalone clusters but not tied to a central hub
• As an entrprise IT i would like to install any type of cluster installation whether on-prem or cloud (managed or self-managed) like i do with Rancher
• As devops person i would like to install HyperShift tugboat/Armada  

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