Files

T

Ta-Ching ChenandGitHub fe8fa94c77 Enable concurrent CI builds (#1236 )

Currently, only one CI build can be started at the same time due to we only have only one testing cluster. This PR aims to enable multiple concurrent builds can be triggered to reduce the waiting time for CI builds. The major changes listed below:

1. Each build generate unique images for testing and debugging
2. Check whether the testing cluster is being used by another build.
3. Cache docker image & go mod after build finished
4. Improve dockerfiles for reusing docker build cache

2019-07-15 16:33:26 +08:00

Dockerfile

Enable concurrent CI builds (#1236 )

2019-07-15 16:33:26 +08:00

README.md

Add experimental environment: tensorflow-serving (#1212 )

2019-07-02 15:43:55 +08:00

server.go

Add experimental environment: tensorflow-serving (#1212 )

2019-07-02 15:43:55 +08:00

README.md

Fission: Tensorflow Serving Environment

This is the Tensorflow Serving environment for Fission.

It's a Docker image containing a Go runtime, along with a tensorflow serving service.

How it works

Tensorflow Serving is an serving service that supports both RESTful API and gRPC endpoints. In current implementation, Go server launches tensorflow_model_server to load in model during specialization. As long as the Go server receives requests from router it creates a reverse proxy that connects to RESTful API endpoint exposed by tensorflow_model_server and get response from the upstream server for user.

Build this image

docker build -t USER/tensorflow-serving . && docker push USER/tensorflow-serving

Using the image in fission

You can add this customized image to fission with "fission env create":

fission env create --name tensorflow --image USER/tensorflow-serving --version 2

After this, fission functions that have the env parameter set to the same environment name as this command will use this environment.