After function autoscaling support, it's impossible for qinling-engine
to get execution log because it doesn't know which pod it is talking
So, it's neccessary for the runtime to return execution logs to
The qinling client is not affected.
Provide an API to do scale up operation, leave the container
monitoring to orchestrator underlay, although k8s already supports
HPA, but we should not rely on specific container orchestrator
capability for general purpose.
Partially implements: blueprint qingling-autoscaling
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.
OpenStack service session is generated when downloading code from
inside the container, but when the function is invoked at a deferred
time, the token may already be expiried.
Need to create the session when executing the function instead of
This is part-1 of jobs support in Qinling.
With job API, users can create a job with an existing function
that can be ran in cron job's fashion, but the job definition
has more capabilities than cron.
Keystone session can be used directly in user function to access
Include openstack clients in python requirements as well.
Add a python function example.
Implements: blueprint qinling-openstack-clients