Roadmap doc formatting
This commit is contained in:
+57
-59
@@ -2,106 +2,104 @@
|
|||||||
|
|
||||||
## Function features (area-func)
|
## Function features (area-func)
|
||||||
|
|
||||||
Secrets, configmaps, env vars
|
- Secrets, configmaps, env vars
|
||||||
Volumes
|
- Volumes
|
||||||
Mem requests and limits
|
- Mem requests and limits
|
||||||
Function exec time deadline
|
- Function exec time deadline
|
||||||
Expose a regular K8s Service for a function
|
- Expose a regular K8s Service for a function
|
||||||
|
|
||||||
## Fission API (area-api)
|
## Fission API (area-api)
|
||||||
|
|
||||||
TPR-based controller
|
- TPR-based controller
|
||||||
API authentication
|
- API authentication
|
||||||
Aggregated API server
|
- Aggregated API server
|
||||||
|
|
||||||
## Development Workflows (area-dev)
|
## Development Workflows (area-dev)
|
||||||
|
|
||||||
Function Versioning
|
- Function Versioning
|
||||||
Versioning for a group of functions
|
- Versioning for a group of functions
|
||||||
Rolling upgrades
|
- Rolling upgrades
|
||||||
for one function
|
- for one function
|
||||||
for multiple functions
|
- for multiple functions
|
||||||
for functions + other kubernetes deployments
|
- for functions + other kubernetes deployments
|
||||||
Unit testing
|
- Unit testing
|
||||||
|
|
||||||
## API Gateway / Ingress features (area-ingress)
|
## API Gateway / Ingress features (area-ingress)
|
||||||
|
|
||||||
Function authn hooks
|
- Function authn hooks
|
||||||
K8s Ingress flag
|
- K8s Ingress flag
|
||||||
Bundle an ingress controller?
|
- Bundle an ingress controller?
|
||||||
|
|
||||||
## Workflows and Function composition (area-composition)
|
## Workflows and Function composition (area-composition)
|
||||||
|
|
||||||
Simple Composition - Sync
|
- Simple Composition - Sync
|
||||||
Simple Composition - Async
|
- Simple Composition - Async
|
||||||
Hooks (pre, post, on-error)
|
- Hooks (pre, post, on-error)
|
||||||
Workflows
|
- Workflows
|
||||||
Testing in the presence of function composition
|
- Testing in the presence of function composition
|
||||||
|
|
||||||
## Events (area-events)
|
## Events (area-events)
|
||||||
|
|
||||||
NATS
|
- NATS
|
||||||
Kafka
|
- Kafka
|
||||||
AWS: SNS, SQS
|
- AWS: SNS, SQS
|
||||||
Google PubSub
|
- Google PubSub
|
||||||
RabbitMQ
|
- RabbitMQ
|
||||||
Other event sources
|
- Other event sources
|
||||||
|
|
||||||
Bundle an event queue (NATS streaming, most probably)
|
|
||||||
|
|
||||||
|
- Bundle an event queue (NATS streaming, most probably)
|
||||||
|
|
||||||
## Operability (area-ops)
|
## Operability (area-ops)
|
||||||
|
|
||||||
### Fission Install/Upgrade (area-install)
|
### Fission Install/Upgrade (area-install)
|
||||||
|
|
||||||
Helm Installer for Fission
|
- Helm Installer for Fission
|
||||||
Helm installation for fission functions
|
- Helm installation for fission functions
|
||||||
CLI installer/upgrader? ("fission upgrade")
|
- CLI installer/upgrader? ("fission upgrade")
|
||||||
Upgrade checker/reminder (like minikube does)
|
- Upgrade checker/reminder (like minikube does)
|
||||||
CLI auto-upgrader
|
- CLI auto-upgrader
|
||||||
|
|
||||||
### Function observation (area-observe)
|
### Function observation (area-observe)
|
||||||
|
|
||||||
Function Logging
|
- Function Logging
|
||||||
Tracing -- Opentracing
|
- Tracing -- Opentracing
|
||||||
Metrics -- Prometheus
|
- Metrics -- Prometheus
|
||||||
Function exception tracking
|
- Function exception tracking
|
||||||
Logging function load errors
|
- Logging function load errors
|
||||||
Tracing fission overheads for each function
|
- Tracing fission overheads for each function
|
||||||
|
|
||||||
## Function Security
|
## Function Security
|
||||||
|
|
||||||
Function isolation (is authz hook sufficient or do we need something like mutual TLS?)
|
- Function isolation (is authz hook sufficient or do we need something like mutual TLS?)
|
||||||
|
|
||||||
## UX, especially for beginners (area-ux)
|
## UX, especially for beginners (area-ux)
|
||||||
|
|
||||||
Fission CLI should include a tutorial
|
- Fission CLI should include a tutorial
|
||||||
Fission CLI should have a way to drop you into the UI
|
- Fission CLI should have a way to drop you into the UI
|
||||||
Eliminate FISSION_URL, just use kube client to find fission url. Also useful to grab credentials.
|
- Eliminate FISSION_URL, just use kube client to find fission url. Also useful to grab credentials.
|
||||||
|
|
||||||
## Documentation (area-doc)
|
## Documentation (area-doc)
|
||||||
|
|
||||||
Installation guide improvements
|
- Installation guide improvements
|
||||||
Troubleshooting guide for common problems
|
- Troubleshooting guide for common problems
|
||||||
FAQ
|
- FAQ
|
||||||
Performance overview
|
- Performance overview
|
||||||
Render docs nicely to fission.io
|
- Render docs nicely to fission.io
|
||||||
|
|
||||||
## Web UI (tracked separately in the fission-ui repo)
|
## Web UI (tracked separately in the fission-ui repo)
|
||||||
|
|
||||||
## Performance and Scalability (area-perf)
|
## Performance and Scalability (area-perf)
|
||||||
|
|
||||||
Autoscaling
|
- Autoscaling
|
||||||
Cold-start optimization -- optimistically choose from pool, save about ~20msec
|
- Cold-start optimization -- optimistically choose from pool, save about ~20msec
|
||||||
Cold-start optimization -- preload funcs in fetcher
|
- Cold-start optimization -- preload funcs in fetcher
|
||||||
Cold-start optimization -- preload libraries in envs (v2) -- mem vs. speed tradeoff
|
- Cold-start optimization -- preload libraries in envs (v2) -- mem vs. speed tradeoff
|
||||||
|
|
||||||
## Function extensibility (area-ext)
|
## Function extensibility (area-ext)
|
||||||
|
|
||||||
Env v2: easy addition of dependencies etc.
|
- Env v2: easy addition of dependencies etc.
|
||||||
Integration with Service Broker
|
- Integration with Service Broker
|
||||||
|
|
||||||
## Multi-area stuff
|
## Multi-area stuff
|
||||||
|
|
||||||
Execution strategies: cold-start pool vs create-pod-on-cold-start
|
- Execution strategies: cold-start pool vs create-pod-on-cold-start -- one size doesn't fit all, at least with current tech; abstract over execution strategies according to requirements
|
||||||
-- one size doesn't fit all, at least with current tech; abstract over execution strategies according to requirements
|
|
||||||
|
|||||||
Reference in New Issue
Block a user