Skip to content

Add Node API in config/v1 #1107

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
harche:node_object
Mar 2, 2022
Merged

Add Node API in config/v1 #1107
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
harche:node_object

Conversation

@harche
Copy link
Copy Markdown
Contributor

@harche harche commented Feb 1, 2022

This PR adds the Node API in config/v1 that holds cluster-wide information about node specific features.

Node API was proposed in the cgroups v2 enhancement and later further modified in WorkerLatencyProfile enhancement to suite those use cases.

Signed-off-by: Harshal Patil harpatil@redhat.com
Signed-off-by: Ryan Phillips rphillip@redhat.com
Signed-off-by: Swarup Ghosh swghosh@redhat.com

@openshift-ci openshift-ci bot requested review from knobunc and mfojtik February 1, 2022 03:46
@harche
Copy link
Copy Markdown
Contributor Author

harche commented Feb 1, 2022

/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 Feb 1, 2022
@harche harche force-pushed the node_object branch 2 times, most recently from 571a5c3 to e8c2872 Compare February 1, 2022 06:17
@harche
Copy link
Copy Markdown
Contributor Author

harche commented Feb 1, 2022

/test verify

@harche harche force-pushed the node_object branch 3 times, most recently from 2c68e6b to 94ca794 Compare February 1, 2022 10:31
@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 Feb 1, 2022
@harche harche changed the title WIP: Add node object WIP: Add node API in config/v1 Feb 1, 2022
@harche harche changed the title WIP: Add node API in config/v1 WIP: Add Node API in config/v1 Feb 1, 2022
@harche harche changed the title WIP: Add Node API in config/v1 Add Node API in config/v1 Feb 1, 2022
@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 Feb 1, 2022
@harche
Copy link
Copy Markdown
Contributor Author

harche commented Feb 1, 2022

/hold cancel

@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 Feb 1, 2022
@harche
Copy link
Copy Markdown
Contributor Author

harche commented Feb 1, 2022

/cc @soltysh @rphillips @swghosh

@rphillips
Copy link
Copy Markdown
Contributor

/lgtm

This is what we agreed to in the enhancement.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 1, 2022
@openshift-ci openshift-ci bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Feb 3, 2022
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 4, 2022
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 7, 2022
@harche
Copy link
Copy Markdown
Contributor Author

harche commented Feb 7, 2022

/hold till #1114 is addressed.

@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 Feb 7, 2022
@harche
Copy link
Copy Markdown
Contributor Author

harche commented Feb 7, 2022

/hold till #1114 is addressed.

Removing the hold because the issue is not related to PR. It's reproducible even without the changes from this RP.

/hold cancel

@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 Feb 7, 2022
CgroupMode_Empty = "" // Empty string will always use the Default
CgroupMode_v1 = "v1"
CgroupMode_v2 = "v2"
CgroupMode_Default = CgroupMode_v1
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Don't use _ in names, we rarely do that, instead use CGroupV1, CGroupV2. I'd suggest dropping CgroupMode_Default entirely, same with CgroupMode_empty both are expressed as empty/not set. No need to add these as constants. Just be explicit that when not set default v1 is used on the field itself.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@rphillips for the comment on cgroups

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Same comment as before. cgroup v2 is the name, and the correct name is Cgroup.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This naming is carried over from the enhancement... The naming should stay the same.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Fine with the naming, but the part about empty vs default still applies, both mean the exact same thing so I'd only add v1 and v2.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@deads2k mentioned adding support for empty and default.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@deads2k mentioned adding support for empty and default.

Please keep empty. Empty avoids pointers, allows an empty object to succeed, and clearly distinguishes between "choose a good default for me" and "I definitely want v1".

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Ack

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

There are still 3 nits to get it merged:

  1. CgroupModeEmpty instead of CgroupMode_Empty to follow all the other types we have, ie. don't use _ in the name
  2. you need to explicitly tell that CgroupModeEmpty is of CgroupMode iow. CgroupModeEmpty CgroupMode = "" w/o it's a string and not the type you wanted it to be
  3. rename CgroupMode to CgroupModeType to follow other types like this.

@rphillips I was told to let you know about it 😄

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks... +1

@soltysh
Copy link
Copy Markdown
Contributor

soltysh commented Feb 7, 2022

/label px-approved
/label qa-approved

@openshift-ci openshift-ci bot added the px-approved Signifies that Product Support has signed off on this PR label Feb 7, 2022
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Feb 7, 2022

@soltysh: The label(s) /label qa-approved cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, backport-risk-assessed, cherry-pick-approved

Details

In response to this:

/label px-approved
/label qa-approved

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.

@soltysh
Copy link
Copy Markdown
Contributor

soltysh commented Feb 7, 2022

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Feb 7, 2022
@harche harche force-pushed the node_object branch 2 times, most recently from 6e8112d to 13762ae Compare February 24, 2022 06:07
Signed-off-by: Harshal Patil <harpatil@redhat.com>
Signed-off-by: Ryan Phillips <rphillip@redhat.com>
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 2, 2022

@harche: all tests passed!

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.

Copy link
Copy Markdown
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 2, 2022
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 2, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: harche, rphillips, soltysh, swghosh

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 2, 2022
@soltysh
Copy link
Copy Markdown
Contributor

soltysh commented Mar 2, 2022

/label docs-approved

@openshift-ci openshift-ci bot added the docs-approved Signifies that Docs has signed off on this PR label Mar 2, 2022
@openshift-merge-robot openshift-merge-robot merged commit 2404307 into openshift:master Mar 2, 2022
@harche harche deleted the node_object branch March 3, 2022 05:45
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. docs-approved Signifies that Docs has signed off on this PR lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants