From 00a4c76efeebb244f6e7cb0da7f6cb81adcba42a Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Wed, 24 May 2017 09:30:01 -0700 Subject: [PATCH 1/2] glossary: Remove "leaf" and "hierarchy" from container namespace definition Namespaces are not all hierarchical and processes aren't always in leaves. Signed-off-by: W. Trevor King --- glossary.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/glossary.md b/glossary.md index 09f80e421..b19f81601 100644 --- a/glossary.md +++ b/glossary.md @@ -15,7 +15,7 @@ For example, namespaces, resource limits, and mounts are all part of the contain ## Container namespace -On Linux, a leaf in the [namespace][namespaces.7] hierarchy in which the [configured process](config.md#process) executes. +On Linux,the [namespaces][namespaces.7] in which the [configured process](config.md#process) executes. ## JSON From b536f130541643a2aa6a4dfc9145dabad1523407 Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Wed, 24 May 2017 09:38:11 -0700 Subject: [PATCH 2/2] glossary: Remove "leaf" and "hierarchy" from runtime namespace definition Namespaces are not all hierarchical and processes aren't always in leaves. Also punt to config-linux.md for details about namespace creation, although currently that section doesn't talk much about how the runtime namespaces relate to new container namespaces [1]. Also mention resource access, because runtime namespaces play a role even if no new container namespaces are created. I've used resources that currently explicitly mention runtime namespaces as examples, although I think more resources (e.g. root.path and mounts[].source [2,3]) deserve wording about that as well and would be better examples if they'd already landed such wording. Examples of resources retrieved from this namespace include linux.namespaces[].path and the resctrl psuedo-filesystem used for `linux.intelRdt`, but Mrunal and Michael didn't want me to include the examples in the glossary entry (probably because they could go stale). [1]: https://github.com/opencontainers/runtime-spec/pull/795#issuecomment-303768518 [2]: https://github.com/opencontainers/runtime-spec/pull/735#issuecomment-301198710 [3]: https://github.com/opencontainers/runtime-spec/commit/604205e5e1b58854c43e07901d3ec241df31df4e#diff-c9c91c29b41257aea3a3403cc606ad99R65 Signed-off-by: W. Trevor King --- glossary.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/glossary.md b/glossary.md index b19f81601..6180db4c5 100644 --- a/glossary.md +++ b/glossary.md @@ -30,9 +30,7 @@ It reads the [configuration files](#configuration) from a [bundle](#bundle), use ## Runtime namespace -On Linux, a leaf in the [namespace][namespaces.7] hierarchy from which the [runtime](#runtime) process is executed. -New container namespaces will be created as children of the runtime namespaces. - +On Linux, the namespaces from which new [container namespaces](#container-namespace) are [created](config-linux.md#namespaces) and from which some configured resources are accessed. [JSON]: https://tools.ietf.org/html/rfc7159 [UTF-8]: http://www.unicode.org/versions/Unicode8.0.0/ch03.pdf