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

change bandwidth units from Kb to b #75442

Merged
merged 1 commit into from
Apr 25, 2019

Conversation

mars1024
Copy link
Member

@mars1024 mars1024 commented Mar 18, 2019

What type of PR is this?
/kind bug

What this PR does / why we need it:
CNI bandwidth plugin is designed to use bits-per-second and bits as the units of bandwidth rates and brust, and bandwidth plugin doc has changed its bandwidth related units from Kb to b in containernetworking/plugins@220499d, and CNI CONVENTIONS has also use b as its unit in containernetworking/cni@d2be2fa. So we have to change bandwidth unit from Kb to b in kubelet/cni.

none

Signed-off-by: Bruce Ma <brucema19901024@gmail.com>
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Mar 18, 2019
@k8s-ci-robot
Copy link
Contributor

Hi @mars1024. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. area/kubelet sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 18, 2019
@yue9944882
Copy link
Member

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 18, 2019
@dcbw
Copy link
Member

dcbw commented Mar 18, 2019

To be clear, it was the 'bandwidth' CNI plugin docs that were wrong. The implementation was always in bits-per-second.

@mars1024 can you add a release note as described in the first comment? that will remove the release note required label.

@mars1024
Copy link
Member Author

To be clear, it was the 'bandwidth' CNI plugin docs that were wrong. The implementation was always in bits-per-second.

@mars1024 can you add a release note as described in the first comment? that will remove the release note required label.

Sure, I will also update the pr comment.

@k8s-ci-robot k8s-ci-robot added release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Mar 19, 2019
@mars1024
Copy link
Member Author

/assign @dcbw

@mars1024
Copy link
Member Author

@dcbw PTAL, thx ~

@mars1024
Copy link
Member Author

/assign @freehan

@mars1024
Copy link
Member Author

mars1024 commented Apr 2, 2019

@freehan @dcbw PTAL, thx~

@mars1024
Copy link
Member Author

@freehan @dcbw friendly ping, thx ~

@thockin thockin removed the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Apr 24, 2019
@thockin thockin added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Apr 24, 2019
@thockin
Copy link
Member

thockin commented Apr 24, 2019

Is there actually action-required?

We should already be converting the annotation quantity into nominal units. This juts fixes a bug where we thought CNI wanted Kb but really it wanted b. As such, I do not think the release-note is right.

Otherwise it is a breaking change, and we have to have a bigger conversation.

Confirm?

@thockin
Copy link
Member

thockin commented Apr 24, 2019

Concretely, I think "NA" is a sufficient release note.

@freehan
Copy link
Contributor

freehan commented Apr 24, 2019

Is there any potential this will break users that depend on the wrong behavior?

I guess it will just looses the bandwidth limit, right?

@mars1024 mars1024 closed this Apr 25, 2019
@mars1024 mars1024 reopened this Apr 25, 2019
@mars1024
Copy link
Member Author

Is there any potential this will break users that depend on the wrong behavior?

I guess it will just looses the bandwidth limit, right?

Yes, it will just looses the bandwidth of newly created pods.

@mars1024
Copy link
Member Author

Concretely, I think "NA" is a sufficient release note.

OK, just as @freehan said above, if we do not think loosing is a breaking point, we need to set release note to NA.

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. labels Apr 25, 2019
@mars1024
Copy link
Member Author

@thockin @freehan I have set release note to NA.

@thockin
Copy link
Member

thockin commented Apr 25, 2019

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 25, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mars1024, thockin

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:

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 25, 2019
@k8s-ci-robot k8s-ci-robot merged commit f493761 into kubernetes:master Apr 25, 2019
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. area/kubelet cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note-none Denotes a PR that doesn't merit a release note. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants