-
Notifications
You must be signed in to change notification settings - Fork 254
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Support multi-stage imports in import populator (#2767)
* Update VolumeImportSource API to support multi-stage imports This commit modifies the VolumeImportSource API to support multi-stage imports, adding the following fields: - Checkpoints, to represent the stages of a multistage import - TargetClaim, the name of the specific PVC to be imported - FinalCheckpoint, to indicate that the current Checkpoint is the final one Signed-off-by: Alvaro Romero <alromero@redhat.com> * Support multi-stage imports in import-populator This commit updates the import populator to support multi-stage imports. The API and functionality remains the same as with DataVolumes, with the only difference that the used VolumeImportSource will now require a populated "TargetClaim" field that reffers to the specific PVC to be populated. The DataVolume controller is also updated to allow using the populator flow with VDDK and ImageIO sources. Signed-off-by: Alvaro Romero <alromero@redhat.com> * Add unit tests for multistage import support in populators Signed-off-by: Alvaro Romero <alromero@redhat.com> * Add functional tests to test multistage import populator flow Signed-off-by: Alvaro Romero <alromero@redhat.com> * Fix multi-stage import logic in import-populator and add remaining tests This commit fixes several bugs in the import-populator logic for multi-stage imports. Signed-off-by: Alvaro Romero <alromero@redhat.com> --------- Signed-off-by: Alvaro Romero <alromero@redhat.com>
- Loading branch information
Showing
25 changed files
with
859 additions
and
314 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.