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

Remove requirments-elyra.txt from the code base #761

Merged
merged 5 commits into from
Nov 27, 2024

Conversation

dibryant
Copy link
Contributor

@dibryant dibryant commented Nov 4, 2024

Fixes for https://issues.redhat.com/browse/RHOAIENG-11068

Description

Remove requirments-elyra.txt from the code base

How Has This Been Tested?

@jiridanek:

  • ran make tests for images
  • pip install -r from the modified requirement files

Merge criteria:

  • The commits are squashed in a cohesive manner and have meaningful messages.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

@openshift-ci openshift-ci bot requested review from atheo89 and paulovmr November 4, 2024 14:18
@dibryant dibryant changed the title WIP Remove requirments-elyra.txt from the code base [WIP] Remove requirments-elyra.txt from the code base Nov 4, 2024
@dibryant dibryant changed the title [WIP] Remove requirments-elyra.txt from the code base Remove requirments-elyra.txt from the code base Nov 5, 2024
Copy link
Member

Choose a reason for hiding this comment

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

I thought we decided to keep these files present, just delete the content. Has anything changed?

Copy link
Member

Choose a reason for hiding this comment

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

Empty out "*/utils/requirements-elyra.txt", with comments to keep it for sanity
remove all "/kustomize/base/requirements-elyra.txt"

hmm

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ahhh I see will revert it back! Sorry about that

Copy link
Member

Choose a reason for hiding this comment

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

Empty out "*/utils/requirements-elyra.txt", with comments to keep it for sanity
remove all "/kustomize/base/requirements-elyra.txt"

This is old summary. Last time we discussed on the scrum to keep the /utils/requirements-elyra.txt and put its content in comments, because otherwise the bootstraper.py will fail.

@dibryant dibryant force-pushed the rhoaieng-11068 branch 2 times, most recently from 8584bc1 to 6f26350 Compare November 13, 2024 14:21
Copy link
Member

@harshad16 harshad16 left a comment

Choose a reason for hiding this comment

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

Great initiative, shared some comments

Makefile Outdated
$(KUBECTL_BIN) exec runtime-pod -- /bin/sh -c "python3 -m pip install -r /opt/app-root/elyra/requirements-elyra.txt && \
curl https://raw.githubusercontent.com/nteract/papermill/main/papermill/tests/notebooks/simple_execute.ipynb --output simple_execute.ipynb && \
python3 -m papermill simple_execute.ipynb output.ipynb > /dev/null" ; \
$(KUBECTL_BIN) exec runtime-pod -- /bin/sh -c "python3 -m pip install pipenv --three sync && \
Copy link
Member

Choose a reason for hiding this comment

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

$(KUBECTL_BIN) exec runtime-pod -- /bin/sh -c "curl https://raw.githubusercontent.com/opendatahub-io/elyra/refs/heads/main/etc/generic/requirements-elyra.txt --output req.txt && \ python3 -m pip install -r req.txt && \
				curl https://raw.githubusercontent.com/nteract/papermill/main/papermill/tests/notebooks/simple_execute.ipynb --output simple_execute.ipynb && \
				python3 -m papermill simple_execute.ipynb output.ipynb > /dev/null" ; \

Try this.
As, the reason for using the requirements.txt is so that , we can make sure that packages are installable ,
perhaps, we can extend this in further tasks, to do some extra checks.

@dibryant dibryant force-pushed the rhoaieng-11068 branch 2 times, most recently from 5382208 to e8d535f Compare November 19, 2024 13:54
Copy link
Member

@harshad16 harshad16 left a comment

Choose a reason for hiding this comment

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

@dibryant , can you please add fail=0 ; \ below line number 522
as i believe we missed it and line 546 complain 😅

@dibryant dibryant force-pushed the rhoaieng-11068 branch 2 times, most recently from 7e917dd to 2144737 Compare November 22, 2024 23:25
@jiridanek jiridanek added tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. trivy-scan This label that allows trivy to create a security report on the pull requests labels Nov 24, 2024
@dibryant dibryant force-pushed the rhoaieng-11068 branch 2 times, most recently from 89fda11 to b69c78a Compare November 26, 2024 16:37
./runtimes/rocm-tensorflow/ubi9-python-3.11/kustomize/base/kustomization.yaml
  Error: 11:1 [empty-lines] too many blank lines (1 > 0)

./runtimes/tensorflow/ubi9-python-3.11/kustomize/base/kustomization.yaml
  Error: 11:1 [empty-lines] too many blank lines (1 > 0)

and wrongly intended line in Makefile, that's not linted automatically
without it, pip would error out on this invalid requirements file
@jiridanek
Copy link
Member

Checked this with github actions in https://github.com/jiridanek/notebooks/actions/runs/12045657286/job/33585360434, the results look good, only failures there are known issues in cuda/rocm images.

This PR is not removing elyra-requirements.txt from python3.9 images and from the intel runtimes, but that's ok. We want to delete the python3.9 images from main anyways, and we don't touch intel because it's broken (https://issues.redhat.com/browse/RHOAIENG-8388)

/lgtm
/approve
Thank you +💯

@openshift-ci openshift-ci bot added the lgtm label Nov 27, 2024
Copy link
Contributor

openshift-ci bot commented Nov 27, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jiridanek

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

@jiridanek
Copy link
Member

jiridanek commented Nov 27, 2024

/label tide/merge-method-squash

to squash all commits on the PR together

@jiridanek
Copy link
Member

/override "build (rocm-jupyter-pytorch-ubi9-python-3.11) / build"
/override "build (rocm-jupyter-pytorch-ubi9-python-3.9) / build"

This is due to known issue

Copy link
Contributor

openshift-ci bot commented Nov 27, 2024

@jiridanek: Overrode contexts on behalf of jiridanek: build (rocm-jupyter-pytorch-ubi9-python-3.11) / build, build (rocm-jupyter-pytorch-ubi9-python-3.9) / build

In response to this:

/override "build (rocm-jupyter-pytorch-ubi9-python-3.11) / build"
/override "build (rocm-jupyter-pytorch-ubi9-python-3.9) / build"

This is due to known issue

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.

@jiridanek
Copy link
Member

ROCm images are failing to build on ephemeral-storage issues, e.g.

Error on reading termination message from logs: failed to ...-c87b227aef51/docker-build/0.log: no such file or directory, the build jupyter-pytorch-ubi9-python-3.9-amd64 failed after 10m39s with reason BuildPodEvicted: The node was low on resource: ephemeral-storage. Threshold quantity: 32121498671, available: 27985436Ki. Container docker-build was using 1112Ki, request is 0, has larger consumption of ephemeral-storage.

/override ci/prow/rocm-runtimes-ubi9-e2e-tests
/override ci/prow/runtimes-ubi9-e2e-tests

Copy link
Contributor

openshift-ci bot commented Nov 27, 2024

@jiridanek: Overrode contexts on behalf of jiridanek: ci/prow/rocm-runtimes-ubi9-e2e-tests, ci/prow/runtimes-ubi9-e2e-tests

In response to this:

ROCm images are failing to build on ephemeral-storage issues, e.g.

Error on reading termination message from logs: failed to ...-c87b227aef51/docker-build/0.log: no such file or directory, the build jupyter-pytorch-ubi9-python-3.9-amd64 failed after 10m39s with reason BuildPodEvicted: The node was low on resource: ephemeral-storage. Threshold quantity: 32121498671, available: 27985436Ki. Container docker-build was using 1112Ki, request is 0, has larger consumption of ephemeral-storage.

/override ci/prow/rocm-runtimes-ubi9-e2e-tests
/override ci/prow/runtimes-ubi9-e2e-tests

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.

@jiridanek
Copy link
Member

/retest

@openshift-merge-bot openshift-merge-bot bot merged commit eff0195 into opendatahub-io:main Nov 27, 2024
51 of 53 checks passed
@jiridanek
Copy link
Member

/test ci/prow/runtimes-ubi9-e2e-tests

jiridanek added a commit to jiridanek/notebooks that referenced this pull request Nov 28, 2024
openshift-merge-bot bot pushed a commit that referenced this pull request Nov 28, 2024
…ebooks Github Actions (#775)

* RHOAIENG-16076: tests(gha): run Makefile tests in GitHub Actions

* fixup, looks like I lost the second changed line from #761 (comment) when merging the work

* fixup, linter wants space in the comments; IntelliJ is ok with it, so let's do that

* fixup, add reference to OpenShift CI for the source of the make invocations

* fixup, the ifNotPresent pull policy (for PR checks without image registry) and the symbolic links apparently needed to deploy rocm stuff
@shalberd
Copy link
Contributor

shalberd commented Dec 4, 2024

@atheo89 @jiridanek

Good idea, I've been putting in the required libraries from requirements-elyra.txt upstream into the main requirements file / Pipfile when building Jupyterlab images and runtime images for a long time now.

With that and the commented-out install at runtime in bootstrapper.py upstream notice, the issue is fixed and Elyra has all it needs even at runtime in Airflow and KFP.

I also introduced a new env var that makes output of file run logs optional to S3.
https://github.com/elyra-ai/elyra/blob/main/elyra/kfp/bootstrapper.py#L52
See documentation on that at readthedocs for elyra main / latest:
https://elyra.readthedocs.io/en/latest/user_guide/env-variables-file-based-nodes.html#

jiridanek added a commit to jiridanek/notebooks that referenced this pull request Dec 18, 2024
…ebooks Github Actions (opendatahub-io#775)

* RHOAIENG-16076: tests(gha): run Makefile tests in GitHub Actions

* fixup, looks like I lost the second changed line from opendatahub-io#761 (comment) when merging the work

* fixup, linter wants space in the comments; IntelliJ is ok with it, so let's do that

* fixup, add reference to OpenShift CI for the source of the make invocations

* fixup, the ifNotPresent pull policy (for PR checks without image registry) and the symbolic links apparently needed to deploy rocm stuff

(cherry picked from commit b3d8af0)
jiridanek added a commit to jiridanek/notebooks that referenced this pull request Dec 19, 2024
…books Github Actions (opendatahub-io#775)

* RHOAIENG-16076: tests(gha): run Makefile tests in GitHub Actions

* fixup, looks like I lost the second changed line from opendatahub-io#761 (comment) when merging the work

* fixup, linter wants space in the comments; IntelliJ is ok with it, so let's do that

* fixup, add reference to OpenShift CI for the source of the make invocations

* fixup, the ifNotPresent pull policy (for PR checks without image registry) and the symbolic links apparently needed to deploy rocm stuff

(cherry picked from commit b3d8af0)
jiridanek added a commit to jiridanek/notebooks that referenced this pull request Jan 8, 2025
…ebooks Github Actions (opendatahub-io#775)

* RHOAIENG-16076: tests(gha): run Makefile tests in GitHub Actions

* fixup, looks like I lost the second changed line from opendatahub-io#761 (comment) when merging the work

* fixup, linter wants space in the comments; IntelliJ is ok with it, so let's do that

* fixup, add reference to OpenShift CI for the source of the make invocations

* fixup, the ifNotPresent pull policy (for PR checks without image registry) and the symbolic links apparently needed to deploy rocm stuff
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. trivy-scan This label that allows trivy to create a security report on the pull requests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants