-
Notifications
You must be signed in to change notification settings - Fork 192
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
chore(ci): make libbpf as the default attacher #1077
chore(ci): make libbpf as the default attacher #1077
Conversation
vimalk78
commented
Nov 24, 2023
•
edited
Loading
edited
- tag existing 'latest' image as 'latest-bcc'
- tag existing 'latest-libbpf' as 'latest'
- make libbpf image as default released image
- use libbpf as attacher for PR image
- make unit_test run with libbpf attacher
- build kepler with libbpf attacher for rpm build
- rename integration_test to integration_test_bcc
- rename integration_test_libbpf to integration_test
cceecea
to
0eef904
Compare
Cc: @rootfs @SamYuan1990 |
6e77fa4
to
08227c7
Compare
@rootfs @marceloamaral can i pls get rights to request a PR review? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this file is renamed
old name: integration_test_libbpf.yml
new name: integration_test.yml
there are no other changes in file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this file is renamed
old name: integration_test.yml
new name: integration_test_bcc.yml
there are no other changes in file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be changed to Build and push kepler latest (bcc)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
4aaf4d1
to
e6db42a
Compare
|
||
on: | ||
workflow_call: | ||
|
||
env: | ||
OUTPUT_DIR: "_output/" | ||
FILE_NAME: "kepler_libbpf.tar.gz" | ||
FILE_NAME: "kepler.tar.gz" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
kepe
FILE_NAME: "kepler.tar.gz" | |
FILE_NAME: "kepler_bcc.tar.gz" |
@@ -24,30 +24,30 @@ jobs: | |||
- name: install libbpf |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- name: install libbpf | |
- name: install bcc |
@@ -130,17 +130,17 @@ jobs: | |||
context: . | |||
platforms: linux/amd64 | |||
push: true | |||
tags: quay.io/sustainable_computing_io/kepler:latest, quay.io/sustainable_computing_io/kepler:${{ github.event.inputs.release }} | |||
tags: quay.io/sustainable_computing_io/kepler:latest, quay.io/sustainable_computing_io/kepler:${{ github.event.inputs.release }}-bcc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we have the latest
tag here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lets take this question in some other PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason I ask is because I am assuming that the previous release tagged bcc
as latest and now we want to switch that to libbpf. Would that be the case if we add latest
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tags
field for both images has quay.io/sustainable_computing_io/kepler:latest
9fb5b58
to
b71c37a
Compare
e4d38f5
to
9b991e5
Compare
- tag existing 'latest' image as 'latest-bcc' - tag existing 'latest-libbpf' as 'latest' - make libbpf image as default released image - use libbpf as attacher for PR image - make unit_test run with libbpf attacher - updated unit_test workflow to install libbpf from source - build kepler with libbpf attacher for rpm build - rename integration_test to integration_test_bcc - rename integration_test_libbpf to integration_test Signed-off-by: Vimal Kumar <[email protected]>
Updated following files to not use normalized_cpu_arch.csv, and use cpus.yaml - updated build/Dockerfile - doc/dev/prepare_dev_env.sh Signed-off-by: Vimal Kumar <[email protected]>
9b991e5
to
e04259c
Compare
Per @SamYuan1990 comment, the bcc code will held in the source and be removed in the next release. |
so we will remove bcc code after 0.8 release? |
@vimalk78 we need a CI step to make genlibbpf @SamYuan1990 yes, let's remove all the bcc code in 0.8 once we are fully confident on libbpf. |
- name: Prepare environment | ||
run: | | ||
sudo apt-get install -y cpuid | ||
cd doc/ && sudo ./dev/prepare_dev_env.sh && cd - | ||
git config --global --add safe.directory /kepler | ||
- name: Run | ||
run: | | ||
make test-verbose | ||
sudo apt remove libbpf-dev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if libbpf-dev
is not enough of our libbpf driver, we should make a deb package at https://github.com/sustainable-computing-io/kepler-ci-artifacts and update our kepler-action.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sustainable-computing-io/kepler-action#87 created accordingly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rootfs / @vimalk78 / @sthaha could you please help double confirm if we need sustainable-computing-io/kepler-action#87 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
new issue related to this PR as #1086
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if
libbpf-dev
is not enough of our libbpf driver, we should make a deb package at
yes @SamYuan1990, opening a PR for the same. in this PR i wanted to test what works. will update kepler-action, and then we dont needs this setup in CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vimalk78 I am going to sleep, please take a look at #1086 briefly, the libbpf-dev ubuntu distribution has the static link file but it seems the version for ubuntu distribution is too old. or mismatch with the golang code. hence I am worry about if libbpf is ready for use? as if we build it from source each time.... dependence maintain as OpenSSF or SBOM sounds like disaster for us.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SamYuan1990 pls check this PR sustainable-computing-io/kepler-action#90
Cc: @rootfs
@@ -277,6 +277,7 @@ test: ginkgo-set tidy-vendor | |||
|
|||
test-verbose: ginkgo-set tidy-vendor | |||
@echo TAGS=$(GO_BUILD_TAGS) | |||
@echo GOENV=$(GOENV) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need echo this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the information echoed in this line is helpful in checking errors we get from go build
, if any.
some further comments been added related pr code but not release process. |
…-io#1077) * chore(ci): make libbpf image as the default image - tag existing 'latest' image as 'latest-bcc' - tag existing 'latest-libbpf' as 'latest' - make libbpf image as default released image - use libbpf as attacher for PR image - make unit_test run with libbpf attacher - updated unit_test workflow to install libbpf from source - build kepler with libbpf attacher for rpm build - rename integration_test to integration_test_bcc - rename integration_test_libbpf to integration_test Signed-off-by: Vimal Kumar <[email protected]> * fix(build): use correct cpus data file Updated following files to not use normalized_cpu_arch.csv, and use cpus.yaml - updated build/Dockerfile - doc/dev/prepare_dev_env.sh Signed-off-by: Vimal Kumar <[email protected]> --------- Signed-off-by: Vimal Kumar <[email protected]>