You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by gi...@apache.org on 2018/05/29 22:22:57 UTC
mesos-site git commit: Updated the website built from mesos SHA:
0ffafd4.
Repository: mesos-site
Updated Branches:
refs/heads/asf-site 80b3e0f25 -> 85919a828
Updated the website built from mesos SHA: 0ffafd4.
Project: http://git-wip-us.apache.org/repos/asf/mesos-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos-site/commit/85919a82
Tree: http://git-wip-us.apache.org/repos/asf/mesos-site/tree/85919a82
Diff: http://git-wip-us.apache.org/repos/asf/mesos-site/diff/85919a82
Branch: refs/heads/asf-site
Commit: 85919a8289ff532d7cb7f25a65e3dfd861e09557
Parents: 80b3e0f
Author: jenkins <bu...@apache.org>
Authored: Tue May 29 22:22:53 2018 +0000
Committer: jenkins <bu...@apache.org>
Committed: Tue May 29 22:22:53 2018 +0000
----------------------------------------------------------------------
.../latest/configuration/agent/index.html | 313 ++++++++++++-------
.../configuration/master-and-agent/index.html | 74 +++--
.../latest/configuration/master/index.html | 135 +++++---
.../latest/isolators/linux-devices/index.html | 198 ++++++++++++
.../latest/mesos-containerizer/index.html | 1 +
.../documentation/latest/upgrades/index.html | 10 +
.../mesos-containerizer/index.html | 1 +
content/documentation/upgrades/index.html | 10 +
content/sitemap.xml | 4 +
9 files changed, 569 insertions(+), 177 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/85919a82/content/documentation/latest/configuration/agent/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/configuration/agent/index.html b/content/documentation/latest/configuration/agent/index.html
index deaf98f..4387fc5 100644
--- a/content/documentation/latest/configuration/agent/index.html
+++ b/content/documentation/latest/configuration/agent/index.html
@@ -111,7 +111,7 @@
<h2>Required Flags</h2>
-<table class="table table-striped">
+<table class=".anchored table table-striped">
<thead>
<tr>
<th width="30%">
@@ -122,7 +122,7 @@
</th>
</tr>
</thead>
-<tr>
+<tr id="master">
<td>
--master=VALUE
</td>
@@ -134,7 +134,7 @@ May be one of:
<code>file:///path/to/file</code> (where file contains one of the above)
</td>
</tr>
-<tr>
+<tr id="work_dir">
<td>
--work_dir=VALUE
</td>
@@ -152,7 +152,7 @@ occurs. (Example: <code>/var/lib/mesos/agent</code>)
<h2>Optional Flags</h2>
-<table class="table table-striped">
+<table class=".anchored table table-striped">
<thead>
<tr>
<th width="30%">
@@ -163,7 +163,7 @@ occurs. (Example: <code>/var/lib/mesos/agent</code>)
</th>
</tr>
</thead>
-<tr>
+<tr id="acls">
<td>
--acls=VALUE
</td>
@@ -191,7 +191,7 @@ Example:
</td>
</tr>
-<tr>
+<tr id="agent_features">
<td>
--agent_features=VALUE
</td>
@@ -212,7 +212,7 @@ Example:
</td>
</tr>
-<tr>
+<tr id="agent_subsystems">
<td>
--agent_subsystems=VALUE,
<p/>
@@ -225,9 +225,9 @@ Present functionality is intended for resource monitoring and
no cgroup limits are set, they are inherited from the root mesos
cgroup.
</td>
-
</tr>
-<tr>
+
+<tr id="effective_capabilities">
<td>
--effective_capabilities=VALUE
</td>
@@ -256,8 +256,7 @@ Example:
</td>
</tr>
-</tr>
-<tr>
+<tr id="bounding_capabilities">
<td>
--bounding_capabilities=VALUE
</td>
@@ -275,7 +274,7 @@ This flag has the same syntax as <code>--effective_capabilities</code>.
</td>
</tr>
-<tr>
+<tr id="appc_simple_discovery_uri_prefix">
<td>
--appc_simple_discovery_uri_prefix=VALUE
</td>
@@ -286,7 +285,8 @@ e.g., <code>http://</code>, <code>https://</code>,
(default: http://)
</td>
</tr>
-<tr>
+
+<tr id="appc_store_dir">
<td>
--appc_store_dir=VALUE
</td>
@@ -295,7 +295,8 @@ Directory the appc provisioner will store images in.
(default: /tmp/mesos/store/appc)
</td>
</tr>
-<tr>
+
+<tr id="attributes">
<td>
--attributes=VALUE
</td>
@@ -304,7 +305,8 @@ Attributes of the agent machine, in the form:
<code>rack:2</code> or <code>rack:2;u:1</code>
</td>
</tr>
-<tr>
+
+<tr id="authenticate_http_executors">
<td>
--[no-]authenticate_http_executors
</td>
@@ -315,7 +317,8 @@ flag is only available when Mesos is built with SSL support.
(default: false)
</td>
</tr>
-<tr>
+
+<tr id="authenticatee">
<td>
--authenticatee=VALUE
</td>
@@ -325,7 +328,8 @@ master. Use the default <code>crammd5</code>, or
load an alternate authenticatee module using <code>--modules</code>. (default: crammd5)
</td>
</tr>
-<tr>
+
+<tr id="authentication_backoff_factor">
<td>
--authentication_backoff_factor=VALUE
</td>
@@ -339,7 +343,8 @@ retry between <code>[0, b * 2^3]</code>, etc up to a maximum of 1mins
(default: 1secs)
</td>
</tr>
-<tr>
+
+<tr id="authorizer">
<td>
--authorizer=VALUE
</td>
@@ -354,7 +359,8 @@ other than the default <code>local</code>, the ACLs
passed through the <code>--acls</code> flag will be ignored.
</td>
</tr>
-<tr>
+
+<tr id="cgroups_cpu_enable_pids_and_tids_count">
<td>
--[no]-cgroups_cpu_enable_pids_and_tids_count
</td>
@@ -363,7 +369,8 @@ Cgroups feature flag to enable counting of processes and threads
inside a container. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="cgroups_enable_cfs">
<td>
--[no]-cgroups_enable_cfs
</td>
@@ -372,7 +379,8 @@ Cgroups feature flag to enable hard limits on CPU resources
via the CFS bandwidth limiting subfeature. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="cgroups_hierarchy">
<td>
--cgroups_hierarchy=VALUE
</td>
@@ -380,7 +388,8 @@ via the CFS bandwidth limiting subfeature. (default: false)
The path to the cgroups hierarchy root. (default: /sys/fs/cgroup)
</td>
</tr>
-<tr>
+
+<tr id="cgroups_limit_swap">
<td>
--[no]-cgroups_limit_swap
</td>
@@ -389,7 +398,8 @@ Cgroups feature flag to enable memory limits on both memory and
swap instead of just memory. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="cgroups_net_cls_primary_handle">
<td>
--cgroups_net_cls_primary_handle
</td>
@@ -398,7 +408,8 @@ A non-zero, 16-bit handle of the form `0xAAAA`. This will be used as
the primary handle for the net_cls cgroup.
</td>
</tr>
-<tr>
+
+<tr id="cgroups_net_cls_secondary_handles">
<td>
--cgroups_net_cls_secondary_handles
</td>
@@ -408,7 +419,8 @@ handles that can be used with the primary handle. This will take
effect only when the <code>--cgroups_net_cls_primary_handle</code> is set.
</td>
</tr>
-<tr>
+
+<tr id="allowed_devices">
<td>
--allowed_devices
</td>
@@ -450,7 +462,8 @@ Example:
</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="cgroups_root">
<td>
--cgroups_root=VALUE
</td>
@@ -458,7 +471,8 @@ Example:
Name of the root cgroup. (default: mesos)
</td>
</tr>
-<tr>
+
+<tr id="check_agent_port_range_only">
<td>
--[no-]check_agent_port_range_only
</td>
@@ -470,7 +484,8 @@ to only listen on ports for which they have been assigned resources.
(default: false)
</td>
</tr>
-<tr>
+
+<tr id="container_disk_watch_interval">
<td>
--container_disk_watch_interval=VALUE
</td>
@@ -479,7 +494,8 @@ The interval between disk quota checks for containers. This flag is
used for the <code>disk/du</code> isolator. (default: 15secs)
</td>
</tr>
-<tr>
+
+<tr id="container_logger">
<td>
--container_logger=VALUE
</td>
@@ -490,7 +506,8 @@ container logger writes to <code>stdout</code> and <code>stderr</code> files
in the sandbox directory.
</td>
</tr>
-<tr>
+
+<tr id="container_ports_watch_interval">
<td>
--container_ports_watch_interval=VALUE
</td>
@@ -500,7 +517,8 @@ containers listening on ports they don't have resources for.
<td>
</td>
</tr>
-<tr>
+
+<tr id="containerizers">
<td>
--containerizers=VALUE
</td>
@@ -513,7 +531,8 @@ are specified is the order they are tried.
(default: mesos)
</td>
</tr>
-<tr>
+
+<tr id="credential">
<td>
--credential=VALUE
</td>
@@ -528,7 +547,8 @@ Example:
}</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="default_container_dns">
<td>
--default_container_dns=VALUE
</td>
@@ -574,7 +594,8 @@ Example:
}</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="default_container_info">
<td>
--default_container_info=VALUE
</td>
@@ -598,7 +619,8 @@ Example:
}</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="default_role">
<td>
--default_role=VALUE
</td>
@@ -610,7 +632,8 @@ automatically detected, will be assigned to
this role. (default: *)
</td>
</tr>
-<tr>
+
+<tr id="disk_profile_adaptor">
<td>
--disk_profile_adaptor=VALUE
</td>
@@ -623,7 +646,8 @@ resource providers is to only expose resources for pre-existing
volumes and not publish RAW volumes.
</td>
</tr>
-<tr>
+
+<tr id="disk_watch_interval">
<td>
--disk_watch_interval=VALUE
</td>
@@ -634,7 +658,8 @@ This drives the garbage collection of archived
information and sandboxes. (default: 1mins)
</td>
</tr>
-<tr>
+
+<tr id="docker">
<td>
--docker=VALUE
</td>
@@ -644,7 +669,8 @@ containerizer.
(default: docker)
</td>
</tr>
-<tr>
+
+<tr id="docker_config">
<td>
--docker_config=VALUE
</td>
@@ -666,7 +692,8 @@ Example JSON (<code>$HOME/.docker/config.json</code>):
</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="docker_kill_orphans">
<td>
--[no-]docker_kill_orphans
</td>
@@ -678,7 +705,8 @@ removing docker tasks launched by other agents.
(default: true)
</td>
</tr>
-<tr>
+
+<tr id="docker_mesos_image">
<td>
--docker_mesos_image=VALUE
</td>
@@ -690,7 +718,8 @@ docker containers in order to recover them when the agent restarts and
recovers.
</td>
</tr>
-<tr>
+
+<tr id="docker_registry">
<td>
--docker_registry=VALUE
</td>
@@ -703,7 +732,8 @@ that this option won't change the default registry server for Docker
containerizer. (default: https://registry-1.docker.io)
</td>
</tr>
-<tr>
+
+<tr id="docker_remove_delay">
<td>
--docker_remove_delay=VALUE
</td>
@@ -714,7 +744,8 @@ after Mesos regards the container as TERMINATED
This only applies for the Docker Containerizer. (default: 6hrs)
</td>
</tr>
-<tr>
+
+<tr id="docker_socket">
<td>
--docker_socket=VALUE
</td>
@@ -728,7 +759,8 @@ used by the Docker image used to run the agent. (default:
platforms).
</td>
</tr>
-<tr>
+
+<tr id="docker_stop_timeout">
<td>
--docker_stop_timeout=VALUE
</td>
@@ -738,7 +770,8 @@ that container. This flag is deprecated; use task's kill policy instead.
(default: 0ns)
</td>
</tr>
-<tr>
+
+<tr id="docker_store_dir">
<td>
--docker_store_dir=VALUE
</td>
@@ -746,7 +779,8 @@ that container. This flag is deprecated; use task's kill policy instead.
Directory the Docker provisioner will store images in (default: /tmp/mesos/store/docker)
</td>
</tr>
-<tr>
+
+<tr id="docker_volume_checkpoint_dir">
<td>
--docker_volume_checkpoint_dir=VALUE
</td>
@@ -756,7 +790,8 @@ volumes that each container uses.
(default: /var/run/mesos/isolators/docker/volume)
</td>
</tr>
-<tr>
+
+<tr id="enforce_container_disk_quota">
<td>
--[no-]enforce_container_disk_quota
</td>
@@ -765,7 +800,8 @@ Whether to enable disk quota enforcement for containers. This flag
is used by the <code>disk/du</code> and <code>disk/xfs</code> isolators. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="enforce_container_ports">
<td>
--[no-]enforce_container_ports
</td>
@@ -774,7 +810,8 @@ Whether to enable network port enforcement for containers. This flag
is used by the <code>network/ports</code> isolator. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="executor_environment_variables">
<td>
--executor_environment_variables=VALUE
</td>
@@ -789,7 +826,8 @@ Example:
}</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="executor_registration_timeout">
<td>
--executor_registration_timeout=VALUE
</td>
@@ -799,7 +837,8 @@ to register with the agent before considering it hung and
shutting it down (e.g., 60secs, 3mins, etc) (default: 1mins)
</td>
</tr>
-<tr>
+
+<tr id="executor_reregistration_timeout">
<td>
--executor_reregistration_timeout=VALUE
</td>
@@ -810,7 +849,8 @@ it down. Note that currently, the agent will not reregister with the
master until this timeout has elapsed (see MESOS-7539). (default: 2secs)
</td>
</tr>
-<tr>
+
+<tr id="executor_reregistration_retry_interval">
<td>
--executor_reregistration_retry_interval=VALUE
</td>
@@ -835,7 +875,8 @@ This results in "old" executors correctly establishing a link
when processing the second reconnect message. (default: no retries)
</td>
</tr>
-<tr>
+
+<tr id="max_completed_executors_per_framework">
<td>
--max_completed_executors_per_framework=VALUE
</td>
@@ -844,7 +885,8 @@ Maximum number of completed executors per framework to store
in memory. (default: 150)
</td>
</tr>
-<tr>
+
+<tr id="jwt_secret_key">
<td>
--jwt_secret_key=VALUE
</td>
@@ -853,7 +895,8 @@ Path to a file containing the key used when generating JWT secrets.
This flag is only available when Mesos is built with SSL support.
</td>
</tr>
-<tr>
+
+<tr id="executor_shutdown_grace_period">
<td>
--executor_shutdown_grace_period=VALUE
</td>
@@ -867,7 +910,8 @@ terminations may occur.
(default: 5secs)
</td>
</tr>
-<tr>
+
+<tr id="fetcher_cache_dir">
<td>
--fetcher_cache_dir=VALUE
</td>
@@ -886,7 +930,8 @@ for several reasons:
</ul>
</td>
</tr>
-<tr>
+
+<tr id="fetcher_cache_size">
<td>
--fetcher_cache_size=VALUE
</td>
@@ -894,7 +939,8 @@ for several reasons:
Size of the fetcher cache in Bytes. (default: 2GB)
</td>
</tr>
-<tr>
+
+<tr id="fetcher_stall_timeout">
<td>
--fetcher_stall_timeout=VALUE
</td>
@@ -906,7 +952,8 @@ keeps below one byte per second).
does not apply to HDFS. (default: 1mins)
</td>
</tr>
-<tr>
+
+<tr id="frameworks_home">
<td>
--frameworks_home=VALUE
</td>
@@ -914,7 +961,8 @@ does not apply to HDFS. (default: 1mins)
Directory path prepended to relative executor URIs (default: )
</td>
</tr>
-<tr>
+
+<tr id="gc_delay">
<td>
--gc_delay=VALUE
</td>
@@ -925,9 +973,9 @@ Note that this delay may be shorter depending on
the available disk usage. (default: 1weeks)
</td>
</tr>
-<tr>
+
+<tr id="gc_disk_headroom">
<td>
- <a name="gc_disk_headroom"></a>
--gc_disk_headroom=VALUE
</td>
<td>
@@ -938,7 +986,8 @@ every <code>--disk_watch_interval</code> duration. <code>gc_disk_headroom</code>
be a value between 0.0 and 1.0 (default: 0.1)
</td>
</tr>
-<tr>
+
+<tr id="hadoop_home">
<td>
--hadoop_home=VALUE
</td>
@@ -949,7 +998,8 @@ fetching framework executors from HDFS)
environment or find hadoop on <code>PATH</code>) (default: )
</td>
</tr>
-<tr>
+
+<tr id="http_credentials">
<td>
--http_credentials=VALUE
</td>
@@ -970,7 +1020,8 @@ Example:
</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="http_command_executor">
<td>
--[no-]http_command_executor
</td>
@@ -983,7 +1034,8 @@ the driver based implementation would be used.
production yet. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="http_heartbeat_interval">
<td>
--http_heartbeat_interval=VALUE
</td>
@@ -995,7 +1047,8 @@ the agent HTTP API. Currently, this only applies to the
(default: 30secs)
</td>
</tr>
-<tr>
+
+<tr id="image_providers">
<td>
--image_providers=VALUE
</td>
@@ -1004,7 +1057,8 @@ Comma-separated list of supported image providers,
e.g., <code>APPC,DOCKER</code>.
</td>
</tr>
-<tr>
+
+<tr id="image_provisioner_backend">
<td>
--image_provisioner_backend=VALUE
</td>
@@ -1013,7 +1067,8 @@ Strategy for provisioning container rootfs from images, e.g., <code>aufs</code>,
<code>bind</code>, <code>copy</code>, <code>overlay</code>.
</td>
</tr>
-<tr>
+
+<tr id="image_gc_config">
<td>
--image_gc_config=VALUE
</td>
@@ -1040,7 +1095,8 @@ Example:
}</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="ip6">
<td>
--ip6=VALUE
</td>
@@ -1053,7 +1109,8 @@ this IPv6 address is only used to advertise IPv6 addresses for
containers running on the host network.
</td>
</tr>
-<tr>
+
+<tr id="ip6_discovery_command">
<td>
--ip6_discovery_command=VALUE
</td>
@@ -1067,7 +1124,8 @@ this IPv6 address is only used to advertise IPv6 addresses for
containers running on the host network.
</td>
</tr>
-<tr>
+
+<tr id="isolation">
<td>
--isolation=VALUE
</td>
@@ -1081,7 +1139,8 @@ flag is only relevant for the Mesos Containerizer.
(default: posix/cpu,posix/mem)
</td>
</tr>
-<tr>
+
+<tr id="launcher">
<td>
--launcher=VALUE
</td>
@@ -1093,7 +1152,8 @@ network, pid, etc. If unspecified, the agent will choose the Linux
launcher if it's running as root on Linux.
</td>
</tr>
-<tr>
+
+<tr id="launcher_dir">
<td>
--launcher_dir=VALUE
</td>
@@ -1103,7 +1163,8 @@ fetcher, containerizer, and executor binary files under this
directory. (default: /usr/local/libexec/mesos)
</td>
</tr>
-<tr>
+
+<tr id="master_detector">
<td>
--master_detector=VALUE
</td>
@@ -1113,7 +1174,8 @@ module specified through the <code>--modules</code> flag. Cannot be used in
conjunction with <code>--master</code>.
</td>
</tr>
-<tr>
+
+<tr id="nvidia_gpu_devices">
<td>
--nvidia_gpu_devices=VALUE
</td>
@@ -1127,7 +1189,8 @@ listed will only be isolated if the <code>--isolation</code> flag contains the
string <code>gpu/nvidia</code>.
</td>
</tr>
-<tr>
+
+<tr id="network_cni_plugins_dir">
<td>
--network_cni_plugins_dir=VALUE
</td>
@@ -1138,7 +1201,8 @@ the plugins to add/delete container from the CNI networks. It is the operator's
responsibility to install the CNI plugin binaries in the specified directory.
</td>
</tr>
-<tr>
+
+<tr id="network_cni_config_dir">
<td>
--network_cni_config_dir=VALUE
</td>
@@ -1148,7 +1212,8 @@ containers launched in Mesos agent can connect to, the operator should install
a network configuration file in JSON format in the specified directory.
</td>
</tr>
-<tr>
+
+<tr id="oversubscribed_resources_interval">
<td>
--oversubscribed_resources_interval=VALUE
</td>
@@ -1159,7 +1224,8 @@ and available. The interval between updates is controlled by this flag.
(default: 15secs)
</td>
</tr>
-<tr>
+
+<tr id="perf_duration">
<td>
--perf_duration=VALUE
</td>
@@ -1168,7 +1234,8 @@ Duration of a perf stat sample. The duration must be less
than the <code>perf_interval</code>. (default: 10secs)
</td>
</tr>
-<tr>
+
+<tr id="perf_events">
<td>
--perf_events=VALUE
</td>
@@ -1181,7 +1248,8 @@ when reported in the PerfStatistics protobuf, e.g., <code>cpu-cycles</code>
becomes <code>cpu_cycles</code>; see the PerfStatistics protobuf for all names.
</td>
</tr>
-<tr>
+
+<tr id="perf_interval">
<td>
--perf_interval=VALUE
</td>
@@ -1193,7 +1261,8 @@ demand. For this reason, <code>perf_interval</code> is independent of the
resource monitoring interval. (default: 60secs)
</td>
</tr>
-<tr>
+
+<tr id="qos_controller">
<td>
--qos_controller=VALUE
</td>
@@ -1201,7 +1270,8 @@ resource monitoring interval. (default: 60secs)
The name of the QoS Controller to use for oversubscription.
</td>
</tr>
-<tr>
+
+<tr id="qos_correction_interval_min">
<td>
--qos_correction_interval_min=VALUE
</td>
@@ -1212,7 +1282,8 @@ The smallest interval between these corrections is controlled by
this flag. (default: 0secs)
</td>
</tr>
-<tr>
+
+<tr id="reconfiguration_policy">
<td>
--reconfiguration_policy=VALUE
</td>
@@ -1230,7 +1301,8 @@ considers unacceptable, which, e.g., currently happens when port or hostname
are changed. (default: equal)
</td>
</tr>
-<tr>
+
+<tr id="recover">
<td>
--recover=VALUE
</td>
@@ -1243,7 +1315,8 @@ cleanup : Kill any old live executors and exit.
or executor upgrade!). (default: reconnect)
</td>
</tr>
-<tr>
+
+<tr id="recovery_timeout">
<td>
--recovery_timeout=VALUE
</td>
@@ -1254,7 +1327,8 @@ waiting to reconnect to the agent will self-terminate.
(default: 15mins)
</td>
</tr>
-<tr>
+
+<tr id="registration_backoff_factor">
<td>
--registration_backoff_factor=VALUE
</td>
@@ -1267,7 +1341,8 @@ interval (e.g., 1st retry uses a random value between <code>[0, b * 2^1]</code>,
etc) up to a maximum of 1mins (default: 1secs)
</td>
</tr>
-<tr>
+
+<tr id="resource_estimator">
<td>
--resource_estimator=VALUE
</td>
@@ -1275,7 +1350,8 @@ etc) up to a maximum of 1mins (default: 1secs)
The name of the resource estimator to use for oversubscription.
</td>
</tr>
-<tr>
+
+<tr id="resources">
<td>
--resources=VALUE
</td>
@@ -1311,7 +1387,8 @@ Example JSON:
]</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="resource_provider_config_dir">
<td>
--resource_provider_config_dir=VALUE
</td>
@@ -1332,7 +1409,8 @@ Example config file in this directory:
}</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="revocable_cpu_low_priority">
<td>
--[no-]revocable_cpu_low_priority
</td>
@@ -1342,7 +1420,8 @@ normal containers (non-revocable cpu). Currently only
supported by the cgroups/cpu isolator. (default: true)
</td>
</tr>
-<tr>
+
+<tr id="runtime_dir">
<td>
--runtime_dir
</td>
@@ -1353,7 +1432,8 @@ not across reboots). This directory will be cleared on reboot.
(Example: <code>/var/run/mesos</code>)
</td>
</tr>
-<tr>
+
+<tr id="sandbox_directory">
<td>
--sandbox_directory=VALUE
</td>
@@ -1363,7 +1443,8 @@ sandbox is mapped to.
(default: /mnt/mesos/sandbox)
</td>
</tr>
-<tr>
+
+<tr id="disallow_sharing_agent_pid_namespace">
<td>
--[no-]disallow_sharing_agent_pid_namespace
</td>
@@ -1377,7 +1458,8 @@ agent if the framework requests it. This flag will be ignored if the
(default: false)
</td>
</tr>
-<tr>
+
+<tr id="strict">
<td>
--[no-]strict
</td>
@@ -1390,7 +1472,8 @@ state as possible is recovered.
(default: true)
</td>
</tr>
-<tr>
+
+<tr id="secret_resolver">
<td>
--secret_resolver=VALUE
</td>
@@ -1402,7 +1485,7 @@ reference-based secrets.
</td>
</tr>
-<tr>
+<tr id="switch_user">
<td>
--[no-]switch_user
</td>
@@ -1457,7 +1540,8 @@ The path to the systemd system run time directory.
</th>
</tr>
</thead>
-<tr>
+
+<tr id="ephemeral_ports_per_container">
<td>
--ephemeral_ports_per_container=VALUE
</td>
@@ -1467,7 +1551,8 @@ isolator. This number has to be a power of 2. This flag is used
for the <code>network/port_mapping</code> isolator. (default: 1024)
</td>
</tr>
-<tr>
+
+<tr id="eth0_name">
<td>
--eth0_name=VALUE
</td>
@@ -1478,7 +1563,8 @@ on the host default gateway. This flag is used for the
<code>network/port_mapping</code> isolator.
</td>
</tr>
-<tr>
+
+<tr id="lo_name">
<td>
--lo_name=VALUE
</td>
@@ -1488,7 +1574,8 @@ not specified, the network isolator will try to guess it. This
flag is used for the <code>network/port_mapping</code> isolator.
</td>
</tr>
-<tr>
+
+<tr id="egress_rate_limit_per_container">
<td>
--egress_rate_limit_per_container=VALUE
</td>
@@ -1500,7 +1587,8 @@ This flag uses the Bytes type (defined in stout) and is used for
the <code>network/port_mapping</code> isolator.
</td>
</tr>
-<tr>
+
+<tr id="egress_unique_flow_per_container">
<td>
--[no-]egress_unique_flow_per_container
</td>
@@ -1510,7 +1598,8 @@ egress traffic. This flag is used for the <code>network/port_mapping</code>
isolator. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="egress_flow_classifier_parent">
<td>
--egress_flow_classifier_parent=VALUE
</td>
@@ -1520,7 +1609,8 @@ a flow classifier (fq_codel) qdisc on egress side. This flag specifies
where to install it in the hierarchy. By default, we install it at root.
</td>
</tr>
-<tr>
+
+<tr id="network_enable_socket_statistics_summary">
<td>
--[no-]network_enable_socket_statistics_summary
</td>
@@ -1530,7 +1620,8 @@ This flag is used for the <code>network/port_mapping</code> isolator.
(default: false)
</td>
</tr>
-<tr>
+
+<tr id="network_enable_socket_statistics_details">
<td>
--[no-]network_enable_socket_statistics_details
</td>
@@ -1540,7 +1631,8 @@ each container. This flag is used for the <code>network/port_mapping</code>
isolator. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="network_enable_snmp_statistics">
<td>
--[no-]network_enable_snmp_statistics
</td>
@@ -1550,6 +1642,7 @@ each container. This flag is used for the 'network/port_mapping'
isolator. (default: false)
</td>
</tr>
+
</table>
@@ -1568,7 +1661,8 @@ isolator. (default: false)
</th>
</tr>
</thead>
-<tr>
+
+<tr id="xfs_project_range">
<td>
--xfs_project_range=VALUE
</td>
@@ -1578,6 +1672,7 @@ quotas for container sandbox directories. Valid project IDs range from
1 to max(uint32). (default `[5000-10000]`)
</td>
</tr>
+
</table>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/85919a82/content/documentation/latest/configuration/master-and-agent/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/configuration/master-and-agent/index.html b/content/documentation/latest/configuration/master-and-agent/index.html
index 3a64fb8..3b2ec04 100644
--- a/content/documentation/latest/configuration/master-and-agent/index.html
+++ b/content/documentation/latest/configuration/master-and-agent/index.html
@@ -122,7 +122,8 @@
</th>
</tr>
</thead>
-<tr>
+
+<tr id="advertise_ip">
<td>
--advertise_ip=VALUE
</td>
@@ -132,7 +133,8 @@ The master/agent does not bind to this IP address.
However, this IP address may be used to access this master/agent.
</td>
</tr>
-<tr>
+
+<tr id="advertise_port">
<td>
--advertise_port=VALUE
</td>
@@ -143,7 +145,8 @@ However, this port (along with <code>advertise_ip</code>) may be used to
access Mesos master/agent.
</td>
</tr>
-<tr>
+
+<tr id="authenticate_http_readonly">
<td>
--[no-]authenticate_http_readonly
</td>
@@ -153,7 +156,8 @@ supporting authentication are allowed. If <code>false</code>, unauthenticated
requests to such HTTP endpoints are also allowed.
</td>
</tr>
-<tr>
+
+<tr id="authenticate_http_readwrite">
<td>
--[no-]authenticate_http_readwrite
</td>
@@ -163,7 +167,8 @@ supporting authentication are allowed. If <code>false</code>, unauthenticated
requests to such HTTP endpoints are also allowed.
</td>
</tr>
-<tr>
+
+<tr id="firewall_rules">
<td>
--firewall_rules=VALUE
</td>
@@ -186,7 +191,8 @@ Example:
}</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="domain">
<td>
--domain=VALUE
</td>
@@ -219,7 +225,8 @@ Example:
}</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="help">
<td>
--[no-]help
</td>
@@ -227,7 +234,8 @@ Example:
Show the help message and exit. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="hooks">
<td>
--hooks=VALUE
</td>
@@ -235,7 +243,8 @@ Show the help message and exit. (default: false)
A comma-separated list of hook modules to be installed inside master/agent.
</td>
</tr>
-<tr>
+
+<tr id="hostname">
<td>
--hostname=VALUE
</td>
@@ -248,7 +257,8 @@ that, using <code>--no-hostname_lookup</code>, in which case the IP itself
is used.
</td>
</tr>
-<tr>
+
+<tr id="hostname_lookup">
<td>
--[no-]hostname_lookup
</td>
@@ -259,7 +269,8 @@ True by default; if set to <code>false</code> it will cause Mesos
to use the IP address, unless the hostname is explicitly set. (default: true)
</td>
</tr>
-<tr>
+
+<tr id="http_authenticators">
<td>
--http_authenticators=VALUE
</td>
@@ -270,7 +281,8 @@ alternate HTTP authenticator module using <code>--modules</code>.
(default: basic, or basic and JWT if executor authentication is enabled)
</td>
</tr>
-<tr>
+
+<tr id="ip">
<td>
--ip=VALUE
</td>
@@ -279,7 +291,8 @@ IP address to listen on. This cannot be used in conjunction
with <code>--ip_discovery_command</code>.
</td>
</tr>
-<tr>
+
+<tr id="ip_discovery_command">
<td>
--ip_discovery_command=VALUE
</td>
@@ -289,7 +302,8 @@ the IP address which the master/agent will try to bind to.
Cannot be used in conjunction with <code>--ip</code>.
</td>
</tr>
-<tr>
+
+<tr id="modules">
<td>
--modules=VALUE
</td>
@@ -336,7 +350,8 @@ Example:
<p/> Cannot be used in conjunction with --modules_dir.
</td>
</tr>
-<tr>
+
+<tr id="modules_dir">
<td>
--modules_dir=VALUE
</td>
@@ -346,7 +361,8 @@ alphabetical order. (See <code>--modules</code> for more information on module
manifest files). Cannot be used in conjunction with <code>--modules</code>.
</td>
</tr>
-<tr>
+
+<tr id="port">
<td>
--port=VALUE
</td>
@@ -354,7 +370,8 @@ manifest files). Cannot be used in conjunction with <code>--modules</code>.
Port to listen on. (master default: 5050; agent default: 5051)
</td>
</tr>
-<tr>
+
+<tr id="version">
<td>
--[no-]version
</td>
@@ -362,7 +379,8 @@ Port to listen on. (master default: 5050; agent default: 5051)
Show version and exit. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="zk_session_timeout">
<td>
--zk_session_timeout=VALUE
</td>
@@ -370,6 +388,7 @@ Show version and exit. (default: false)
ZooKeeper session timeout. (default: 10secs)
</td>
</tr>
+
</table>
@@ -389,7 +408,8 @@ For more about logging, see the <a href="/documentation/latest/configuration/../
</th>
</tr>
</thead>
-<tr>
+
+<tr id="quiet">
<td>
--[no-]quiet
</td>
@@ -397,7 +417,8 @@ For more about logging, see the <a href="/documentation/latest/configuration/../
Disable logging to stderr. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="log_dir">
<td>
--log_dir=VALUE
</td>
@@ -409,7 +430,8 @@ If specified, the log file will appear in the Mesos WebUI.
only written to stderr!
</td>
</tr>
-<tr>
+
+<tr id="logbufsecs">
<td>
--logbufsecs=VALUE
</td>
@@ -418,7 +440,8 @@ Maximum number of seconds that logs may be buffered for.
By default, logs are flushed immediately. (default: 0)
</td>
</tr>
-<tr>
+
+<tr id="logging_level">
<td>
--logging_level=VALUE
</td>
@@ -429,7 +452,8 @@ If <code>--quiet</code> is specified, this will only affect the logs
written to <code>--log_dir</code>, if specified. (default: INFO)
</td>
</tr>
-<tr>
+
+<tr id="initialize_driver_logging">
<td>
--[no-]initialize_driver_logging
</td>
@@ -443,7 +467,8 @@ This option has no effect when using the HTTP scheduler/executor APIs.
(default: true)
</td>
</tr>
-<tr>
+
+<tr id="external_log_file">
<td>
--external_log_file=VALUE
</td>
@@ -460,6 +485,7 @@ However, logs will still be written to the <code>--log_dir</code> if
that option is specified.
</td>
</tr>
+
</table>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/85919a82/content/documentation/latest/configuration/master/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/configuration/master/index.html b/content/documentation/latest/configuration/master/index.html
index 5967b27..abd3567 100644
--- a/content/documentation/latest/configuration/master/index.html
+++ b/content/documentation/latest/configuration/master/index.html
@@ -122,7 +122,8 @@
</th>
</tr>
</thead>
-<tr>
+
+<tr id="quorum">
<td>
--quorum=VALUE
</td>
@@ -133,7 +134,8 @@ masters i.e., <code>quorum > (number of masters)/2</code>.
<b>NOTE</b>: Not required if master is run in standalone mode (non-HA).
</td>
</tr>
-<tr>
+
+<tr id="work_dir">
<td>
--work_dir=VALUE
</td>
@@ -145,7 +147,8 @@ directory when running in production, since long-running masters could
lose data when cleanup occurs. (Example: <code>/var/lib/mesos/master</code>)
</td>
</tr>
-<tr>
+
+<tr id="zk">
<td>
--zk=VALUE
</td>
@@ -158,6 +161,7 @@ file:///path/to/file (where file contains one of the above)</code></pre>
<b>NOTE</b>: Not required if master is run in standalone mode (non-HA).
</td>
</tr>
+
</table>
@@ -174,7 +178,8 @@ file:///path/to/file (where file contains one of the above)</code></pre>
</th>
</tr>
</thead>
-<tr>
+
+<tr id="acls">
<td>
--acls=VALUE
</td>
@@ -231,7 +236,8 @@ Example:
}</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="agent_ping_timeout">
<td>
--agent_ping_timeout=VALUE,
<p/>
@@ -247,7 +253,8 @@ session timeout to prevent useless re-registration attempts.
(default: 15secs)
</td>
</tr>
-<tr>
+
+<tr id="agent_removal_rate_limit">
<td>
--agent_removal_rate_limit=VALUE
<p/>
@@ -260,7 +267,8 @@ By default, agents will be removed as soon as they fail the health
checks. The value is of the form <code>(Number of agents)/(Duration)</code>.
</td>
</tr>
-<tr>
+
+<tr id="agent_reregister_timeout">
<td>
--agent_reregister_timeout=VALUE
<p/>
@@ -276,7 +284,8 @@ non-partition-aware tasks running on the agent will be terminated.
<b>NOTE</b>: This value has to be at least 10mins. (default: 10mins)
</td>
</tr>
-<tr>
+
+<tr id="allocation_interval">
<td>
--allocation_interval=VALUE
</td>
@@ -285,7 +294,8 @@ Amount of time to wait between performing
(batch) allocations (e.g., 500ms, 1sec, etc). (default: 1secs)
</td>
</tr>
-<tr>
+
+<tr id="allocator">
<td>
--allocator=VALUE
</td>
@@ -296,7 +306,8 @@ load an alternate allocator module using <code>--modules</code>.
(default: HierarchicalDRF)
</td>
</tr>
-<tr>
+
+<tr id="authenticate_agents">
<td>
--[no-]authenticate_agents,
<p/>
@@ -307,7 +318,8 @@ If <code>true</code> only authenticated agents are allowed to register.
If <code>false</code> unauthenticated agents are also allowed to register. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="authenticate_frameworks">
<td>
--[no-]authenticate_frameworks,
<p/>
@@ -319,7 +331,8 @@ If <code>true</code>, only authenticated frameworks are allowed to register. If
HTTP based frameworks use the <code>--authenticate_http_frameworks</code> flag. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="authenticate_http_frameworks">
<td>
--[no-]authenticate_http_frameworks
</td>
@@ -328,7 +341,8 @@ If <code>true</code>, only authenticated HTTP based frameworks are allowed to
register. If <code>false</code>, HTTP frameworks are not authenticated. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="authenticators">
<td>
--authenticators=VALUE
</td>
@@ -338,7 +352,8 @@ and/or agents. Use the default <code>crammd5</code>, or
load an alternate authenticator module using <code>--modules</code>. (default: crammd5)
</td>
</tr>
-<tr>
+
+<tr id="authorizers">
<td>
--authorizers=VALUE
</td>
@@ -355,7 +370,8 @@ passed through the <code>--acls</code> flag will be ignored.
Currently there is no support for multiple authorizers. (default: local)
</td>
</tr>
-<tr>
+
+<tr id="cluster">
<td>
--cluster=VALUE
</td>
@@ -363,7 +379,8 @@ Currently there is no support for multiple authorizers. (default: local)
Human readable name for the cluster, displayed in the webui.
</td>
</tr>
-<tr>
+
+<tr id="credentials">
<td>
--credentials=VALUE
</td>
@@ -381,7 +398,8 @@ Example:
}</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="fair_sharing_excluded_resource_names">
<td>
--fair_sharing_excluded_resource_names=VALUE
</td>
@@ -394,7 +412,8 @@ sharing implementation currently has limitations. E.g. See the problem of
<a href="https://issues.apache.org/jira/browse/MESOS-5377">MESOS-5377</a>
</td>
</tr>
-<tr>
+
+<tr id="filter_gpu_resources">
<td>
--[no_]filter_gpu_resources
</td>
@@ -411,7 +430,8 @@ the following for more information:
<a href="https://issues.apache.org/jira/browse/MESOS-7576">MESOS-7576</a>
</td>
</tr>
-<tr>
+
+<tr id="framework_sorter">
<td>
--framework_sorter=VALUE
</td>
@@ -421,7 +441,8 @@ frameworks. Options are the same as for <code>--user_sorter</code>.
(default: drf)
</td>
</tr>
-<tr>
+
+<tr id="http_framework_authenticators">
<td>
--http_framework_authenticators=VALUE
</td>
@@ -434,7 +455,8 @@ module using <code>--modules</code>. This must be used in conjunction with
Currently there is no support for multiple HTTP authenticators.
</td>
</tr>
-<tr>
+
+<tr id="log_auto_initialize">
<td>
--[no-]log_auto_initialize
</td>
@@ -444,7 +466,8 @@ used for the registry. If this is set to false, the log has to be manually
initialized when used for the very first time. (default: true)
</td>
</tr>
-<tr>
+
+<tr id="master_contender">
<td>
--master_contender=VALUE
</td>
@@ -455,7 +478,8 @@ conjunction with <code>--zk</code>. Must be used in conjunction with
<code>--master_detector</code>.
</td>
</tr>
-<tr>
+
+<tr id="master_detector">
<td>
--master_detector=VALUE
</td>
@@ -466,7 +490,8 @@ conjunction with <code>--zk</code>. Must be used in conjunction with
<code>--master_contender</code>.
</td>
</tr>
-<tr>
+
+<tr id="max_agent_ping_timeouts">
<td>
--max_agent_ping_timeouts=VALUE,
<p/>
@@ -479,7 +504,8 @@ ping from the master. Agents that do not respond within
(default: 5)
</td>
</tr>
-<tr>
+
+<tr id="max_completed_frameworks">
<td>
--max_completed_frameworks=VALUE
</td>
@@ -487,7 +513,8 @@ ping from the master. Agents that do not respond within
Maximum number of completed frameworks to store in memory. (default: 50)
</td>
</tr>
-<tr>
+
+<tr id="max_completed_tasks_per_framework">
<td>
--max_completed_tasks_per_framework=VALUE
</td>
@@ -495,7 +522,8 @@ Maximum number of completed frameworks to store in memory. (default: 50)
Maximum number of completed tasks per framework to store in memory. (default: 1000)
</td>
</tr>
-<tr>
+
+<tr id="max_unreachable_tasks_per_framework">
<td>
--max_unreachable_tasks_per_framework=VALUE
</td>
@@ -503,7 +531,8 @@ Maximum number of completed tasks per framework to store in memory. (default: 10
Maximum number of unreachable tasks per framework to store in memory. (default: 1000)
</td>
</tr>
-<tr>
+
+<tr id="offer_timeout">
<td>
--offer_timeout=VALUE
</td>
@@ -514,7 +543,8 @@ or frameworks that accidentally drop offers.
If not set, offers do not timeout.
</td>
</tr>
-<tr>
+
+<tr id="rate_limits">
<td>
--rate_limits=VALUE
</td>
@@ -542,7 +572,8 @@ Example:
}</code></pre>
</td>
</tr>
-<tr>
+
+<tr id="recovery_agent_removal_limit">
<td>
--recovery_agent_removal_limit=VALUE,
<p/>
@@ -563,7 +594,8 @@ in the cluster.
Values: [0%-100%] (default: 100%)
</td>
</tr>
-<tr>
+
+<tr id="registry">
<td>
--registry=VALUE
</td>
@@ -572,7 +604,8 @@ Persistence strategy for the registry; available options are
<code>replicated_log</code>, <code>in_memory</code> (for testing). (default: replicated_log)
</td>
</tr>
-<tr>
+
+<tr id="registry_fetch_timeout">
<td>
--registry_fetch_timeout=VALUE
</td>
@@ -581,7 +614,8 @@ Duration of time to wait in order to fetch data from the registry
after which the operation is considered a failure. (default: 1mins)
</td>
</tr>
-<tr>
+
+<tr id="registry_gc_interval">
<td>
--registry_gc_interval=VALUE
</td>
@@ -595,7 +629,8 @@ how often the master will examine the registry to see if data
should be discarded. (default: 15mins)
</td>
</tr>
-<tr>
+
+<tr id="registry_max_agent_age">
<td>
--registry_max_agent_age=VALUE
</td>
@@ -610,7 +645,8 @@ information may be discarded from the registry sooner than indicated
by this parameter. (default: 2weeks)
</td>
</tr>
-<tr>
+
+<tr id="registry_max_agent_count">
<td>
--registry_max_agent_count=VALUE
</td>
@@ -622,7 +658,8 @@ information about all connected agents. See also the
<code>registry_max_agent_age</code> flag. (default: 102400)
</td>
</tr>
-<tr>
+
+<tr id="registry_store_timeout">
<td>
--registry_store_timeout=VALUE
</td>
@@ -631,7 +668,8 @@ Duration of time to wait in order to store data in the registry
after which the operation is considered a failure. (default: 20secs)
</td>
</tr>
-<tr>
+
+<tr id="require_agent_domain">
<td>
--[no-]require_agent_domain
</td>
@@ -639,7 +677,8 @@ after which the operation is considered a failure. (default: 20secs)
If true, only agents with a configured domain can register. (default: false)
</td>
</tr>
-<tr>
+
+<tr id="roles">
<td>
--roles=VALUE
</td>
@@ -649,7 +688,8 @@ in this cluster may belong to. This flag is deprecated;
if it is not specified, any role name can be used.
</td>
</tr>
-<tr>
+
+<tr id="root_submissions">
<td>
--[no-]root_submissions
</td>
@@ -657,7 +697,8 @@ if it is not specified, any role name can be used.
Can root submit frameworks? (default: true)
</td>
</tr>
-<tr>
+
+<tr id="user_sorter">
<td>
--user_sorter=VALUE
</td>
@@ -666,7 +707,8 @@ Policy to use for allocating resources between users. May be one of:
dominant_resource_fairness (drf) (default: drf)
</td>
</tr>
-<tr>
+
+<tr id="webui_dir">
<td>
--webui_dir=VALUE
</td>
@@ -674,7 +716,8 @@ Policy to use for allocating resources between users. May be one of:
Directory path of the webui files/assets (default: /usr/local/share/mesos/webui)
</td>
</tr>
-<tr>
+
+<tr id="weights">
<td>
--weights=VALUE
</td>
@@ -686,7 +729,8 @@ flag is deprecated. Instead, operators should configure weights dynamically
using the <code>/weights</code> HTTP endpoint.
</td>
</tr>
-<tr>
+
+<tr id="whitelist">
<td>
--whitelist=VALUE
</td>
@@ -698,6 +742,7 @@ machines are accepted. Path can be of the form
<code>file:///path/to/file</code> or <code>/path/to/file</code>.
</td>
</tr>
+
</table>
@@ -716,7 +761,8 @@ machines are accepted. Path can be of the form
</th>
</tr>
</thead>
-<tr>
+
+<tr id="max_executors_per_agent">
<td>
--max_executors_per_agent=VALUE,
<p/>
@@ -729,6 +775,7 @@ acquisition on each executor (# ephemeral ports), as a result
one can only run a certain number of executors on each agent.
</td>
</tr>
+
</table>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/85919a82/content/documentation/latest/isolators/linux-devices/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/isolators/linux-devices/index.html b/content/documentation/latest/isolators/linux-devices/index.html
new file mode 100644
index 0000000..9f5da39
--- /dev/null
+++ b/content/documentation/latest/isolators/linux-devices/index.html
@@ -0,0 +1,198 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <meta charset="utf-8">
+ <title>Apache Mesos - Linux Devices Isolator in Mesos Containerizer</title>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <meta property="og:locale" content="en_US"/>
+ <meta property="og:type" content="website"/>
+ <meta property="og:title" content="Apache Mesos"/>
+ <meta property="og:site_name" content="Apache Mesos"/>
+ <meta property="og:url" content="http://mesos.apache.org/"/>
+ <meta property="og:image" content="http://mesos.apache.org/assets/img/mesos_logo_fb_preview.png"/>
+ <meta property="og:description"
+ content="Apache Mesos abstracts resources away from machines,
+ enabling fault-tolerant and elastic distributed systems
+ to easily be built and run effectively."/>
+
+ <meta name="twitter:card" content="summary"/>
+ <meta name="twitter:site" content="@ApacheMesos"/>
+ <meta name="twitter:title" content="Apache Mesos"/>
+ <meta name="twitter:image" content="http://mesos.apache.org/assets/img/mesos_logo_fb_preview.png"/>
+ <meta name="twitter:description"
+ content="Apache Mesos abstracts resources away from machines,
+ enabling fault-tolerant and elastic distributed systems
+ to easily be built and run effectively."/>
+
+ <link href="//netdna.bootstrapcdn.com/bootstrap/3.1.1/css/bootstrap.min.css" rel="stylesheet">
+ <link rel="alternate" type="application/atom+xml" title="Apache Mesos Blog" href="/blog/feed.xml">
+ <link href="../../../../assets/css/main.css" rel="stylesheet" />
+
+
+ <!-- Google Analytics Magic -->
+ <script type="text/javascript">
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-20226872-1']);
+ _gaq.push(['_setDomainName', 'apache.org']);
+ _gaq.push(['_trackPageview']);
+
+ (function() {
+ var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+ })();
+ </script>
+ </head>
+ <body>
+ <!-- magical breadcrumbs -->
+ <div class="topnav">
+ <div class="container">
+ <ul class="breadcrumb">
+ <li>
+ <div class="dropdown">
+ <a data-toggle="dropdown" href="#">Apache Software Foundation <span class="caret"></span></a>
+ <ul class="dropdown-menu" role="menu" aria-labelledby="dLabel">
+ <li><a href="http://www.apache.org">Apache Homepage</a></li>
+ <li><a href="http://www.apache.org/licenses/">License</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+ <li><a href="http://www.apache.org/security/">Security</a></li>
+ </ul>
+ </div>
+ </li>
+
+ <li><a href="http://mesos.apache.org">Apache Mesos</a></li>
+ <li><a href="/documentation
+/">Documentation
+</a></li>
+ </ul><!-- /.breadcrumb -->
+ </div><!-- /.container -->
+ </div><!-- /.topnav -->
+
+ <!-- navbar excitement -->
+<div class="navbar navbar-default navbar-static-top" role="navigation">
+ <div class="container">
+ <div class="navbar-header">
+ <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#mesos-menu" aria-expanded="false">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+ <a class="navbar-brand" href="/"><img src="/assets/img/mesos_logo.png" alt="Apache Mesos logo"/></a>
+ </div><!-- /.navbar-header -->
+
+ <div class="navbar-collapse collapse" id="mesos-menu">
+ <ul class="nav navbar-nav navbar-right">
+ <li><a href="/getting-started/">Getting Started</a></li>
+ <li><a href="/blog/">Blog</a></li>
+ <li><a href="/documentation/latest/">Documentation</a></li>
+ <li><a href="/downloads/">Downloads</a></li>
+ <li><a href="/community/">Community</a></li>
+ </ul>
+ </div><!-- /#mesos-menu -->
+ </div><!-- /.container -->
+</div><!-- /.navbar -->
+
+<div class="content">
+ <div class="container">
+ <div class="row-fluid">
+ <div class="col-md-4">
+ <h4>If you're new to Mesos</h4>
+ <p>See the <a href="/getting-started/">getting started</a> page for more
+ information about downloading, building, and deploying Mesos.</p>
+
+ <h4>If you'd like to get involved or you're looking for support</h4>
+ <p>See our <a href="/community/">community</a> page for more details.</p>
+ </div>
+ <div class="col-md-8">
+ <h1>Linux Devices in Mesos Containerizer</h1>
+
+<p>While the <code>cgroups/devices</code> isolator allows operators to control
+container access to host devices, the container might still need
+additional privileges to create a device node to actually use the
+device. The <code>linux/devices</code> isolator ensures that containers that
+are granted access to host devices are populated with the the correct
+set of device nodes. Access to host devices is granted by using the
+<a href="/documentation/latest/isolators/../configuration/agent/#allowed_devices"><code>--allowed_devices</code></a> flag
+on the agent.</p>
+
+<p>To enable the <code>linux/devices</code> isolator, append <code>linux/devices</code> to the
+<a href="/documentation/latest/isolators/../configuration/agent/#isolation"><code>--isolation</code></a> flag when starting
+the Mesos agent.</p>
+
+<h2>Security Considerations</h2>
+
+<p>Device access is configured at container
+granularity. For example, this means that if the
+<a href="/documentation/latest/isolators/../configuration/agent/#allowed_devices"><code>--allowed_devices</code></a> flag
+specifies read access for a device, then every process in the container
+will be able to read from the specified device.</p>
+
+<p>The <code>linux/devices</code> isolator does not require the
+<a href="/documentation/latest/isolators/../configuration/agent/#allowed_devices"><code>--allowed_devices</code></a> entry
+to grant <code>mknod</code> access, since it creates device nodes from outside
+the container.</p>
+
+ </div>
+</div>
+
+ </div><!-- /.container -->
+</div><!-- /.content -->
+
+<hr>
+
+
+
+ <!-- footer -->
+ <div class="footer">
+ <div class="container">
+
+ <div class="col-md-3">
+ <a href="https://www.apache.org/events/current-event.html">
+ <img src="https://www.apache.org/events/current-event-234x60.png"/>
+ </a>
+ </div>
+
+ <div class="col-md-3 social-blk">
+ <span class="social">
+ <a href="https://twitter.com/ApacheMesos"
+ class="twitter-follow-button"
+ data-show-count="false" data-size="large">Follow @ApacheMesos</a>
+ <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script>
+ <a href="https://twitter.com/intent/tweet?button_hashtag=mesos"
+ class="twitter-hashtag-button"
+ data-size="large"
+ data-related="ApacheMesos">Tweet #mesos</a>
+ <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script>
+ </span>
+ </div>
+
+ <div class="col-md-6 trademark">
+ <p>© 2012-2018 <a href="http://apache.org">The Apache Software Foundation</a>.
+ Apache Mesos, the Apache feather logo, and the Apache Mesos project logo are trademarks of The Apache Software Foundation.
+ <p>
+ </div>
+
+ </div><!-- /.container -->
+ </div><!-- /.footer -->
+
+ <!-- JS -->
+ <script src="//code.jquery.com/jquery-1.11.0.min.js"></script>
+ <script src="//netdna.bootstrapcdn.com/bootstrap/3.1.1/js/bootstrap.min.js"></script>
+ <script src="//cdnjs.cloudflare.com/ajax/libs/anchor-js/4.1.0/anchor.min.js"></script>
+
+ <!-- Inject anchors for all headings on the page, see https://www.bryanbraun.com/anchorjs. -->
+ <script type="text/javascript">
+ anchors.options = {
+ placement: 'right',
+ ariaLabel: 'Permalink',
+ };
+
+ // The default is to not add anchors to h1, but we have pages with multiple h1 headers,
+ // and we do want to put anchors on those.
+ anchors.add('h1, h2, h3, h4, h5, h6');
+ </script>
+ </body>
+</html>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/85919a82/content/documentation/latest/mesos-containerizer/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/mesos-containerizer/index.html b/content/documentation/latest/mesos-containerizer/index.html
index 8705f52..a2ded3f 100644
--- a/content/documentation/latest/mesos-containerizer/index.html
+++ b/content/documentation/latest/mesos-containerizer/index.html
@@ -153,6 +153,7 @@ can write modules that implement custom isolators.</p>
<li>filesystem/windows</li>
<li><a href="/documentation/latest/./gpu-support/">gpu/nvidia</a></li>
<li><a href="/documentation/latest/./isolators/linux-capabilities/">linux/capabilities</a></li>
+<li><a href="/documentation/latest/./isolators/linux-devices/">linux/devices</a></li>
<li><a href="/documentation/latest/./isolators/namespaces-ipc/">namespaces/ipc</a></li>
<li><a href="/documentation/latest/./isolators/namespaces-pid/">namespaces/pid</a></li>
<li><a href="/documentation/latest/./cni/">network/cni</a></li>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/85919a82/content/documentation/latest/upgrades/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/upgrades/index.html b/content/documentation/latest/upgrades/index.html
index b72cb1c..ad83a32 100644
--- a/content/documentation/latest/upgrades/index.html
+++ b/content/documentation/latest/upgrades/index.html
@@ -153,6 +153,7 @@ R Removed feature/behavior
<td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Mesos Core-->
<ul style="padding-left:10px;">
+ <li>A <a href="#1-7-x-linux-devices-isolator">Linux devices isolator</a></li>
</ul>
</td>
@@ -536,6 +537,15 @@ R Removed feature/behavior
<h2>Upgrading from 1.6.x to 1.7.x</h2>
+<p><a name="1-7-x-linux-devices-isolator"></a></p>
+
+<ul>
+<li>A new <a href="/documentation/latest/./isolators/linux-devices/"><code>linux/devices</code></a> isolator has been
+added. This isolator automatically populates containers with devices
+that have been whitelisted with the <code>--allowed_devices</code> agent flag.</li>
+</ul>
+
+
<p><a name="1-7-x-container-logger"></a></p>
<ul>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/85919a82/content/documentation/mesos-containerizer/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/mesos-containerizer/index.html b/content/documentation/mesos-containerizer/index.html
index 0e5a885..6ce90bf 100644
--- a/content/documentation/mesos-containerizer/index.html
+++ b/content/documentation/mesos-containerizer/index.html
@@ -153,6 +153,7 @@ can write modules that implement custom isolators.</p>
<li>filesystem/windows</li>
<li><a href="/documentation/latest/./gpu-support/">gpu/nvidia</a></li>
<li><a href="/documentation/latest/./isolators/linux-capabilities/">linux/capabilities</a></li>
+<li><a href="/documentation/latest/./isolators/linux-devices/">linux/devices</a></li>
<li><a href="/documentation/latest/./isolators/namespaces-ipc/">namespaces/ipc</a></li>
<li><a href="/documentation/latest/./isolators/namespaces-pid/">namespaces/pid</a></li>
<li><a href="/documentation/latest/./cni/">network/cni</a></li>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/85919a82/content/documentation/upgrades/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/upgrades/index.html b/content/documentation/upgrades/index.html
index 6765995..61dfaf4 100644
--- a/content/documentation/upgrades/index.html
+++ b/content/documentation/upgrades/index.html
@@ -153,6 +153,7 @@ R Removed feature/behavior
<td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Mesos Core-->
<ul style="padding-left:10px;">
+ <li>A <a href="#1-7-x-linux-devices-isolator">Linux devices isolator</a></li>
</ul>
</td>
@@ -536,6 +537,15 @@ R Removed feature/behavior
<h2>Upgrading from 1.6.x to 1.7.x</h2>
+<p><a name="1-7-x-linux-devices-isolator"></a></p>
+
+<ul>
+<li>A new <a href="/documentation/latest/./isolators/linux-devices/"><code>linux/devices</code></a> isolator has been
+added. This isolator automatically populates containers with devices
+that have been whitelisted with the <code>--allowed_devices</code> agent flag.</li>
+</ul>
+
+
<p><a name="1-7-x-container-logger"></a></p>
<ul>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/85919a82/content/sitemap.xml
----------------------------------------------------------------------
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 0346975..5075066 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -185,6 +185,10 @@
<lastmod>2018-05-29T00:00:00+00:00</lastmod>
</url>
<url>
+ <loc>http://mesos.apache.org/documentation/latest/isolators/linux-devices/</loc>
+ <lastmod>2018-05-29T00:00:00+00:00</lastmod>
+ </url>
+ <url>
<loc>http://mesos.apache.org/documentation/latest/isolators/filesystems/</loc>
<lastmod>2018-05-29T00:00:00+00:00</lastmod>
</url>