apache/openwhisk

provide a run-once mode that disables container reuse

Open

#3,896 opened on Jul 24, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Scala (1,177 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (6,777 stars)
PR merge metrics
 (Avg merge 17h 31m) (3 merged PRs in 30d)

Description

Today we reuse containers for performance reasons. There are many advantages however to run-once that disables container reuse. Just as @tysonnorris is adding support for intra-container concurrency via an opt-in annotation, we can do the same to prevent container reuse for an action annotated accordingly to create a new container every time. This has the nice property of ensuring that every function starts from the same pristine environment.

Contributor guide

Research direction
Study how container reuse is currently implemented in OpenWhisk and how annotations are processed. Look at the intra container concurrency feature (PR by @tysonnorris) for a similar annotation pattern. Then propose a new annotation to disable container reuse for specific actions, ensuring each invocation starts with a fresh container.
Tech stack
scala
Domain
backendclouddevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ScalaDockerserverless concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60