Skip to content
This repository was archived by the owner on Nov 10, 2022. It is now read-only.

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.

  1. Application - information about the application and its requirement
    1. Hints - information which may be of interest to the deploying party, but may be ignored or overridden
      1. Memory - amount of memory requested
      2. TEE Technology? - type of TEE requested (e.g. for performance)
    2. Requirements
      1. Wasm file - name of the workload
      2. Pre-Opened File Descriptors - any file descriptors required
      3. Key/Values Config Values - key/value tuples
      4. Bundled Data - list of data required for operation of the workload, expected to be bundled with the workload
    3. Bundled Data
      1. /app - the workload to be run
      2. /data - bundled data
  2. Deployment - requirements for the deployment environment
    1. Set-up File Descriptors - file descriptors required for operation of the workload
      1. Connect - file descriptors to be opened in "connect" mode
        1. TCP
        2. UDP
        3. TLS
          1. with or without client certificate
        4. QUIC
      2. Listen - file descriptors to be opened in "listen" mode
        1. TCP
        2. UDP
        3. TLS
          1. Host Certificate
          2. Client CA(s) + max number of intermediaries
          3. Identity?
        4. QUIC
      3. Stdio - stdio
      4. Passthrough - TBD
    2. Key/Value Config
    3. Filesystems:
      1. Workload-managed
        1. /cfg - configuration bundled data
        2. /mnt - host filesystem - external to the TEE
      2. wasm-loader-managed:
        1. /tmp - temporary file storage - assumed to be ephemeral
Clone this wiki locally