openstack/qinling
Code Issues Proposed changes
d3356c3757
qinling/runtimes/python2
History
Lingxian Kong 4b06c280bb Add administrative operations for some resources 
Now, admin user could list/show/delete/update most of qinling
resources, except function deletion. Because function deletion
needs to delete the trust created for qinling service by its
owner, only end user has the authority to delete their trust.

Implements: blueprint qinling-admin-operations
Change-Id: I9ec4df59fbf8ac50c96d9677dd74c54677b307a5
2018-01-18 14:45:11 +13:00
..
custom-entrypoint.sh Limit resource consumption of function 2017-12-04 23:26:13 +13:00
Dockerfile Limit resource consumption of function 2017-12-04 23:26:13 +13:00
README.md Support python function input 2017-06-15 22:59:27 +12:00
requirements.txt Limit resource consumption of function 2017-12-04 23:26:13 +13:00
server.py Add administrative operations for some resources 2018-01-18 14:45:11 +13: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