-
Notifications
You must be signed in to change notification settings - Fork 11
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
UPSTREAM: <carry>: Add ilab kfp pipeline to the DSPO repo #120
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
Commit Checker results:
|
f92a1dc
to
a699d91
Compare
Commit Checker results:
|
a699d91
to
e068d34
Compare
Commit Checker results:
|
A set of new images have been built to help with testing out this PR: |
An OCP cluster where you are logged in as cluster admin is required. The Data Science Pipelines team recommends testing this using the Data Science Pipelines Operator. Check here for more information on using the DSPO. To use and deploy a DSP stack with these images (assuming the DSPO is deployed), first save the following YAML to a file named apiVersion: datasciencepipelinesapplications.opendatahub.io/v1alpha1
kind: DataSciencePipelinesApplication
metadata:
name: pr-120
spec:
dspVersion: v2
apiServer:
image: "quay.io/opendatahub/ds-pipelines-api-server:pr-120"
argoDriverImage: "quay.io/opendatahub/ds-pipelines-driver:pr-120"
argoLauncherImage: "quay.io/opendatahub/ds-pipelines-launcher:pr-120"
persistenceAgent:
image: "quay.io/opendatahub/ds-pipelines-persistenceagent:pr-120"
scheduledWorkflow:
image: "quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-120"
mlmd:
deploy: true # Optional component
grpc:
image: "quay.io/opendatahub/mlmd-grpc-server:latest"
envoy:
image: "registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2"
mlpipelineUI:
deploy: true # Optional component
image: "quay.io/opendatahub/ds-pipelines-frontend:pr-120"
objectStorage:
minio:
deploy: true
image: 'quay.io/opendatahub/minio:RELEASE.2019-08-14T20-37-41Z-license-compliance' Then run the following: cd $(mktemp -d)
git clone [email protected]:opendatahub-io/data-science-pipelines.git
cd data-science-pipelines/
git fetch origin pull/120/head
git checkout -b pullrequest 2e8d4cf6d5e4c7089a261ab86560f1a313550325
oc apply -f dspa.pr-120.yaml More instructions here on how to deploy and test a Data Science Pipelines Application. |
Change to PR detected. A new PR build was completed. |
1 similar comment
Change to PR detected. A new PR build was completed. |
backend/Dockerfile
Outdated
@@ -44,6 +44,7 @@ WORKDIR /bin | |||
|
|||
COPY --from=builder /opt/app-root/src/backend/src/apiserver/config/ /config | |||
COPY --from=builder /bin/apiserver /bin/apiserver | |||
COPY --from=builder /opt/app-root/src/backend/src/apiserver/ilab_pipeline/pipeline.yaml /pipelines/ |
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 we're going with this method of including the pipeline we should also include the iris pipeline similarly. This may be out of scope for the ticket, but let's open a story to do so before we forget
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.
following https://github.com/opendatahub-io/data-science-pipelines/pull/120/files#r1884437176, we could just COPY the entire directory rather than pinning individual files, so something like:
COPY --from=builder /opt/app-root/src/backend/src/apiserver/sample_pipelines /pipelines
which would be a bit easier on upkeep as we can just add new pipelines and it would automatically get picked up, rather than explicitly adding new layers every time
@@ -0,0 +1,2326 @@ | |||
# PIPELINE DEFINITION |
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 put this file in backend/src/apiserver/sample_pipelines
, or something similar, so we can expand on this later.
Also, we should name this file something a little more clear than pipeline.yaml
. Perhaps instructlab.yaml
?
Commit Checker results:
|
a30d8e0
to
8f895ca
Compare
Commit Checker results:
|
Commit Checker results:
|
Signed-off-by: VaniHaripriya <[email protected]>
cfd29b3
to
90b978f
Compare
Change to PR detected. A new PR build was completed. |
Commit Checker results:
|
Change to PR detected. A new PR build was completed. |
2 similar comments
Change to PR detected. A new PR build was completed. |
Change to PR detected. A new PR build was completed. |
Description of your changes:
Resolves #RHOAIENG-16507
Checklist: