constraints: add as part of design documents

Let's keep all design documents in the same logical location. Updating
the file to be called 'cpu-constraints', though we may want to expand to
resource constraints going forward.

Fixes: #417

Signed-off-by: Eric Ernst <eric.ernst@intel.com>
This commit is contained in:
Eric Ernst 2019-03-29 10:06:02 -07:00
parent 353b2ecf9f
commit c0d63796a2
3 changed files with 2 additions and 2 deletions

View File

@ -138,7 +138,7 @@ these commands is potentially challenging.
See issue https://github.com/clearcontainers/runtime/issues/341 and [the constraints challenge](#the-constraints-challenge) for more information.
For CPUs resource management see
[cpu-constraints](constraints/cpu.md).
[cpu-constraints](design/cpu-constraints.md).
### docker run and shared memory

View File

@ -130,5 +130,5 @@ the containers are removed automatically.
[2]: https://github.com/kata-containers/proxy
[3]: https://github.com/hashicorp/yamux
[4]: https://wiki.qemu.org/Features/VirtioVsock
[5]: https://github.com/kata-containers/documentation/blob/master/constraints/cpu.md#virtual-cpus-and-kubernetes-pods
[5]: https://github.com/kata-containers/documentation/blob/master/design/cpu-constraints.md#virtual-cpus-and-kubernetes-pods
[6]: https://github.com/kata-containers/shim