commit | 0f3ef780124622e1983e9bc693109bca94b5c7d4 | [log] [tgz] |
---|---|---|
author | Cosmin Stanciu <selfxp@users.noreply.github.com> | Wed Apr 29 22:18:27 2020 -0700 |
committer | GitHub <noreply@github.com> | Wed Apr 29 22:18:27 2020 -0700 |
tree | 4b2d170c5f1d7bac5f5d8762f4cc6a7100c65574 | |
parent | 154faf985262f4fd0e06ca55b0fc96b6e37c3965 [diff] |
Disable db record store for successful blocking activations (#4885) * Make container proxy activation store configurable * Format code * Add tests * Don't copy message in case of blocking action * Don't store sequences and compositions when disable store config is true * Make splunk logs available for activations with no db entry * Make elasticsearch logs available for activations with no db entry * Format code * Add comment for disable-store-result configuration * Update configuration description * Move logic for activation store disable to a central location * Update common/scala/src/main/resources/application.conf Co-Authored-By: rodric rabbah <rodric@gmail.com> * Update common/scala/src/main/scala/org/apache/openwhisk/core/database/ActivationStore.scala Co-Authored-By: rodric rabbah <rodric@gmail.com> * Update common/scala/src/main/scala/org/apache/openwhisk/core/database/ActivationStore.scala Co-Authored-By: rodric rabbah <rodric@gmail.com> * Update tests/src/test/scala/org/apache/openwhisk/core/controller/test/ControllerTestCommon.scala Co-Authored-By: rodric rabbah <rodric@gmail.com> * Remove creation of bogus WhiskActivation record * Wrap start, end and logs parameters in Options * Read disableStore configuration only from ActivationStore * Add logging for activations that have not been stored * Including action name in the log message * Make splunk api max-time and max earliest_time configurable * Pass disableStore as explicit not implicit parameter * Define variables as FiniteDuration * Use ActivationId instead of String * Update common/scala/src/main/scala/org/apache/openwhisk/core/database/ActivationStore.scala Co-Authored-By: rodric rabbah <rodric@gmail.com> * Fix tests Co-authored-by: rodric rabbah <rodric@gmail.com>
OpenWhisk is a serverless functions platform for building cloud applications. OpenWhisk offers a rich programming model for creating serverless APIs from functions, composing functions into serverless workflows, and connecting events to functions using rules and triggers. Learn more at http://openwhisk.apache.org.
The easiest way to start using OpenWhisk is to install the “Standalone” OpenWhisk stack. This is a full-featured OpenWhisk stack running as a Java process for convenience. Serverless functions run within Docker containers. You will need Docker, Java and Node.js available on your machine.
To get started:
git clone https://github.com/apache/openwhisk.git cd openwhisk ./gradlew core:standalone:bootRun
When the OpenWhisk stack is up, it will open your browser to a functions Playground, typically served from http://localhost:3232. The Playground allows you create and run functions directly from your browser.
To make use of all OpenWhisk features, you will need the OpenWhisk command line tool called wsk
which you can download from https://s.apache.org/openwhisk-cli-download. Please refer to the CLI configuration for additional details. Typically you configure the CLI for Standalone OpenWhisk as follows:
wsk property set \ --apihost 'http://localhost:3233' \ --auth '23bc46b1-71f6-4ed5-8c54-816aa4f8c502:123zO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwP'
OpenWhisk can also be installed on a Kubernetes cluster. You can use a managed Kubernetes cluster provisioned from a public cloud provider (e.g., AKS, EKS, IKS, GKE), or a cluster you manage yourself. Additionally for local development, OpenWhisk is compatible with Minikube, and Kubernetes for Mac using the support built into Docker 18.06 (or higher).
To get started:
git clone https://github.com/apache/openwhisk-deploy-kube.git
Then follow the instructions in the OpenWhisk on Kubernetes README.md.
Browse the documentation to learn more. Here are some topics you may be interested in:
Report bugs, ask questions and request features here on GitHub.
You can also join the OpenWhisk Team on Slack https://openwhisk-team.slack.com and chat with developers. To get access to our public Slack team, request an invite https://openwhisk.apache.org/slack.html.
The OpenWhisk system is built from a number of components. The picture below groups the components by their GitHub repos. Please open issues for a component against the appropriate repo (if in doubt just open against the main openwhisk repo).