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

make ambassador a dependency #480

Merged
merged 11 commits into from
Apr 4, 2019
Merged

Conversation

ryandawsonuk
Copy link
Contributor

Replaces #445

The core of this is that change.

As discussed in that thread, there are also changes to improve the reliability of the E2E tests.

The chart doesn't currently allow us to default ambassador to a single namespace and override so have had to change a lot of notebooks. The last commit does this. Will reverse that if the PR to the stable/ambassador chart is merged. We could create a ticket dedicated for keeping an eye on that and reversing these changes.

@@ -174,3 +174,7 @@ doc/source/_static/cluster-manager
python/build/
python/dist/
testing/scripts/proto
testing/scripts/tensorflow
Copy link
Contributor Author

@ryandawsonuk ryandawsonuk Apr 1, 2019

Choose a reason for hiding this comment

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

Noticed these were generated so put in gitignore and also the clean script in the testing makefile

@@ -273,7 +273,8 @@
"source": [
"!helm install ../../../helm-charts/seldon-core --name seldon-core \\\n",
" --namespace seldon \\\n",
" --set ambassador.enabled=true"
" --set ambassador.enabled=true \\\n",
" --set ambassador.env.AMBASSADOR_SINGLE_NAMESPACE=true"
Copy link
Contributor Author

@ryandawsonuk ryandawsonuk Apr 1, 2019

Choose a reason for hiding this comment

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

I think this is not strictly necessary as otherwise it will be cluster-wide and that would work too. But previously it was namespace-only. In addition to running the tests I also stepped through this notebook to make sure it was ok to make this change. I was able to make all the requests.

Copy link
Contributor Author

@ryandawsonuk ryandawsonuk Apr 1, 2019

Choose a reason for hiding this comment

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

For a little while I wasn't able to see anything in the grafana dashboard but that turned out to be unrelated as I was seeing it with master too and it was fixed by recreating minikube.

@@ -6,10 +6,17 @@ build_protos:
python -m grpc.tools.protoc -I. --python_out=. --grpc_python_out=. ./proto/prediction.proto
cd ../../notebooks && make build_protos

#requires mvn, helm, ks, python, s2i and an accessible k8s cluster (if minikube increase mem and cpu)
#tests will create namespaces, deploy seldon core and create examples
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Pointers to help getting started with running E2E tests

rm -rf run.log
rm -rf tensorflow
rm -rf my-model
rm -rf ../../wrappers/s2i/python/_python/
Copy link
Contributor Author

Choose a reason for hiding this comment

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

These are generated files so I figured they could be included in the clean

@@ -3,6 +3,8 @@
import subprocess
import os
import time
import random
from retrying import retry
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Use of retry is to handle sporadic connectivity failures. See #473

Copy link
Contributor

@ukclivecox ukclivecox left a comment

Choose a reason for hiding this comment

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

Can we check the docs have been changed as well.

@ukclivecox ukclivecox merged commit 5c033e3 into master Apr 4, 2019
@ryandawsonuk ryandawsonuk deleted the seldon-core-ambassador-pr445 branch April 4, 2019 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants