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

Fix(scheduler): use SpaceWeighted as the default scheduler #187

Merged
merged 1 commit into from
Apr 27, 2022

Conversation

nkwangleiGIT
Copy link
Contributor

@nkwangleiGIT nkwangleiGIT commented Apr 23, 2022

Pull Request template

Please, go through these steps before you submit a PR.

Why is this PR required? What issue does it fix?:
Fix issue #188

What this PR does?:
Use SpaceWeighted as the default scheduler

Does this PR require any upgrade changes?:
No

If the changes in this PR are manually verified, list down the scenarios covered::
1、Install openebs lvm
2、Create lvm storageclass(Use two K8S nodes for lvm provision)
3、Create PVC to use the sc above to provision LVM volume, to make sure it use the SpaceWeighted when schedule LVM volume

Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs

Checklist:

  • Fixes #
  • PR Title follows the convention of <type>(<scope>): <subject>
  • Has the change log section been updated?
  • Commit has unit tests
  • Commit has integration tests
  • (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
  • (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

PLEASE REMOVE BELOW INFORMATION BEFORE SUBMITTING

The PR title message must follow convention:
<type>(<scope>): <subject>.

Where:

  • type is defining if release will be triggering after merging submitted changes, details in CONTRIBUTING.md.
    Most common types are:

    • feat - for new features, not a new feature for build script
    • fix - for bug fixes or improvements, not a fix for build script
    • chore - changes not related to production code
    • docs - changes related to documentation
    • style - formatting, missing semi colons, linting fix etc; no significant production code changes
    • test - adding missing tests, refactoring tests; no production code change
    • refactor - refactoring production code, eg. renaming a variable or function name, there should not be any significant production code changes
  • scope is a single word that best describes where the changes fit.
    Most common scopes are like:

    • data engine (localpv, jiva, cstor)
    • feature (provisioning, backup, restore, exporter)
    • code component (api, webhook, cast, upgrade)
    • test (tests, bdd)
    • chores (version, build, log, travis)
  • subject is a single line brief description of the changes made in the pull request.

Copy link
Contributor

@pawanpraka1 pawanpraka1 left a comment

Choose a reason for hiding this comment

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

@nkwangleiGIT thanks for this PR.

@pawanpraka1
Copy link
Contributor

@nkwangleiGIT can you DCO signoff this PR?

Signed-off-by: nkwangleiGIT <nkwanglei@126.com>
@nkwangleiGIT
Copy link
Contributor Author

Signed-off-by: nkwangleiGIT nkwanglei@126.com
done

@pawanpraka1 pawanpraka1 merged commit 696c369 into openebs:develop Apr 27, 2022
@pawanpraka1
Copy link
Contributor

@nkwangleiGIT Would you like to mention your use case in our adopters(openebs/openebs#2719) file.

@nkwangleiGIT
Copy link
Contributor Author

@pawanpraka1 sure, I just need to add our user case here openebs/openebs#2719?

@pawanpraka1
Copy link
Contributor

@nkwangleiGIT that is right. You can put a comment describing your use case.

@nkwangleiGIT
Copy link
Contributor Author

sure, done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants