History

Lingxian Kong 55c7e5f496 Do not get openstack session in container If the function is triggered by job, it's very hard to get openstack serssion based on trust id, unless the qinling service credentials are passed which will lead to security issue. So, this patch will remove 'context' param for user function. Change-Id: Ib0e185ad9729cf59e308b7ded683911a92624ad0		2017-08-06 15:02:49 +12:00
..
Dockerfile	Disable python buffer for stdout/stderr	2017-07-17 23:47:23 +12:00
README.md	Support python function input	2017-06-15 22:59:27 +12:00
requirements.txt	Support Keystone session in python runtime	2017-07-03 01:16:40 +12:00
server.py	Do not get openstack session in container	2017-08-06 15:02:49 +12:00

README.md

Qinling: Python Environment

This is the Python environment for Qinling.

It's a Docker image containing a Python 2.7 runtime, along with a dynamic loader. A few common dependencies are included in the requirements.txt file. End users need to provide their own dependencies in their function packages through Qinling API or CLI.

Rebuilding and pushing the image

You'll need access to a Docker registry to push the image, by default it's docker hub. After modification, build a new image and upload to docker hub:

docker build -t USER/python-runtime . && docker push USER/python-runtime

Using the image in Qinling

After the image is ready in docker hub, create a runtime in Qinling:

http POST http://127.0.0.1:7070/v1/runtimes name=python2.7 image=USER/python-runtime