Value Statement

Review with the Observability and CIM teams their component architecture and the need to backup PV data using the hub backup support.

Definition of Done for Engineering Story Owner (Checklist)

• What we wanted to get out of this : 
  • contact the teams ( CIM and Observability) and make them aware that DR recovery for their component requires to include PV recovery in 2.8
  • discuss what is missing in terms of persistent data recovery for their components
  • discuss what should be done to address issues with how the persistent data is recovered for these components
  • come up with a plan of action

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.