f2189a0468
After function autoscaling support, it's impossible for qinling-engine to get execution log because it doesn't know which pod it is talking to. So, it's neccessary for the runtime to return execution logs to qinling engine. The qinling client is not affected. Change-Id: I96dfd00cc83d8b8a5e8c601ee3800b1ef1a45b1b
Qinling
Note
Qinling (is pronounced "tʃinliŋ") refers to Qinling Mountains in southern Shaanxi Province in China. The mountains provide a natural boundary between North and South China and support a huge variety of plant and wildlife, some of which is found nowhere else on Earth.
Qinling is Function as a Service for OpenStack. This project aims to provide a platform to support serverless functions (like AWS Lambda). Qinling supports different container orchestration platforms (Kubernetes/Swarm, etc.) and different function package storage backends (local/Swift/S3) by nature using plugin mechanism.
- Free software: Apache license
- Documentation: http://qinling.readthedocs.io/
- Source: http://git.openstack.org/cgit/openstack/qinling
- Features: https://blueprints.launchpad.net/qinling
- Bug Track: http://bugs.launchpad.net/qinling
- IRC channel on Freenode: #openstack-qinling