faas-rs/faas
1
0
Fork 0
mirror of https://github.com/openfaas/faas.git synced 2025-06-10 01:06:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update items completed.

Browse Source
This commit is contained in:
Alex Ellis 2017-10-25 20:33:13 +01:00 committed by GitHub
parent ec60d97518
commit acfcc73ddb
1 changed files with 22 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

43
ROADMAP.md
View File

@ -40,6 +40,19 @@ Some of the more recent Completed Features:
* Asynchronous / long-running tasks via NATS Streaming * Asynchronous / long-running tasks via NATS Streaming
* CLI - invoke / list functions / query function info * CLI - invoke / list functions / query function info
* OS constraints in the deploy function API * OS constraints in the deploy function API
* helm chart
* Developer guide to using functions together - via pipes on client, or a "director" function on server
* Developer guide for DigitalOcean
* Re-branding to OpenFaaS
* New logo - graphic icon and text
* Website / landing page
* Non-root Docker templates for the CLI
* Integration with a reverse proxy - such as Traefik or Kong
* I.e. for TLS termination
* Basic auth for /system endpoints (probably via reverse proxy)
* AARCH64 (64-bit ARM) port (dependent on Docker release schedule)
* Healthchecks for functions deployed on Kubernetes
* Supporting request parameters via query-string
**Incoming requests and routing** **Incoming requests and routing**
@ -59,40 +72,29 @@ This binary fwatchdog acts as a watchdog for your function. Features:
* Language/binding independent - can invoke any UNIX process, including built-ins such as `wc` or `cat` * Language/binding independent - can invoke any UNIX process, including built-ins such as `wc` or `cat`
* Can also run Windows native binaries * Can also run Windows native binaries
## 2. Future items ## 2. Future/current work (subject to change)
Most items are detailed [via Github issues](https://github.com/openfaas/faas/issues). If you need an up-to-date picture of what is current and ready-for-use please reach out to the OpenFaaS maintainers through our Slack comunity. Most items are detailed [via Github issues](https://github.com/openfaas/faas/issues).
Native support is available for Docker Swarm and Kubernetes using primitive API objects in each orchestration platform. Native support is available for Docker Swarm and Kubernetes using primitive API objects in each orchestration platform.
Must have Must have
* Dedicated blog site built from GitHub pages or Hugo
* Developer Cloud guides: * Developer Cloud guides:
* for Digital Ocean * for Digital Ocean (done)
* for Packet * for Packet
* for AWS * for AWS
* Re-branding to OpenFaaS (in-progress)
* New logo - graphic icon and text (in-progress)
* Website / landing page (in progress)
* Developer guide for your first Node.js function * Developer guide for your first Node.js function
* Developer guide to using functions together - via pipes on client, or a "director" function on server
Should have Should have
* helm chart * Certifier for third-party integrations - via e2e tests (in progress)
* Certifier for third-party integrations (via e2e tests) * AfterBurn - fork once, use many which removes almost all runtime latency - (Alpha available)
* AfterBurn - fork once, use many which removes almost all runtime latency - (in progress) * Kafka queue worker implementation (async currently available by NATS Streaming) - available in pending PR
* Kafka queue worker implementation (async currently available by NATS Streaming)
* Non-root Docker templates for the CLI (in progress)
* Community templates for the FaaS-CLI (in progress) * Community templates for the FaaS-CLI (in progress)
* Our own "timer" (aka cron) for invoking functions on a regular basis - or a guide for setting this up via Jenkins or CRON * Our own "timer" (aka cron) for invoking functions on a regular basis - or a guide for setting this up via Jenkins or CRON
* Integration with a reverse proxy - such as Traefik or Kong
* I.e. for TLS termination
* Basic auth for /system endpoints (probably via reverse proxy)
* AARCH64 (64-bit ARM) port (dependent on Docker release schedule)
* Healthchecks for functions deployed on Kubernetes
Could have Could have
@ -106,13 +108,12 @@ Could have
* Scale to zero 0/0 replicas * Scale to zero 0/0 replicas
* Guide/proxy for Flask in a function * Guide/proxy for Flask in a function
Nice to have Nice to have
* Guide for basic authentication over HTTPs (set up externally through NGinx etc) * Guide for basic authentication over HTTPs (set up externally through NGinx etc)
* CRIU - (Checkpoint/Restore In Userspace) for starting serverless tasks with a high start-up cost/latency. * CRIU - (Checkpoint/Restore In Userspace) for starting serverless tasks with a high start-up cost/latency.
* Deeper tests coverage and integration tests * Deeper tests coverage and integration tests
* Serverless Inc framework support - as a "provider" * Serverless Inc framework support - as a "provider" (in progress)
On-going integrations in addition to Swarm and K8s: On-going integrations in addition to Swarm and K8s: