513cebe7b7
* Add Virtual Kubelet provider for VIC Initial virtual kubelet provider for VMware VIC. This provider currently handles creating and starting of a pod VM via the VIC portlayer and persona server. Image store handling via the VIC persona server. This provider currently requires the feature/wolfpack branch of VIC. * Added pod stop and delete. Also added node capacity. Added the ability to stop and delete pod VMs via VIC. Also retrieve node capacity information from the VCH. * Cleanup and readme file Some file clean up and added a Readme.md markdown file for the VIC provider. * Cleaned up errors, added function comments, moved operation code 1. Cleaned up error handling. Set standard for creating errors. 2. Added method prototype comments for all interface functions. 3. Moved PodCreator, PodStarter, PodStopper, and PodDeleter to a new folder. * Add mocking code and unit tests for podcache, podcreator, and podstarter Used the unit test framework used in VIC to handle assertions in the provider's unit test. Mocking code generated using OSS project mockery, which is compatible with the testify assertion framework. * Vendored packages for the VIC provider Requires feature/wolfpack branch of VIC and a few specific commit sha of projects used within VIC. * Implementation of POD Stopper and Deleter unit tests (#4) * Updated files for initial PR
2.5 KiB
Windows-specific Container Configuration
This document describes the schema for the Windows-specific section of the container configuration. The Windows container specification uses APIs provided by the Windows Host Compute Service (HCS) to fulfill the spec.
Resources
You can configure a container's resource limits via the OPTIONAL resources field of the Windows configuration.
Memory
memory is an OPTIONAL configuration for the container's memory usage.
The following parameters can be specified:
-
limit(uint64, OPTIONAL) - sets limit of memory usage in bytes. -
reservation(uint64, OPTIONAL) - sets the guaranteed minimum amount of memory for a container in bytes.
Example
"windows": {
"resources": {
"memory": {
"limit": 2097152,
"reservation": 524288
}
}
}
CPU
cpu is an OPTIONAL configuration for the container's CPU usage.
The following parameters can be specified:
-
count(uint64, OPTIONAL) - specifies the number of CPUs available to the container. -
shares(uint16, OPTIONAL) - specifies the relative weight to other containers with CPU shares. The range is from 1 to 10000. -
percent(uint, OPTIONAL) - specifies the percentage of available CPUs usable by the container.
Example
"windows": {
"resources": {
"cpu": {
"percent": 50
}
}
}
Storage
storage is an OPTIONAL configuration for the container's storage usage.
The following parameters can be specified:
-
iops(uint64, OPTIONAL) - specifies the maximum IO operations per second for the system drive of the container. -
bps(uint64, OPTIONAL) - specifies the maximum bytes per second for the system drive of the container. -
sandboxSize(uint64, OPTIONAL) - specifies the minimum size of the system drive in bytes.
Example
"windows": {
"resources": {
"storage": {
"iops": 50
}
}
}
Network
network is an OPTIONAL configuration for the container's network usage.
The following parameters can be specified:
egressBandwidth(uint64, OPTIONAL) - specified the maximum egress bandwidth in bytes per second for the container.
Example
"windows": {
"resources": {
"network": {
"egressBandwidth": 1048577
}
}
}