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
Change-Id: Iff1ff646a6df263b2770b8cebc74e80ab18c7613
After execution is finished, Qinling provides API to query execution
log for audit, debug or other purposes.
Implements: blueprint qinling-logs
Change-Id: Ie92619bf238c8e72e15c350c65bfbbb88a065f97
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
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
when downloading.
Change-Id: I8170bfb1c5f8b6cf88a744547db12cc12248aaca
When deleting function, the service mapping record should be
deleted automatically.
Provide a helper script for resource clean up.
Change-Id: Ie3db454b5bcfb74a0826f01c4626fb45fca58478
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.
Change-Id: I0cb885dd6005ba024e3816bae9b79b0d3f35d335
Keystone session can be used directly in user function to access
OpenStack services.
Include openstack clients in python requirements as well.
Add a python function example.
Implements: blueprint qinling-openstack-clients
Change-Id: I4798c404cb57bafe14049f57ba8db7c7125106c7
If update image, will send asynchronous request to engine. If some
error happened during update, engine will rollback runtime
automatically.
Change-Id: I1598b1c04427dfdb7d573bbff8dc017f113c2fd2
When deleting function, we should remove all the allocated resources
in the orchestrator, no matter what kind of source the function is
using.
Change-Id: I7ee3d1bb1e6b417194a1b86606f8fcd64cb598cf
Currenty, the function entry is hard-coded to be 'main.main' which is
not flexible. This patch adds support for specifying module name and
function name in the code package.
Change-Id: I92ea36f668073f380a4aef4526a6fad321d8cc95
When a package function is executed, a service url is cached so it's
faster when function is executed again. But this will lead to problem
if function is never executed for a long time.
This patch add an expiry machanism which will release resources in
orchestration platform.
Change-Id: I754ebe314d87f6d7c194d9b9c061316f7ba74245
Invoke a function in sync way means the command will wait until the
execution finish. On the contrary, 'sync=false' means user will get
a response before the function is actually invoked. User could get
execution status using execution ID in the response.
Change-Id: I605ea8414f49d44899e0bc8c36b89e48e335d284
Allow user to create function using her own docker image including
all the code and dependencies inside. The image needs to have an
script running as entry point, expecting user's input as params.
This allow users to execute functions written in any language.
With this patch, users can create function using swift object:
http POST http://127.0.0.1:7070/v1/functions name=swift_function \
runtime_id=xxx \
code='{"source": "swift", "swift": {"container": "container_name", "object": "object_name"}}'
Implements: blueprint support-swift-object-as-code
Lingxian Kong