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

WIP: NOMERGE: DNM: consume u/s PR 126750 #2088

Open
wants to merge 18 commits into
base: release-4.16
Choose a base branch
from

Conversation

ffromani
Copy link

WIP DNM

@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Sep 19, 2024
@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 Sep 19, 2024
@openshift-ci-robot
Copy link

@ffromani: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@ffromani ffromani changed the title WIP: DNM: consume u/s PR 126750 WIP: NOMERGE: DNM: consume u/s PR 126750 Sep 19, 2024
@ffromani
Copy link
Author

/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 Sep 19, 2024
adapt to the older codebase

Signed-off-by: Francesco Romani <fromani@redhat.com>
@openshift-ci-robot
Copy link

@ffromani: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@ffromani
Copy link
Author

/test k8s-e2e-aws-ovn-serial

@openshift-ci-robot
Copy link

@ffromani: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

In order to improve the observability of the resource management
in kubelet, cpu allocation and NUMA alignment, we add more metrics
to report if resource alignment is in effect.

The more precise reporting would probably be using pod status,
but this would require more invasive and riskier changes,
and possibly extra interactions to the APIServer.

We start adding metrics to report if containers got their
compute resources aligned.
If metrics are growing, the assingment is working as expected;
If metrics stay consistent, perhaps at zero, no resource
alignment is done.

Signed-off-by: Francesco Romani <fromani@redhat.com>
wire in the l3 group alignment metrics

Signed-off-by: Francesco Romani <fromani@redhat.com>
make sure to log the patched version

Signed-off-by: Francesco Romani <fromani@redhat.com>
@openshift-ci-robot
Copy link

@ffromani: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

Copy link

openshift-ci bot commented Sep 26, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ffromani
Once this PR has been reviewed and has the lgtm label, please assign tkashem for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

add more verbose logs by default to make the LLC algorithm
debuggable.

Signed-off-by: Francesco Romani <fromani@redhat.com>
@openshift-ci-robot
Copy link

@ffromani: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@ffromani
Copy link
Author

/test

Copy link

openshift-ci bot commented Sep 27, 2024

@ffromani: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

  • /test artifacts
  • /test configmap-scale
  • /test e2e-aws-crun-wasm
  • /test e2e-aws-jenkins
  • /test e2e-aws-ovn-cgroupsv2
  • /test e2e-aws-ovn-crun
  • /test e2e-aws-ovn-downgrade
  • /test e2e-aws-ovn-fips
  • /test e2e-aws-ovn-serial
  • /test e2e-aws-ovn-upgrade
  • /test e2e-azure-ovn-upgrade
  • /test e2e-gcp
  • /test e2e-gcp-ovn-upgrade
  • /test images
  • /test integration
  • /test k8s-e2e-conformance-aws
  • /test k8s-e2e-gcp-ovn
  • /test k8s-e2e-gcp-serial
  • /test unit
  • /test verify
  • /test verify-commits

The following commands are available to trigger optional jobs:

  • /test e2e-agnostic-ovn-cmd
  • /test e2e-aws
  • /test e2e-aws-csi
  • /test e2e-aws-disruptive
  • /test e2e-aws-multitenant
  • /test e2e-aws-ovn
  • /test e2e-aws-single-node
  • /test e2e-azure
  • /test e2e-metal-ipi
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-ipv6
  • /test e2e-openstack
  • /test e2e-openstack-csi-cinder
  • /test e2e-openstack-csi-manila
  • /test e2e-vsphere
  • /test k8s-e2e-aws
  • /test k8s-e2e-aws-ovn-serial
  • /test k8s-e2e-gcp-five-control-plane-replicas
  • /test okd-scos-images

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-kubernetes-release-4.16-e2e-agnostic-ovn-cmd
  • pull-ci-openshift-kubernetes-release-4.16-e2e-aws-crun-wasm
  • pull-ci-openshift-kubernetes-release-4.16-e2e-aws-csi
  • pull-ci-openshift-kubernetes-release-4.16-e2e-aws-ovn-cgroupsv2
  • pull-ci-openshift-kubernetes-release-4.16-e2e-aws-ovn-crun
  • pull-ci-openshift-kubernetes-release-4.16-e2e-aws-ovn-fips
  • pull-ci-openshift-kubernetes-release-4.16-e2e-aws-ovn-serial
  • pull-ci-openshift-kubernetes-release-4.16-e2e-gcp
  • pull-ci-openshift-kubernetes-release-4.16-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-kubernetes-release-4.16-images
  • pull-ci-openshift-kubernetes-release-4.16-integration
  • pull-ci-openshift-kubernetes-release-4.16-k8s-e2e-aws-ovn-serial
  • pull-ci-openshift-kubernetes-release-4.16-k8s-e2e-conformance-aws
  • pull-ci-openshift-kubernetes-release-4.16-k8s-e2e-gcp-ovn
  • pull-ci-openshift-kubernetes-release-4.16-k8s-e2e-gcp-serial
  • pull-ci-openshift-kubernetes-release-4.16-unit
  • pull-ci-openshift-kubernetes-release-4.16-verify
  • pull-ci-openshift-kubernetes-release-4.16-verify-commits

In response to this:

/test

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-sigs/prow repository.

@ffromani
Copy link
Author

/test k8s-e2e-aws
/test k8s-e2e-aws-ovn-serial

fix logging to reflect what takeFullUnCoreCache
actually did; with the buggy code it was still inferrable
from the logs, but it has to be explicit.

Signed-off-by: Francesco Romani <fromani@redhat.com>
@openshift-ci-robot
Copy link

@ffromani: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

Signed-off-by: Francesco Romani <fromani@redhat.com>
@openshift-ci-robot
Copy link

@ffromani: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@ffromani
Copy link
Author

/test k8s-e2e-aws
/test k8s-e2e-aws-ovn-serial

A log in `topology` subpkg was too spammy. Bump its verbosiness.

Signed-off-by: Francesco Romani <fromani@redhat.com>
@openshift-ci-robot
Copy link

@ffromani: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot
Copy link

@ffromani: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

no uncore cache can be treated as all CPUs belonging
to the same group, so alignment is implicit and always guaranteed.

Signed-off-by: Francesco Romani <fromani@redhat.com>
@openshift-ci-robot
Copy link

@ffromani: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

further improve throubleshooting to check if the LLC alignment
code is engaging.

Signed-off-by: Francesco Romani <fromani@redhat.com>
@openshift-ci-robot
Copy link

@ffromani: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

Copy link

openshift-ci bot commented Oct 16, 2024

@ffromani: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants