Skip to content

OADP-1821: storageClass mapping for data mover volumeOptions#1006

Merged
weshayutin merged 13 commits intoopenshift:masterfrom
eemcmullan:sc-mapping
May 19, 2023
Merged

OADP-1821: storageClass mapping for data mover volumeOptions#1006
weshayutin merged 13 commits intoopenshift:masterfrom
eemcmullan:sc-mapping

Conversation

@eemcmullan
Copy link
Contributor

@eemcmullan eemcmullan commented May 15, 2023

No description provided.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 15, 2023
@openshift-ci
Copy link

openshift-ci bot commented May 15, 2023

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 15, 2023
// defines configurations for data mover volume options for a storageClass
// +optional
DataMoverVolumeOptions *DataMoverVolumeOptions `json:"volumeOptions,omitempty"`
StorageClass map[string]DataMoverVolumeOptions `json:"storageClass,omitempty"`
Copy link
Member

Choose a reason for hiding this comment

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

Are we just removing volumeoptions in general?
Thought we were looking to expose the useMoverContext elsewhere.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is a separate issue from securityContext. This is to create a mapping of storgeClasses to volumeOptions

Copy link
Contributor

Choose a reason for hiding this comment

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

The name is confusing. Calling it StorageClass makes it look like the value is the name of a storage class rather than a mapping of storage classes to volume options. The original DataMoverVolumeOptions name might be better, or maybe DataMoverVolumeOptionsForStorageClasses (or shortened to VolumeOptionsForStorageClasses)

@eemcmullan eemcmullan marked this pull request as ready for review May 16, 2023 16:30
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 16, 2023
@eemcmullan
Copy link
Contributor Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 16, 2023
@eemcmullan eemcmullan changed the title storageClass mapping for data mover volumeOptions OADP-1821: storageClass mapping for data mover volumeOptions May 17, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 17, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 17, 2023

@eemcmullan: This pull request references OADP-1821 which is a valid jira issue.

Details

In response to this:

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.

@weshayutin
Copy link
Contributor

/test 4.10-operator-e2e-gcp

@kaovilai
Copy link
Member

/test 4.11-operator-unit-test

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 18, 2023
@shubham-pampattiwar
Copy link
Member

@eemcmullan Please resolve the conflicts on this PR.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 18, 2023
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 19, 2023
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label May 19, 2023
@shubham-pampattiwar
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 19, 2023
@openshift-ci
Copy link

openshift-ci bot commented May 19, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eemcmullan, kaovilai, shubham-pampattiwar, sseago

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [eemcmullan,kaovilai,shubham-pampattiwar,sseago]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@shubham-pampattiwar
Copy link
Member

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 19, 2023
@shubham-pampattiwar
Copy link
Member

/cherry-pick oadp-1.2

@openshift-cherrypick-robot
Copy link
Contributor

@shubham-pampattiwar: once the present PR merges, I will cherry-pick it on top of oadp-1.2 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick oadp-1.2

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.

@eemcmullan
Copy link
Contributor Author

/test 4.10-operator-e2e-aws

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label May 19, 2023
@openshift-ci
Copy link

openshift-ci bot commented May 19, 2023

New changes are detected. LGTM label has been removed.

@weshayutin weshayutin merged commit 3a430a3 into openshift:master May 19, 2023
@openshift-ci
Copy link

openshift-ci bot commented May 19, 2023

@eemcmullan: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/4.10-operator-e2e-gcp df9357e link true /test 4.10-operator-e2e-gcp

Full PR test history. Your PR dashboard.

Details

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.

@openshift-cherrypick-robot
Copy link
Contributor

@shubham-pampattiwar: #1006 failed to apply on top of branch "oadp-1.2":

Applying: SC to datamover api
Using index info to reconstruct a base tree...
M	api/v1alpha1/oadp_types.go
M	api/v1alpha1/zz_generated.deepcopy.go
M	config/crd/bases/oadp.openshift.io_dataprotectionapplications.yaml
M	controllers/datamover.go
M	tests/e2e/lib/dpa_helpers.go
Falling back to patching base and 3-way merge...
Auto-merging tests/e2e/lib/dpa_helpers.go
CONFLICT (content): Merge conflict in tests/e2e/lib/dpa_helpers.go
Auto-merging controllers/datamover.go
Auto-merging config/crd/bases/oadp.openshift.io_dataprotectionapplications.yaml
CONFLICT (content): Merge conflict in config/crd/bases/oadp.openshift.io_dataprotectionapplications.yaml
Auto-merging api/v1alpha1/zz_generated.deepcopy.go
Auto-merging api/v1alpha1/oadp_types.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 SC to datamover api
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherry-pick oadp-1.2

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.

kaovilai added a commit to kaovilai/oadp-operator that referenced this pull request May 19, 2023
…ft#1006)

* SC to datamover api

* check for existing sc in cluster

* bundle updates

Co-authored-by: Emily McMullan <[email protected]>

* Use typed strings for accessMode

Signed-off-by: Tiger Kaovilai <[email protected]>

* Add spec.features.datamover.storageclass to e2e with provider storageclass name.

Signed-off-by: Tiger Kaovilai <[email protected]>

* rename volumeoptions sc

* update crds

* Fix `ProviderStorageClassName()` relative path

Signed-off-by: Tiger Kaovilai <[email protected]>

---------

Signed-off-by: Tiger Kaovilai <[email protected]>
Co-authored-by: Tiger Kaovilai <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants