OADP-567: Document VolSync as a prerequisite for Tech Preview use of DataMover
OADP 1.1.0
Resolves: https://issues.redhat.com/browse/OADP-567
This bit of text will be added to the prerequisites for DataMover. The documentation for DataMover is being written by another writer, so this text will be added to that section.
LGTM
@sbeskin-redhat: Please review
@sbeskin-redhat Fixed the mistake.
@sbeskin-redhat -- great -- now you can copy/paste that into the Data Mover documentation you are writing...
Maya Peretz is telling me that there are lots of blockers and various issues in the workflow...
On Sun, Jul 17, 2022 at 3:39 PM Richard Hoch @.***> wrote:
@sbeskin-redhat https://github.com/sbeskin-redhat -- great -- now you can copy/paste that into the Data Mover documentation you are writing...
— Reply to this email directly, view it on GitHub https://github.com/openshift/openshift-docs/pull/47698#issuecomment-1186504893, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATJEI5MIRG2CH73UDAPHHNTVUP5G5ANCNFSM53LOSZRQ . You are receiving this because you were mentioned.Message ID: @.***>
-- *Sasha Beskin (*סשה בסקין) He/His/Him Technical Writer Red Hat Migration and Modernization Solutions Red Hat http://redhat.com Israel
https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png @.***
@sbeskin-redhat -- whenever you write the Data Mover documentation, please be sure to add this to the prerequisites. That's all I meant.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
@sbeskin-redhat You added this to your PR, right?
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
/remove-lifecycle rotten
@sbeskin-redhat please look into this after MTR GA. I think you took care of it, but it would be great if you could confirm. Thanks.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
/close
@RichardHoch: Closed this PR.
In response to this:
/close
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.