-
Feature
-
Resolution: Unresolved
-
Undefined
-
None
-
ACM 2.15.1
-
None
-
False
-
-
False
-
Not Selected
Feature Overview
...
Goals
This Section: Provide high-level goal statement, providing user context
and expected user outcome(s) for this feature
- Bharti Airtel use ACM to deploy, scale-out the cluster. They have also started using ACM for their EUS-EUS OCP upgrades. They want to consume ACM more going forward.
- As they have more than 150+ clusters and moving forward 300+ clusters in next 2 years. With this count, managing inventory is a challenge and will be more challenging going forward.
- Bharti Airtel is expecting a better format for the inventory from the ACM being a central site. The current feature of inventory is very basic and needs lot of manual work to format it.
- The requirement of the inventory is majorly with the below format
| Cloud Name | Cluster ID | HW OEM | RHOCP Version | Installation Method | ODF version | No of Worker basis the labels | Networking (IPv4/IPv6/dual-stack) |
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 a 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)?
