Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@klihub
Copy link
Contributor

@klihub klihub commented Jan 25, 2022

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR adds support for injecting CDI devices into containers.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

This PR depends on a pending CDI PR. There is a related go.mod rewrite rule among the commits here, to allow the tree to be compile and tested. Once that CDI PR is merged, the repo diverting rewrite will be removed from this PR.

Does this PR introduce a user-facing change?

Implement CDI device injection: extract the names of requested CDI devices and update
the OCI Spec according to the corresponding CDI device specifications. Please refer to
https://github.com/container-orchestrated-devices/container-device-interface for more
info about CDI.

@klihub klihub requested review from mrunalp and runcom as code owners January 25, 2022 23:39
@openshift-ci openshift-ci bot added kind/feature Categorizes issue or PR as related to a new feature. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. 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 Jan 25, 2022
@openshift-ci openshift-ci bot requested a review from haircommander January 25, 2022 23:40
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 25, 2022

Hi @klihub. Thanks for your PR.

I'm waiting for a cri-o 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.

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.

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jan 25, 2022
@codecov
Copy link

codecov bot commented Jan 25, 2022

Codecov Report

Merging #5571 (a7ec3cc) into main (f4083c4) will increase coverage by 0.01%.
The diff coverage is n/a.

❗ Current head a7ec3cc differs from pull request most recent head 1281651. Consider uploading reports for the commit 1281651 to get more accurate results

@@            Coverage Diff             @@
##             main    #5571      +/-   ##
==========================================
+ Coverage   43.18%   43.19%   +0.01%     
==========================================
  Files         123      123              
  Lines       12267    12265       -2     
==========================================
+ Hits         5297     5298       +1     
+ Misses       6462     6459       -3     
  Partials      508      508              

@klihub klihub force-pushed the devel/cdi-support branch from 90e82eb to 3821927 Compare January 26, 2022 23:33
@saschagrunert
Copy link
Member

/ok-to-test

@openshift-ci openshift-ci bot 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 Jan 27, 2022
Copy link
Member

@saschagrunert saschagrunert left a comment

Choose a reason for hiding this comment

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

Just a few nits, generally LGTM :)

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 27, 2022
@klihub klihub force-pushed the devel/cdi-support branch 2 times, most recently from 08c6789 to b73ff38 Compare January 27, 2022 15:47
Copy link
Contributor

@fidencio fidencio left a comment

Choose a reason for hiding this comment

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

LGTM, thanks @klihub!

@haircommander
Copy link
Member

a rebase will fix ci @klihub :)

@klihub klihub force-pushed the devel/cdi-support branch 7 times, most recently from 3e4fd2c to a09fae1 Compare February 1, 2022 00:38
@klihub
Copy link
Contributor Author

klihub commented Feb 24, 2022

/test integration_crun

@klihub
Copy link
Contributor Author

klihub commented Feb 24, 2022

/test integration_cgroupv2

@klihub
Copy link
Contributor Author

klihub commented Feb 24, 2022

/test integration_cgroupv2

1 similar comment
@klihub
Copy link
Contributor Author

klihub commented Feb 24, 2022

/test integration_cgroupv2

@klihub
Copy link
Contributor Author

klihub commented Feb 24, 2022

/test integration_fedora

@klihub
Copy link
Contributor Author

klihub commented Feb 24, 2022

/test integration_cgroupv2

2 similar comments
@klihub
Copy link
Contributor Author

klihub commented Feb 24, 2022

/test integration_cgroupv2

@klihub
Copy link
Contributor Author

klihub commented Feb 24, 2022

/test integration_cgroupv2

Signed-off-by: Krisztian Litkey <[email protected]>
Extract the names of requested CDI devices and update the OCI
Spec according to the corresponding CDI device specifications.

CDI devices are requested using container annotations in the
cdi.k8s.io namespace. Once CRI gains dedicated fields for CDI
injection the snippet for extracting CDI names will need an
update.

Signed-off-by: Krisztian Litkey <[email protected]>
@klihub
Copy link
Contributor Author

klihub commented Feb 25, 2022

/test integration_cgroupv2

@klihub
Copy link
Contributor Author

klihub commented Feb 25, 2022

/test integration_cgroupv2

1 similar comment
@klihub
Copy link
Contributor Author

klihub commented Feb 25, 2022

/test integration_cgroupv2

@klihub
Copy link
Contributor Author

klihub commented Feb 25, 2022

/retest-required

1 similar comment
@klihub
Copy link
Contributor Author

klihub commented Feb 25, 2022

/retest-required

@klihub
Copy link
Contributor Author

klihub commented Feb 25, 2022

/test integration_cgroupv2

@haircommander
Copy link
Member

/approve

thanks @klihub!

@cri-o/cri-o-maintainers PTAL

@klihub klihub requested a review from saschagrunert March 4, 2022 15:46
Copy link
Member

@saschagrunert saschagrunert left a comment

Choose a reason for hiding this comment

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

/lgtm

Great work @klihub!

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

openshift-ci bot commented Mar 7, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: haircommander, klihub, saschagrunert

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:
  • OWNERS [haircommander,saschagrunert]

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

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/feature Categorizes issue or PR as related to a new feature. lgtm 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. release-note Denotes a PR that will be considered when it comes time to generate release notes.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants