Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OADP Datamover readthrough #69706

Merged
merged 1 commit into from
Dec 29, 2023

Conversation

RichardHoch
Copy link
Contributor

@RichardHoch RichardHoch commented Dec 28, 2023

OADP 1.3; OCP 4.11+

Resolves https://issues.redhat.com/browse/OADP-3185 by making a number of minor changes to the discussion of the pre-OADP 1.3 DataMover in the OADP user guide.

@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Dec 28, 2023
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Dec 28, 2023

🤖 Thu Dec 28 14:15:37 - Prow CI generated the docs preview: https://69706--ocpdocs-pr.netlify.app

@RichardHoch
Copy link
Contributor Author

/oadp
/peer-review-needed

@RichardHoch
Copy link
Contributor Author

Fixing a typo, so if we can go straight to merging, that would be appreciated.

@RichardHoch
Copy link
Contributor Author

/label oadp
/peer-review-needed

@openshift-ci openshift-ci bot added the OADP Label for all OADP PRs label Dec 28, 2023
@RichardHoch
Copy link
Contributor Author

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Dec 28, 2023
@snarayan-redhat snarayan-redhat added peer-review-in-progress Signifies that the peer review team is reviewing this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Dec 28, 2023
Copy link
Contributor

@snarayan-redhat snarayan-redhat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good. Couple of suggestions that may not be related to the changes that you are trying to fix. Just a good to have fix along with your current changes.

One of the changes seem to remove a statement regarding marking backup as complete which I feel needs a go ahead from QE. Let me know if I am missing something here.

@@ -16,8 +16,7 @@ The Data Mover solution uses the Restic option of VolSync.

Data Mover supports backup and restore of CSI volume snapshots only.

In OADP 1.2 Data Mover `VolumeSnapshotBackups` (VSBs) and `VolumeSnapshotRestores` (VSRs) are queued using the VolumeSnapshotMover (VSM). The VSM's performance is improved by specifying a concurrent number of VSBs and VSRs simultaneously `InProgress`. After all async plugin operations are complete, the backup is marked as complete.

In OADP 1.2 Data Mover, `VolumeSnapshotBackups` (VSBs) and `VolumeSnapshotRestores` (VSRs) are queued using the VolumeSnapshotMover (VSM). The VSM's performance is improved by specifying a concurrent number of VSBs and VSRs simultaneously `InProgress`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is more than just a typo. I think we need a QE approval here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@snarayan-redhat The sentence involved is no doubt true, but it has nothing to do with performance improvement, which is the subject of the paragraph. I will leave it in for now so we can fix the typo in the document.

modules/oadp-ceph-prerequisites.adoc Outdated Show resolved Hide resolved
@@ -16,8 +16,7 @@ The Data Mover solution uses the Restic option of VolSync.

Data Mover supports backup and restore of CSI volume snapshots only.

In OADP 1.2 Data Mover `VolumeSnapshotBackups` (VSBs) and `VolumeSnapshotRestores` (VSRs) are queued using the VolumeSnapshotMover (VSM). The VSM's performance is improved by specifying a concurrent number of VSBs and VSRs simultaneously `InProgress`. After all async plugin operations are complete, the backup is marked as complete.

In OADP 1.2 Data Mover, `VolumeSnapshotBackups` (VSBs) and `VolumeSnapshotRestores` (VSRs) are queued using the VolumeSnapshotMover (VSM). The VSM's performance is improved by specifying a concurrent number of VSBs and VSRs simultaneously `InProgress`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you wouldn't mind changing this one too? Thanks for considering.

Suggested change
In OADP 1.2 Data Mover, `VolumeSnapshotBackups` (VSBs) and `VolumeSnapshotRestores` (VSRs) are queued using the VolumeSnapshotMover (VSM). The VSM's performance is improved by specifying a concurrent number of VSBs and VSRs simultaneously `InProgress`.
In OADP 1.2 Data Mover, `VolumeSnapshotBackups` (VSBs) and `VolumeSnapshotRestores` (VSRs) are queued by using the VolumeSnapshotMover (VSM). The VSM's performance is improved by specifying a concurrent number of VSBs and VSRs simultaneously `InProgress`.

@snarayan-redhat snarayan-redhat added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Dec 28, 2023
@RichardHoch
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Dec 28, 2023
Copy link

openshift-ci bot commented Dec 28, 2023

@RichardHoch: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@snarayan-redhat snarayan-redhat added merge-review-in-progress Signifies that the merge review team is reviewing this PR branch/enterprise-4.11 branch/enterprise-4.12 branch/enterprise-4.13 branch/enterprise-4.14 branch/enterprise-4.15 and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Dec 29, 2023
@snarayan-redhat snarayan-redhat added this to the Continuous Release milestone Dec 29, 2023
@snarayan-redhat snarayan-redhat merged commit 97bce5d into openshift:main Dec 29, 2023
3 checks passed
@snarayan-redhat
Copy link
Contributor

/cherrypick enterprise-4.11

@snarayan-redhat
Copy link
Contributor

/cherrypick enterprise-4.12

@snarayan-redhat
Copy link
Contributor

/cherrypick enterprise-4.13

@snarayan-redhat
Copy link
Contributor

/cherrypick enterprise-4.14

@snarayan-redhat
Copy link
Contributor

/cherrypick enterprise-4.15

@openshift-cherrypick-robot

@snarayan-redhat: new pull request created: #69707

In response to this:

/cherrypick enterprise-4.11

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-cherrypick-robot

@snarayan-redhat: new pull request created: #69708

In response to this:

/cherrypick enterprise-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-cherrypick-robot

@snarayan-redhat: new pull request created: #69709

In response to this:

/cherrypick enterprise-4.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-cherrypick-robot

@snarayan-redhat: new pull request created: #69710

In response to this:

/cherrypick enterprise-4.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-cherrypick-robot

@snarayan-redhat: new pull request created: #69711

In response to this:

/cherrypick enterprise-4.15

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.11 branch/enterprise-4.12 branch/enterprise-4.13 branch/enterprise-4.14 branch/enterprise-4.15 merge-review-in-progress Signifies that the merge review team is reviewing this PR OADP Label for all OADP PRs peer-review-done Signifies that the peer review team has reviewed this PR size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants