feat(examples/pachyderm-simple): Update and improve Pachyderm example

[philwinder]

This PR updates and improves the current pachyderm integration demo. This demo highlights the use of Pachyderm's S3 gateway and how seldon-core deployments can read directly from a version-controlled model artefact.

More sophisticated demos will come next.

What this PR does / why we need it:
Update Pachyderm demo.

Special notes for your reviewer:
This demo requires a public docker image to be built and pushed to seldonio's docker hub (following on from how the previous demo worked).

Someone with access to seldonio's docker hub account needs to:

# login to docker hub then...
cd examples/pachyderm-simple/iris-train-python-svm/
make build
make push

This will push a new version of the already existing training image to here: https://hub.docker.com/r/seldonio/pachyderm-iris-trainer

Does this PR introduce a user-facing change?:

NONE

[seldondev]

Hi @philwinder. Thanks for your PR.

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

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 jenkins-x/lighthouse repository.

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[philwinder]

/assign @SachinVarghese

[RafalSkolasinski]

/retest

[seldondev]

Wed Dec 16 12:15:57 UTC 2020
The logs for [lint] [2] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2764/2.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2764 --build=2

[seldondev]

Wed Dec 16 12:15:58 UTC 2020
The logs for [pr-build] [1] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2764/1.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2764 --build=1

[RafalSkolasinski]

Awesome work @philwinder!

Few comments, it would be good to:

• use seldon namespace for deployments to be consistent with most of the examples we have
• add one more kubectl rollout status before sending requests to updated deployment at the end of the notebook

I also noticed that the docs don't build, you may need to update path in https://github.com/SeldonIO/seldon-core/blob/master/doc/source/examples/pachyderm.nblink
to be

"path": "../../../examples/pachyderm-simple/index.ipynb"

It may be required to copy images to doc/source/examples wherever required.
You may build docs locally to test it by using

make livehtml

in the doc directory

[philwinder]

Hi @RafalSkolasinski.
I have fixed the docs build, added the extra rollout status check, and moved the deployments to the seldon workspace.

Thanks, Phil

[RafalSkolasinski]

/ok-to-test

[seldondev]

Tue Jan 5 14:38:17 UTC 2021
The logs for [lint] [4] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2764/4.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2764 --build=4

[seldondev]

Tue Jan 5 14:38:29 UTC 2021
The logs for [pr-build] [3] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2764/3.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2764 --build=3

[RafalSkolasinski]

/approve

[seldondev]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RafalSkolasinski

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:

• OWNERS [RafalSkolasinski]

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