-
Epic
-
Resolution: Obsolete
-
Critical
-
None
-
None
-
None
-
Backup & Restore for RHOSP 18.0 using OpenShift API for Data Protection
-
False
-
-
False
-
Proposed
-
Proposed
-
Done
-
Proposed
-
Proposed
-
0% To Do, 0% In Progress, 100% Done
-
2024Q1
Epic Overview
This epic focuses on implementing data protection for RHOSO control plane by leveraging the OpenShift API for backup and restore functionality (OADP).
Goals
The main beneficiaries of this epic are system administrators, DevOps teams, and any stakeholders involved in ensuring the reliability and availability of RHOSO control plane.
Requirements
A list of specific needs or objectives with a designation of MVP (Minimum Viable Product) where applicable.
| Requirements | Notes | isMvp? |
|---|---|---|
| Document the RHOSO control plane backup using OADP | Yes | |
| Document the RHOSO control plane restore using OADP | Yes | |
| Define backup frequency and retention policies | Specify how often backups should occur and how long they should be retained | No |
| Logging and reporting for backup and restore operations | Provide detailed logs and reports for monitoring and auditing purposes | No |
(Optional) Use Cases
- Administrators triggering manual backups or restores via the OpenShift OADP API before an RHOSO update
- Administrators triggering manual backups or restores via the OpenShift OADP API before an RHOSO upgrade
- Scheduled automated backups of the application data.
- Restoring the application to a specific point in time using backup data.
< Which users will use this and when will they use it? >
System administrators will interact with this epic especially during updates and upgrades of the RHOSO platform.
< Is this feature used as part of the current user interface? >
No, the functionality is primarily accessed and managed through the OpenShift API and related command-line tools.
Out of Scope
- Integration with external backup solutions not leveraging the OpenShift API.
- Support for specific storage solutions not compatible with OpenShift API.
Assumptions
- The OpenShift cluster is properly configured and accessible,
- Storage is properly configured
- Adequate storage space is available for storing backups.
Documentation Considerations
- A new context needs to be created evolving the next following guides:
<Is there source material that can be used as a reference for the Technical Writer in writing the content? If yes, please link if available.>
OpenShift API documentation, application documentation related to backup and restore procedures.
<What is the doc impact (New Content, Updates to existing content, or Release Note)?>
New Content
Interoperability Considerations
- Verify interoperability with different storage solutions supported by OpenShift.
Questions
| Question | Outcome |
|---|---|
| How often should automated backups occur? | Define backup frequency and retention policies |
| What is the process for restoring the application from backup data? | Provide detailed documentation for the restore process |
- mentioned in
-
Page Loading...