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-1067: Design for Batching VSM CRs #179

Merged
merged 4 commits into from Jan 17, 2023

Conversation

eemcmullan
Copy link
Collaborator

No description provided.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 14, 2022
@weshayutin
Copy link
Collaborator

+1 that looks nice and clear to me. Thank you @eemcmullan!

docs/design/batching.md Outdated Show resolved Hide resolved
docs/design/batching.md Outdated Show resolved Hide resolved
docs/design/batching.md Outdated Show resolved Hide resolved
docs/design/batching.md Outdated Show resolved Hide resolved
@eemcmullan eemcmullan requested review from sseago and kaovilai and removed request for sseago December 16, 2022 19:39
docs/design/batching.md Outdated Show resolved Hide resolved

If `dpa.spec.dataMover.concurrentBackupVolumes` or
`dpa.spec.dataMover.concurrentRestoreVolumes` is not set or it is set to zero,
then a default value will be used. This value is TBD.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Hmm. I'm wondering how this would work if a user wants to set it to zero, meaning "no limit". For example, if the default is 12, then a user setting this to 0 will result in the default of 12 being used. Maybe we don't allow "no limit" -- but practically speaking, the user can still have "no limit" by setting it to 1000 or something similarly huge.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I guess one way to allow unlimited would be to implement the setting as an int pointer rather than an int -- that way we can distinguish between "not present; use default" (i.e. value is nil) and "unlimited" (value is 0; use this rather than default)" Thinking more about it, I'm leaning towards this. If we want "not specified" to mean "use the default" then we want the spec field to be *int64 rather than int64, so that 0 won't be overridden by the default.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I agree, this approach sounds more reasonable. Will update with these details.

docs/design/batching.md Outdated Show resolved Hide resolved
`volumeSnapshotRestores` if it is not set. Another option is to defing constants
such as `DefaultConcurrentBackupVolumes` and `DefaultConcurrentRestoreVolumes`
that can be set to a determined number, such as 0 or 12. More discussion is needed
around this topic.
Copy link
Collaborator

Choose a reason for hiding this comment

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

If 0 means "unlimited" then we don't really need to know which option we're using in the design -- when we decide the default value, then it's just a matter of assigning the const in the golang file. If the default is zero, then it's unlimited -- if it's another number, then it's limited to that.

@openshift-ci
Copy link

openshift-ci bot commented Dec 22, 2022

@sseago: changing LGTM is restricted to collaborators

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.

docs/design/batching.md Outdated Show resolved Hide resolved
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 17, 2023
Copy link
Contributor

@dymurray dymurray left a comment

Choose a reason for hiding this comment

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

LGTM

@openshift-ci
Copy link

openshift-ci bot commented Jan 17, 2023

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

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

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

@dymurray dymurray merged commit 1da3f2b into migtools:master Jan 17, 2023
@eemcmullan eemcmullan deleted the batch-design branch January 30, 2023 16:18
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants