package peloton.api.v1alpha.pod.apachemesos

Get desktop application:
View/edit binary Protocol Buffers messages

Extra configuration only supported in the Mesos runtime.

Used in: PodSpec

• PodSpec.ContainerType type = 1

  Type of containerizer to use.

• repeated PodSpec.DockerParameter docker_parameters = 2

  Parameters to be passed to the Docker cli.

• repeated PodSpec.URI uris = 3

  URIs fetched before executing the command.

• bool shell = 4

  If shell is set to true, then the command will be launched via shell. TBD After this is supported by Kubelet runtime, move to pod.CommandSpec. This is a mandatory field to be provided if the additional mesos specification is provided as part of the pod specification.

• optional PodSpec.ExecutorSpec executor_spec = 5

  The executor configuration.

• optional PodSpec.NetworkSpec network_spec = 6

  The docker network configuration. This is only applicable when the container type is selected to be DOCKER.

Used in: PodSpec

• CONTAINER_TYPE_INVALID = 0

  Invalid container type

• CONTAINER_TYPE_DOCKER = 1

  Use Docker containerizer

• CONTAINER_TYPE_MESOS = 2

  Use Mesos containerizer

Arbitrary parameters to be passed to Docker CLI.

Used in: PodSpec

• string key = 1

• string value = 2

Configuration for the mesos executor.

Used in: PodSpec

• ExecutorSpec.ExecutorType type = 1

  Executor type. This is mandatory field, and if not provided, executor type is set to EXECUTOR_TYPE_INVALID.

• string executor_id = 2

  The executor identifier

• bytes data = 3

  Executor data

• optional ExecutorSpec.Resources resources = 4

  Executor resources

Used in: ExecutorSpec

• EXECUTOR_TYPE_INVALID = 0

• EXECUTOR_TYPE_DEFAULT = 1

  Mesos default executor

• EXECUTOR_TYPE_CUSTOM = 2

  Custom Mesos executor like Thermos

Resources to be given to the executor.

Used in: ExecutorSpec

• double cpu = 1

  CPU resources to be given to the executor.

• double mem_mb = 2

  Memory (in MB) to be given to the executor.

Network specification to determine which network should the container connect to. By default, the container connects to the host network. TODO Move to PodSpec once we determine how the network namespace in kubelets will get configured.

Used in: PodSpec

• NetworkSpec.NetworkType type = 1

  The network type.

• string name = 2

  Name of the user network which will be used by network isolator to determine the network that the container joins. It is up to the network isolator on the host to decide how to interpret this field.

Type of the network the container will connect to.

Used in: NetworkSpec

• NETWORK_TYPE_INVALID = 0

• NETWORK_TYPE_HOST = 1

  Connect container to host network.

• NETWORK_TYPE_BRIDGE = 2

  Connect container to bridge on the host to allow containers running on the same host to connect to each other.

• NETWORK_TYPE_NONE = 3

  Disable networking for the container.

• NETWORK_TYPE_USER = 4

  Connect to a user defined network.

URIs specified are fetched before executing the command. If the executable field for an uri is set, executable file permission is set on the downloaded file. Otherwise, if the downloaded file has a recognized archive extension (currently [compressed] tar and zip) it is extracted into the executor's working directory. This extraction can be disabled by setting `extract` to false. In addition, any environment variables are set before executing the command (so they can be used to "parameterize" the command). This used to fetch binaries in stateless workloads and data bundles in batch workloads. TBD After this is supported by Kubelet runtime, it should be moved to pod.ContainerSpec.

Used in: PodSpec

• string value = 1

• bool executable = 2

• bool extract = 3

  In case the fetched file is recognized as an archive, extract its contents into the sandbox. Note that a cached archive is not copied from the cache to the sandbox in case extraction originates from an archive in the cache.

• bool cache = 4

  If this field is "true", the fetcher cache will be used. If not, fetching bypasses the cache and downloads directly into the sandbox directory, no matter whether a suitable cache file is available or not. The former directs the fetcher to download to the file cache, then copy from there to the sandbox. Subsequent fetch attempts with the same URI will omit downloading and copy from the cache as long as the file is resident there. Cache files may get evicted at any time, which then leads to renewed downloading.

• string output_file = 5

  The fetcher's default behavior is to use the URI string's basename to name the local copy. If this field is provided, the local copy will be named with its value instead. If there is a directory component (which must be a relative path), the local copy will be stored in that subdirectory inside the sandbox.