This repository was archived by the owner on Nov 10, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7
Enarx wasm workload details
Mike Bursell edited this page Oct 2, 2020
·
1 revision
This page records the various options and configuration pieces to be loaded into a Enarx-wasmldr instance. Those entries in bold are targeted for initial implementation. Those marked with a question mark ("?") are still under consideration.
- Application - information about the application and its requirement
- Hints - information which may be of interest to the deploying party, but may be ignored or overridden
- Memory - amount of memory requested
- TEE Technology? - type of TEE requested (e.g. for performance)
- Requirements
- Wasm file - name of the workload
- Pre-Opened File Descriptors - any file descriptors required
- Key/Values Config Values - key/value tuples
- Bundled Data - list of data required for operation of the workload, expected to be bundled with the workload
- Bundled Data
- /app - the workload to be run
- /data - bundled data
- Hints - information which may be of interest to the deploying party, but may be ignored or overridden
- Deployment - requirements for the deployment environment
- Set-up File Descriptors - file descriptors required for operation of the workload
- Connect - file descriptors to be opened in "connect" mode
- TCP
- UDP
- TLS
- with or without client certificate
- QUIC
- Listen - file descriptors to be opened in "listen" mode
- TCP
- UDP
- TLS
- Host Certificate
- Client CA(s) + max number of intermediaries
- Identity?
- QUIC
- Stdio - stdio
- Passthrough - TBD
- Connect - file descriptors to be opened in "connect" mode
- Key/Value Config
- Filesystems:
- Workload-managed
- /cfg - configuration bundled data
- /mnt - host filesystem - external to the TEE
- wasm-loader-managed:
- /tmp - temporary file storage - assumed to be ephemeral
- Workload-managed
- Set-up File Descriptors - file descriptors required for operation of the workload