-
Feature
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
False
-
-
False
-
?
-
?
-
0% To Do, 0% In Progress, 100% Done
-
-
-
Approved
Feature Overview
As an Operator I would like to separate the OpenStack Update process from the OS Update process (when reboot is needed)
Goals
Limit the data plane interruption during the update process.
Requirements
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips, it does not shift the feature.
| Requirements | Notes | isMvp? |
|---|---|---|
| No data plane interruption during the update process | ||
| Some degraded performance on the control plane during the update process | ||
| Successfully updated an OSP Next Gen adopted field deployment | ||
| Successfully updated an OSP Next Gen green field deployment |
Out of Scope
TBD
Documentation Considerations
TBD
Interoperability Considerations
Questions
| Question | Outcome |
|---|---|
- blocks
-
OSPRH-1048 RHOSO 18 updates at scale
-
- Backlog
-
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
-
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
