Versions Compared

Old Version 6

changes.mady.by.user Stephen Lawrence

Saved on

compared with

New Version 7

changes.mady.by.user Yevgen Abramov

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. OCI runtime specification gaps
    The OCI Container runtime specification is missing some controls typically required in embedded applications. The task is to specify them in an open specification.

OCI runtime specification gaps

The OCI container runtime specification has somewhat of a cloud focus, for example concentrating on network port connections, which lacks some controls typically required in embedded applications that has more diverse IP in h/w. Standardisation of the missing controls and their definition is therefore beneficial. Controls should be upstreamed where possible.

OCIspecifications providea detailed explanation of how to limit resources for the container, but currently, there is no specification that covers how to provide limits that will be used by OCI runtime specifications.  
Thes deployment specification could be divided into two parts: 

  • Container deployment that is created by the user to define limits 
  • Container deployment configuration that is used by container compositor to generate OCI runtime specification

Key parameters and limits should be covered by deployment specifications: 

  • Container quotas 
  • Container network configuration 
  • Access to hos devices and resources 

Examples can be found in VSC PR #39