-
Epic
-
Resolution: Done
-
Normal
-
None
-
cnv-fsx-validation
-
-
Green
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
doc-ready, qe-ready
-
Goal
Do additional validation on top of orginal spike that confirmed that FSx generally works and can be used with CNV on AWS BM.
On this epic we want to be sure that we cover more scenarios and also make sure we put a mechanism in place to catch regressions along the way.
User Stories
- High-Level goal-based user story, with context.
"As a <VM Owner/Cluster Admin>, I want <to Achieve Some Goal>, so that <Some Reason/Context>." - another user story
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
- Any additional details or decisions made/needed
1.
|
upstream roadmap issue | Closed | Adam Litke | ||
2.
|
upstream documentation | Closed | Adam Litke | ||
3.
|
upgrade consideration | Closed | Unassigned | ||
4.
|
CEE/PX summary presentation | Closed | Adam Litke | ||
5.
|
test plans in polarion | Closed | Unassigned | ||
6.
|
automated tests | Closed | Unassigned | ||
7.
|
downstream documentation merged | Closed | Unassigned |