-
Feature
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
Feature Overview
In order to reduce operational problems once an environment is upgraded, and to ensure like-for-like functional parity, an environment which has been upgraded and a freshly deployed environment should look the same.
The same should be true for a scaled-up new host in an environment that is freshly deployed or scaled up.
If there are any deviations from this pattern, they should be clearly noted in the documentation with the rationale behind the difference.
Currently it is required to run the update process on a scaled-up node in order to ensure that the node is up to date. This extends the time taken considerably.
Goals
This feature benefits operations teams by reducing operational problems after environment upgrades. It ensures consistency and parity between upgraded and freshly deployed environments, minimizing potential issues caused by discrepancies in package versions, installed packages, and container versions. The feature aims to streamline the deployment and upgrade process, saving time and effort for the teams involved.
Requirements
| Requirements | Notes | isMvp? |
|---|---|---|
| Containers installed on the upgraded host and fresh installed host should be same | ||
| Containers versions installed on the upgraded host and fresh installed host should be same | ||
| Package installed on the upgraded host and fresh installed host should be same | ||
| Package versions installed on the upgraded host and fresh installed host should be same | ||
(Optional) Use Cases
< How will the user interact with this feature? >
< Which users will use this and when will they use it? >
< Is this feature used as part of current user interface? >
Out of Scope
Background, and strategic fit
< What does the person writing code, testing, documenting need to know? >
Assumptions
< Are there assumptions being made regarding prerequisites and dependencies?>
< Are there assumptions about hardware, software or people resources?>
Customer Considerations
< Are there specific customer environments that need to be considered (such as working with existing h/w and software)?>
< Are there upgrade considerations that customers need to account for or that the feature should address on behalf of the customer?>
Documentation Considerations
If there are any deviations from an upgraded environment and fresh installed deployment, they should be clearly noted in the documentation with the rationale behind the difference.
Interoperability Considerations
< Which other products and versions in our portfolio does this feature impact?>
< What interoperability test scenarios should be factored by the layered product(s)?>
Questions
| Question | Outcome |
|---|---|
Related to
https://bugzilla.redhat.com/show_bug.cgi?id=2082054