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

Batch Processor Component #1915

Merged

Conversation

axsaucedo
Copy link
Contributor

@axsaucedo axsaucedo commented Jun 5, 2020

This PR contains the updated implementation of #1714 with the ability to be used in workflow managers. In contrast with previous PR, this one does not implement the data download step within the batch processor and expects the data download steps to be carried out by a separate container.

PR shows example with Argo Workflows and Kubeflow Pipelines.

@seldondev
Copy link
Collaborator

Mon Jun 8 11:17:42 UTC 2020
The logs for [lint] [35] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1915/35.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1915 --build=35

@seldondev
Copy link
Collaborator

Mon Jun 8 11:19:06 UTC 2020
The logs for [pr-build] [34] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1915/34.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1915 --build=34

@ukclivecox
Copy link
Contributor

The kubeflow pipelines notes is still badly formatted.

@axsaucedo
Copy link
Contributor Author

@cliveseldon I just had a look, the notebook has been updated to only have 2nd level headers, did you have a look at the latest file? Maybe the notebook where the comments are is cached to the previous changes

@seldondev
Copy link
Collaborator

Mon Jun 8 15:17:36 UTC 2020
The logs for [pr-build] [36] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1915/36.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1915 --build=36

@seldondev
Copy link
Collaborator

Mon Jun 8 15:19:08 UTC 2020
The logs for [lint] [37] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1915/37.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1915 --build=37

@axsaucedo
Copy link
Contributor Author

@cliveseldon @adriangonz @RafalSkolasinski seems all the comments have been addressed, is there any further changes required? Happy to jump on it today if there's anything outstanding

@RafalSkolasinski
Copy link
Contributor

Would be good to confirm that argo example can run in kind and if not make a note that Minikube is recommended for this one.

@axsaucedo
Copy link
Contributor Author

axsaucedo commented Jun 9, 2020

@RafalSkolasinski I think you had mentioned it had fixed the RBAC errors with that command provided above? It seems it's just a standard RBAC issue, not a KIND specific issue. Would you be able to have a look?

@RafalSkolasinski
Copy link
Contributor

RBAC errors went away but still had some troubles running it - will give it another shot to verify if there is a kind related problem

@seldondev
Copy link
Collaborator

Tue Jun 9 12:50:37 UTC 2020
The logs for [lint] [39] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1915/39.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1915 --build=39

@axsaucedo
Copy link
Contributor Author

Ok I have been able to run it in KIND, and it seems that the main issue is that Argo by default tries to mount "/var/run/docker.sock" for all workflows, which I don't really understand why as it seems quite bad practice. Due to this I added a note outlining that the example won't work on KIND as that issue is one that is specific to Argo on KIND.

@seldondev
Copy link
Collaborator

Tue Jun 9 12:52:26 UTC 2020
The logs for [pr-build] [38] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1915/38.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1915 --build=38

Use the notebook to [set-up Seldon Core with Ambassador or Istio Ingress](https://docs.seldon.io/projects/seldon-core/en/latest/examples/seldon_core_setup.html).

Note: This example won't work in KIND (Kubernetes in Docker) due to a known requirement from Argo which mounts the docker socket: https://github.com/argoproj/argo/issues/826

Copy link
Contributor

Choose a reason for hiding this comment

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

I managed to get this running with fix in argoproj/argo-workflows#2376 (comment)
Can you add thos instructions for Kind.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nice, thanks - ok I've added the comment

@ukclivecox
Copy link
Contributor

@axsaucedo I added comments on getting runnimg in Kind and a small fix for log output. Apart from that now got notebook to run e2e.

@axsaucedo
Copy link
Contributor Author

@cliveseldon awesome, ok I've added the changes suggested, should be good to go 🚀

@seldondev
Copy link
Collaborator

Tue Jun 9 17:21:45 UTC 2020
The logs for [lint] [41] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1915/41.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1915 --build=41

@seldondev
Copy link
Collaborator

Tue Jun 9 17:21:50 UTC 2020
The logs for [pr-build] [40] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-1915/40.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-1915 --build=40

@RafalSkolasinski
Copy link
Contributor

Nice one on the argo example!

I only think that clusterrole required is --clusterrole=cluster-admin not --clusterrole=admin - but could be that I was doing something wrong.

Also the SeldonCore notebook setup leaves environment with set namespace being seldon and it seems this example assumes it to be default.

Besides that it works pretty well!

@axsaucedo
Copy link
Contributor Author

/approve

@seldondev
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: axsaucedo

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

@axsaucedo axsaucedo merged commit b3ca768 into SeldonIO:master Jun 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants