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

resync 20240507 #196

Merged
merged 49 commits into from
May 14, 2024
Merged

resync 20240507 #196

merged 49 commits into from
May 14, 2024

Conversation

ffromani
Copy link
Member

@ffromani ffromani commented May 7, 2024

resync with the tip of the upstream master branch

we can now drop our KNI-specific dep bump, they are done by u/s

ichbinblau and others added 30 commits January 8, 2024 10:08
Co-authored-by: Cathy Zhang <cathy.h.zhang@intel.com>
Signed-off-by: Theresa <theresa.shan@intel.com>
Co-authored-by: Cathy Zhang <cathy.h.zhang@intel.com>
Signed-off-by: Theresa <theresa.shan@intel.com>
Fix wrong highlight in diff code block
Remove incorrect Pod name from installation doc
remove manual edit strings from crd manifests
Fix diff code block highlight color, change the format of yaml diff code block from raw diff to git diff.
Manually update the API files for the implementation of SySched,
a system call-aware scheduler(KEP kubernetes-sigs#399). SySched is a new scoring
plugin that ranks feasible nodes based on the relative risks of
pods' system call usage.
Sysched: add the implementation of SySched
…ng_op_helm

Add scheduling op to helm chart
…rf-fix

Avoid unnecessary requeue operations in coscheduling
Huang-Wei and others added 16 commits April 18, 2024 14:19
Bump NRT API package to v0.1.2; there is no API change,
but we have now a better replacement for the internal
`getID` helper, which we can now remove.

Signed-off-by: Francesco Romani <fromani@redhat.com>
Move to the logr.Logger interface everywhere, instead of the
global `klog` instance. This enable named logger, presetting values
for simple and automatic consistency, enables pluggable loggers
and comes for free since we already depend on the logr package
and klog has a native logr integration.

In addition, add minimal support to make it easy to
replace the logr reference, to help integrators of
this code. The default is still (and will still be)
klog for backward compatibility and ecosystem integration.

Signed-off-by: Francesco Romani <fromani@redhat.com>
[noderesourcetopology] move logging to the logr interface
pass existing context without using TODO()
After more review and conversations, we have a better
understanding of how integration with contextual logging
should loom like.
First and foremost, injecting loggers would conflict with
the very goals of contextual logging.
So, let's drop this code we added in kubernetes-sigs#710.

The contextual logger doesn't do key/values deduplication.
This is let to (some) backends. To avoid log clutter,
trim down the extra key/value pairs and add only those we
really need to ensure a good troubleshooting experience.

Still let's make sure to add critical key/value
pairs in the relevant entries, at cost of a possible
duplication.

When reporting the current assumed resources, the current
representation is neither concise nor very human friendly.
Additionally, multi-line log entries are harder to process
and should be avoided.
So let's move to a more concise representation, which turns
out not obviously less human friendly and is no longer multiline.

Review verbosiness of log entries.
Move down to verbose=2 logs which are really key to understand
the behavior. We should set a hard limit to log entries to minimize
the log spam while keeping at least some observability without
requiring v=4 or greater.

The level v=4 is usually/often the highest-not-spammy log.
When debug logs are needed we often set v=4, and higher verbosity
levels are often used only in desperate times.
Thus, promote to v=4 the debug logs we should really see.

Everywhere else in the kubernetes ecosystem, and most
notably in the scheduler, the pod namespace/name pair is called
"pod", while we called it "logID".
We do it to use the same name for all the flows, being the
cache resync (which is driven by time, not by an object) the
odd one.

It seems better to be externally consistent (with the ecosystem)
rather than internally consistent (all the flows in the same plugin),
so we rename "logID" to "pod" in the log entries.

Signed-off-by: Francesco Romani <fromani@redhat.com>
…logging

[noderesourcetopology] complete the contextual logging integration
resync to the tip of the main u/s branch

Signed-off-by: Francesco Romani <fromani@redhat.com>
@openshift-ci openshift-ci bot requested review from MarSik and swatisehgal May 7, 2024 16:06
Copy link

openshift-ci bot commented May 7, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ffromani

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 7, 2024
Update the plugins to conform to the newer APIs
The v1beta3 was removed

Signed-off-by: Francesco Romani <fromani@redhat.com>
@ffromani
Copy link
Member Author

ffromani commented May 8, 2024

depends on openshift-kni/numaresources-operator#933

@ffromani
Copy link
Member Author

ffromani commented May 8, 2024

/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 May 8, 2024
@ffromani
Copy link
Member Author

/cc @shajmakh

@openshift-ci openshift-ci bot requested a review from shajmakh May 10, 2024 13:29
@ffromani
Copy link
Member Author

/hold cancel

dependency merged

@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 May 13, 2024
@ffromani ffromani merged commit e94856f into master May 14, 2024
6 of 7 checks passed
@ffromani ffromani deleted the resync-20240507 branch May 14, 2024 10:09
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants