-
Notifications
You must be signed in to change notification settings - Fork 280
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
Ensure container/model is ready to be queried #447
Conversation
…ausing two models to register
…to develop Merging reformatted code
Added docker/k8s container checking
…_data, a DataDesc object
Test FAILed. |
Test FAILed. |
Jenkins test this please |
Test FAILed. |
Test FAILed. |
Test FAILed. |
@chester-leung what's the status of this? Are you waiting on a review? |
Test FAILed. |
Test FAILed. |
@dcrankshaw I'm trying to figure out why the build is failing - the tests are all passing when I run them locally. I encountered a problem locally similar to the current error when I hadn't rebuilt the py-rpc docker image to have the healthcheck. I think somehow the healthcheck isn't being set for the containers when Jenkins runs the tests. |
Test FAILed. |
Jenkins test this please |
Test FAILed. |
Test FAILed. |
Test PASSed. |
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.
lgtm
Implemented Docker healtcheck and Kubernetes readiness probe to ensure that a container/model is ready to be queried. This change blocks
deploy_model()
until we get explicit notification that the container/model is running.Also changes pull policy in query frontend and management frontend such that new Docker images are always pulled.
Fixes #436, Fixes #425, Fixes #152