-
Notifications
You must be signed in to change notification settings - Fork 116
fix(BD-labels):add device attributes and location details as bd labels #618
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
Conversation
Signed-off-by: Abhishek Agarwal <[email protected]>
This pull request introduces 1 alert when merging 8fdf4f5 into 426eeaa - view on LGTM.com new alerts:
|
This pull request introduces 2 alerts when merging 3ef8aa5 into 426eeaa - view on LGTM.com new alerts:
|
Signed-off-by: Abhishek Agarwal <[email protected]>
Codecov Report
@@ Coverage Diff @@
## develop #618 +/- ##
===========================================
- Coverage 46.09% 44.87% -1.23%
===========================================
Files 78 79 +1
Lines 3820 3964 +144
===========================================
+ Hits 1761 1779 +18
- Misses 1901 2018 +117
- Partials 158 167 +9
Continue to review full report at Codecov.
|
This pull request introduces 2 alerts when merging dca0b0f into 426eeaa - view on LGTM.com new alerts:
|
Signed-off-by: Abhishek Agarwal <[email protected]>
This pull request introduces 2 alerts when merging f274c21 into 426eeaa - view on LGTM.com new alerts:
|
This pull request introduces 2 alerts when merging ad03f13 into 426eeaa - view on LGTM.com new alerts:
|
Signed-off-by: Abhishek Agarwal <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@a4abhishek a few more nitpick comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a comment on the generated operator file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Abhishek Agarwal <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Need to add a reference link to the original code from the k8s repo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks for working on this.
BlockDeviceTag cas-config option was replaced by BlockDeviceSelectors. Updating website documentation... Github doc link --> https://github.com/openebs/dynamic-localpv-provisioner/blob/develop/docs/tutorials/device/blockdeviceselectors.md Relevant PRs: - openebs/dynamic-localpv-provisioner#106 - openebs/dynamic-localpv-provisioner#125 - openebs-archive/node-disk-manager#618
Add `metaconfigs` capability introduced in openebs-archive/node-disk-manager#618 fixes 338 Signed-off-by: cmontemuino <[email protected]>
Add `metaconfigs` capability introduced in openebs-archive/node-disk-manager#618 fixes 338 Signed-off-by: cmontemuino <[email protected]>
Signed-off-by: Abhishek Agarwal [email protected]
Why is this PR required? What issue does it fix?:
issue- #615
What this PR does?:
This PR adds some generic labels to the block device resources which are already present inside the BD CR spec along with some topology(location) details as labels for the block devices to be able to easily classify devices on the basis of these labels.
The labels will be added by making use of ndm configmap. The update that configmap requires is the addition of new field
metaconfigs
:Does this PR require any upgrade changes?:
If the changes in this PR are manually verified, list down the scenarios covered::
Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>