Undefined Feature Overview (aka. Goal Summary)
An elevator pitch (value statement) that describes the Feature in a clear, concise way. Complete during New status.
4.12 EOL is approaching. We need to make sure we handle the EOL properly.
4.12 EOL is Jul 17.
Goals (aka. expected user outcomes)
The observable functionality that the user now has as a result of receiving this feature. Complete during New status.
- Confirm notifications are sent to customers as specified by our communication plan
Requirements (aka. Acceptance Criteria):
A list of specific needs or objectives that a feature must deliver in order to be considered complete. Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc. Initial completion during Refinement status.
| Supported Clients | Option |
|---|---|
| Supported in ROSA cli | (x ) Yes ( ) No ( ) N/A |
| Supported in OCM cli | ( ) Yes ( ) No (x ) N/A |
| Supported in OCM UI | (x ) Yes ( ) No ( ) N/A |
| Supported in TF | ( ) Yes ( ) No (x ) N/A |
| Supported in Capi | ( ) Yes ( ) No x( ) N/A |
| Supported Offerings | Option |
| Fedramp supported? | ( ) Yes ( ) No ( x) N/A |
| OCP Support | Option |
| Is it already supported in OCP? | ( x) Yes ( ) No ( ) N/A |
| If Yes, what OCP version ? |
Use Cases (Optional):
Include use case diagrams, main success scenarios, alternative flow scenarios. Initial completion during Refinement status.
1. We have OCM-CS API checking for OCP versions when allowing for configurations of clusters that become obsolete after particular OCP version EOLs. e.g., we check OCP 4.11 before enabling IMDS configuration. Similarly there are checks for enabling additional SGs based on OCP Versions.
Questions to Answer (Optional):
Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.
Out of Scope
High-level list of items that are out of scope. Initial completion during Refinement status.
Background
Provide any additional context is needed to frame the feature. Initial completion during Refinement status.
Customer Considerations
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature. Initial completion during Refinement status.
Documentation Considerations
Provide information that needs to be considered and planned so that documentation will meet customer needs. Initial completion during Refinement status.
Interoperability Considerations
Which other projects and versions in our portfolio does this feature impact? What interoperability test scenarios should be factored by the layered products? Initial completion during Refinement status.
