-
Notifications
You must be signed in to change notification settings - Fork 543
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
glossary: Merge into the definitions file
There is no reason to separate these from the definitions which are already there. But the existing definition paragraphs define multiple terms a piece, so I haven't converted them to the alphabetized labeled-list format I've been using for glossary entries. Signed-off-by: W. Trevor King <wking@tremily.us>
- Loading branch information
Showing
4 changed files
with
38 additions
and
47 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,41 @@ | ||
Definitions | ||
----------- | ||
|
||
:rfc2119: http://tools.ietf.org/html/rfc2119 | ||
:c99-unspecified: http://www.open-std.org/jtc1/sc22/wg14/www/C99RationaleV5.10.pdf#page=18 | ||
:json: https://tools.ietf.org/html/rfc7159 | ||
:namespaces-7: http://man7.org/linux/man-pages/man7/namespaces.7.html | ||
:rfc2119: http://tools.ietf.org/html/rfc2119 | ||
:utf-8: http://www.unicode.org/versions/Unicode8.0.0/ch03.pdf | ||
|
||
In the specifications in the above table of contents, the keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in {rfc2119}[RFC 2119] (Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997). | ||
|
||
The keywords "unspecified", "undefined", and "implementation-defined" are to be interpreted as described in the {c99-unspecified}[rationale for the C99 standard]. | ||
|
||
An implementation is not compliant for a given CPU architecture if it fails to satisfy one or more of the MUST, REQUIRED, or SHALL requirements for the protocols it implements. | ||
An implementation is compliant for a given CPU architecture if it satisfies all the MUST, REQUIRED, and SHALL requirements for the protocols it implements. | ||
|
||
[[bundle-definition,bundle]] bundle:: | ||
A <<bundle,directory structure>> that is written ahead of time, distributed, and used to seed the runtime for creating a <<container>> and launching a process within it. | ||
|
||
[[config-definition,configuration]] configuration:: | ||
The <<config,`config.json`>> file in a <<bundle-definition>> which defines the intended <<container>> and container process. | ||
|
||
[[container,container]] container:: | ||
An environment for executing processes with configurable isolation and resource limitations. | ||
For example, namespaces, resource limits, and mounts are all part of the container environment. | ||
|
||
[[container-namespace,container namespace]] container namespace:: | ||
On Linux, a leaf in the {namespaces-7}[namespace] hierarchy in which the <<process,configured process>> executes. | ||
|
||
[[json,JSON]] JSON:: | ||
All configuration {json}[JSON] MUST be encoded in {utf-8}[UTF-8]. | ||
JSON objects MUST NOT include duplicate names. | ||
The order of entries in JSON objects is not significant. | ||
|
||
[[runtime-definition,runtime]] runtime:: | ||
An implementation of this specification. | ||
It reads the <<config-definition>> from a <<bundle-definition>>, uses that information to create a <<container>>, launches a process inside the container, and performs other <<runtime,lifecycle actions>>. | ||
|
||
[[runtime-namespace,runtime namespace]] runtime namespace:: | ||
On Linux, a leaf in the {namespaces-7}[namespace] hierarchy from which the <<runtime-definition>> process is executed. | ||
New <<container-namespace,container namespaces>> will be created as children of the runtime namespaces. |
This file was deleted.
Oops, something went wrong.