11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation

MESOSPHERE DOCUMENTATION 1.8 ADMINISTRATION INSTALLING DC/OS CUSTOM

Configuration parameters
ENTERPRISE DC/OS Updated: November 18, 2016

These configuration parameters are specified in YAML format in your config.yaml file. During DC/OS
installation the configuration file is used to generate a customized DC/OS build.

Cluster Setup
agent_list
This parameter specifies a YAML nested list ( ) of IPv4 addresses to your private agent host names.

aws_template_storage_bucket
This parameter specifies the name of your S3 bucket. For more information, see Generating Custom
AWS CF Templates.

aws_template_storage_bucket_path
This paraemter specifies the S3 bucket storage path. For more information, see Generating Custom AWS
CF Templates.

aws_template_storage_region_name
This parameters specifies the S3 region. For more information, see Generating Custom AWS CF
Templates.

aws_template_upload
This parameter specifies whether to automatically upload the customized advanced templates to your
S3 bucket. If you specify true , you must also specify these parameters:

aws_template_storage_access_key_id This parameters specifies the AWS Access Key ID.

aws_template_storage_secret_access_key This parameter specifies the AWS Secret Access Key.

For more information, see Generating Custom AWS CF Templates.

bootstrap_url
This required parameter specifies the URI path for the DC/OS installer to store the customized DC/OS
build files. If you are using the automated DC/OS installer, you should specify
bootstrap_url:file:///opt/dcos_install_tmp unless you have moved the installer assets. By default
the automated DC/OS installer places the build files in file:///opt/dcos_install_tmp .
cluster_name
https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 1/15
11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation

cluster_name
This parameter specifies the name of your cluster.

exhibitor_storage_backend
This parameter specifies the type of storage backend to use for Exhibitor. You can use internal DC/OS
storage ( static ) or specify an external storage system ( zookeeper , and aws_s3 ) for configuring and
orchestrating ZooKeeper with Exhibitor on the master nodes. Exhibitor automatically configures your
ZooKeeper installation on the master nodes during your DC/OS installation.

exhibitor_storage_backend:static This option specifies that the Exhibitor storage backend is

managed internally within your cluster.
exhibitor_storage_backend:zookeeper This option specifies a ZooKeeper instance for shared
storage. If you use a ZooKeeper instance to bootstrap Exhibitor, this ZooKeeper instance must be
separate from your DC/OS cluster. You must have at least 3 ZooKeeper instances running at all times
for high availability. If you specify zookeeper , you must also specify these parameters.
exhibitor_zk_hosts This parameter specifies a comma-separated list (
<ZK_IP>:<ZK_PORT>,<ZK_IP>:<ZK_PORT>,<ZK_IP:ZK_PORT> ) of one or more ZooKeeper node IP
and port addresses to use for configuring the internal Exhibitor instances. Exhibitor uses this
ZooKeeper cluster to orchestrate its configuration. Multiple ZooKeeper instances are
recommended for failover in production environments.
exhibitor_zk_path This parameter specifies the filepath that Exhibitor uses to store data,
including the zoo.cfg file.
exhibitor_storage_backend:aws_s3 This option specifies an Amazon Simple Storage Service (S3)
bucket for shared storage. If you specify aws_s3 , you must also specify these parameters.
aws_access_key_id This parameter specifies AWS key ID.
aws_region This parameter specifies AWS region for your S3 bucket.
aws_secret_access_key This parameter specifies AWS secret access key.
exhibitor_explicit_keys This parameter specifies whether you are using AWS API keys to grant
Exhibitor access to S3.
exhibitor_explicit_keys:'true' If youre using AWS API keys to manually grant Exhibitor
access.
exhibitor_explicit_keys:'false' If youre using AWS Identity and Access Management
(IAM) to grant Exhibitor access to s3.
s3_bucket This parameter specifies name of your S3 bucket.
s3_prefix This parameter specifies S3 prefix to be used within your S3 bucket to be used by
Exhibitor.
Tip: AWS EC2 Classic is not supported.

master_discovery
This required parameter specifies the Mesos master discovery method. The available options are
static or master_http_loadbalancer .

master_discovery:static This option specifies that Mesos agents are used to discover the masters
by giving each agent a static list of master IPs. The masters must not change IP addresses, and if a

https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 2/15
11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation

master is replaced, the new master must take the old masters IP address. If you specify static , you
must also specify this parameter:
master_list This required parameter specifies a list of your static master IP addresses as a YAML
nested series ( ).
master_discovery:master_http_loadbalancer This option specifies that the set of masters has an
HTTP load balancer in front of them. The agent nodes will know the address of the load balancer.
They use the load balancer to access Exhibitor on the masters to get the full list of master IPs. If you
specify master_http_load_balancer , you must also specify these parameters:
exhibitor_address This required parameter specifies the location (preferably an IP address) of
the load balancer in front of the masters. The load balancer must accept traic on ports 8080,
5050, 80, and 443; and forward it to the same ports on the master (for example, 8080 on lb ->
8080 on one master, 5050 on lb -> 5050 on one master). The master should forward any new
connections via round robin, and should avoid machines that do not respond to requests on
port 5050 to ensure the master is up.
num_masters This parameter specifies the number of Mesos masters in your DC/OS cluster. If
master_discovery:static , do not use the num_masters parameter.

Note: On platforms like AWS where internal IPs are allocated dynamically, you should not use a static
master list. If a master instance were to terminate for any reason, it could lead to cluster instability.

public_agent_list
This parameter specifies a YAML nested list ( ) of IPv4 addresses to your public agent host names.

rexray_config_method
This parameter specifies the REX-Ray configuration method for enabling external persistent volumes in
Marathon. REX-Ray is a storage orchestration engine. For more information, see the external persistent
volumes documentation.

rexray_config_method:empty An empty REX-ray configuration. This is the default value.

awsA REX-Ray configuration that is set up for AWS EC2 (EBS) and AWS Identity and Access
Management (IAM).
rexray_config_method:file Specify the path to a REX-Ray configuration file with
rexray_config_filename .

rexray_config_filename The path of a REX-Ray configuration file. For example:

rexray_config_filename: genconf/rexray.yaml

Security and Authentication

auth_cookie_secure_flag
This parameter specifies whether to allow web browsers to send the DC/OS authentication cookie
through a non-HTTPS connection. Because the DC/OS authentication cookie allows access to the
DC/OS cluster, it should be sent over an encrypted connection to prevent man-in-the-middle attacks.

https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 3/15
11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation

auth_cookie_secure_flag:false (default) Browsers will send the DC/OS authentication cookie

through either an unencrypted HTTP connection or an encrypted HTTPS connection.
auth_cookie_secure_flag:true The authentication cookie set by DC/OS will contain the Secure
flag, which instructs the browser to not send the cookie over unencrypted HTTP connections. This
could cause authentication to fail under the following circumstances.
If the security mode is disabled .
If the security mode is permissive , the URL specifies HTTP, and the URL includes a path (e.g.,
http://cluster-url.com/path/).
There are proxies in between the browser and DC/OS.

bouncer_expiration_auth_token_days
This parameter sets the auth token time-to-live (TTL) for Identity and Access Management. You must
specify the value in Python float syntax wrapped in a YAML string. By default the token expires aer 5
days. For example, to set the token lifetime to half a day:

bouncer_expiration_auth_token_days:'0.5'

customer_key
This parameter specifies the Enterprise DC/OS customer key. Customer keys are delivered via email to
the Authorized Support Contact.
This key is a 128-bit hyphen-delimited hexadecimal identifier used to distinguish an individual cluster.
The customer key serves as the Universally Unique Identifier (UUID) for a given installation.
Customer keys look like this:

ab1c23de45f67g8h9012i345j6k7lm8n

security
This parameter specifies your desired security mode. security:permissive is the default value. The
following table provides a high-level view of what changes per setting.
security:disabled

Mesos resource Marathon resource Mesos master/agent Linux

Encryption
authentication authentication permissions user
Disabled* Disabled Required Disabled root

* HTTPS requests from outside of the cluster will be rejected because the Admin Router does not have a
valid certificate.
security:permissive

Mesos resource Marathon resource Mesos master/agent Linux

Encryption
authentication authentication permissions user
Optional Optional Required Disabled root

https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 4/15
11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation

security:strict

Mesos resource Marathon resource Mesos master/agent Linux

Encryption
authentication authentication permissions user
nobod
Required Required Required Enabled
y

Important: In security:strict mode, only the Cassandra, HDFS, Kafka, Marathon, Marathon-LB, and
Spark user services can be deployed and they require special configuration.

For more information see the example and for a detailed discussion of the ramifications of each setting,
see the documentation.

TLS/SSL encryption
Service Authentication
Mesos master and agent permissions
Configuring Linux users
Tip: You can determine which security mode your cluster is using by SSHing to your master and viewing
the contents of opt/mesosphere/etc/bootstrapconfig.json .

ssh_key_path
This parameter specifies the path to the installer uses to log into the target nodes. By default this is set
to /genconf/ssh_key . This parameter should not be changed because /genconf is local to the container
that is running the installer, and is a mounted volume.

ssh_port
This parameter specifies the port to SSH to, for example 22 .

ssh_user
This parameter specifies the SSH username, for example centos .

superuser_password_hash
This required parameter specifies the hashed superuser password. The superuser_password_hash is
generated by using the installer hashpassword flag. For more information, see Identity and Access
Management.

superuser_username
This required parameter specifies the Admin username. For more information, see Identity and Access
Management.

telemetry_enabled
This parameter specifies whether to enable sharing of anonymous data for your cluster.

telemetry_enabled:'true' Enable anonymous data sharing. This is the default value.

https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 5/15
11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation

telemetry_enabled:'false' Disable anonymous data sharing.

If youve already installed your cluster and would like to disable this in-place, you can go through an
upgrade with the same parameter set.

zk_super_credentials
This parameter specifies the ZooKeeper superuser credentials. This protects access to Mesos, DC/OS
Marathon, Identity and Access Management, Package service, and other cluster metadata. It is
recommended that you specify a non-default value. For more information about ZooKeeper passwords,
see the documentation.

For more information see the example.

zk_master_credentials
This parameter specifies the ZooKeeper master credentials. This protects access to Mesos, DC/OS
Marathon, Identity and Access Management, Package service, and other cluster metadata. It is
recommended that you specify a non-default value. For more information about ZooKeeper passwords,
see the documentation.

For more information see the example.

zk_agent_credentials
This parameter specifies the ZooKeeper agent credentials. This protects access to Mesos, DC/OS
Marathon, Identity and Access Management, Package service, and other cluster metadata. It is
recommended that you specify a non-default value. For more information about ZooKeeper passwords,
see the documentation.
For more information see the example.

Networking
dcos_overlay_enable
This parameter specifies whether to enable DC/OS overlay networks.

Important: Overlay networks require Docker 1.11. If you are using Docker 1.10 or earlier, you must
specify dcos_overlay_enable:'false' . For more information, see the system requirements.

dcos_overlay_enable:'false' Do not enable the DC/OS overlay network.

dcos_overlay_enable:'true' Enable the DC/OS overlay network. This is the default value. When
the overlay network is enabled you can also specify the following parameters:
dcos_overlay_config_attempts This parameter specifies how many failed configuration
attempts are allowed before the overlay configuration modules stop trying to configure an
overlay network.
Tip: The failures might be related to a malfunctioning Docker daemon.

dcos_overlay_mtu This parameter specifies the maximum transmission unit (MTU) of the Virtual
Ethernet (vEth) on the containers that are launched on the overlay.
https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 6/15
11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation

dcos_overlay_network This group of parameters define an overlay network for DC/OS. The
default configuration of DC/OS provides an overlay network named dcos whose YAML
configuration is as follows:

dcos_overlay_network:
vtep_subnet:44.128.0.0/20
vtep_mac_oui:70:B3:D5:00:00:00
overlays:
name:dcos
subnet:9.0.0.0/8
prefix:26

vtep_subnet This parameter specifies a dedicated address space that is used for the VxLAN
backend for the overlay network. This address space should not be routeable from outside
the agents or master.
vtep_mac_oui This parameter specifies the MAC address of the interface connecting to it in
the public node.
Important: The last 3 bytes must be 00 .

overlays
nameThis parameter specifies the canonical name (see limitations for constraints on
naming overlay networks).
subnet This parameter specifies the subnet that is allocated to the overlay network.
prefix This parameter specifies the size of the subnet that is allocated to each agent
and thus defines the number of agents on which the overlay can run. The size of the
subnet is carved from the overlay subnet.
For more information see the example and documentation.

dns_search
This parameter specifies a space-separated list of domains that are tried when an unqualified domain is
entered (e.g. domain searches that do not contain .). The Linux implementation of /etc/resolv.conf
restricts the maximum number of domains to 6 and the maximum number of characters the setting can
have to 256. For more information, see man /etc/resolv.conf.
A search line with the specified contents is added to the /etc/resolv.conf file of every cluster host.
search can do the same things as domain and is more extensible because multiple domains can be
specified.

In this example, example.com has public website www.example.com and all of the hosts in the datacenter
have fully qualified domain names that end with dc1.example.com . One of the hosts in your datacenter
has the hostname foo.dc1.example.com . If dns_search is set to dc1.example.com example.com, then
every DC/OS host which does a name lookup of foo will get the A record for foo.dc1.example.com . If a
machine looks up www , first www.dc1.example.com would be checked, but it does not exist, so the search
would try the next domain, lookup www.example.com , find an A record, and then return it.

dns_search:dc1.example.comdc1.example.comexample.comdc1.example.comdc2.example.comexample.com

master_dns_bindall
https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 7/15
11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation

This parameter specifies whether the master DNS port is open. An open master DNS port listens publicly
on the masters. If you are upgrading, set this parameter to true .

'master_dns_bindall':'true' The master DNS port is open. This is the default value.
'master_dns_bindall':'false' The master DNS port is closed.

resolvers
This required parameter specifies a YAML nested list ( ) of DNS resolvers for your DC/OS cluster nodes.
You can specify a maximum of 3 resolvers. Set this parameter to the most authoritative nameservers
that you have. If you want to resolve internal hostnames, set it to a nameserver that can resolve them. If
you have no internal hostnames to resolve, you can set this to a public nameserver like Google or AWS.
In the example file above, the Google Public DNS IP addresses (IPv4) are specified ( 8.8.8.8 and
8.8.4.4 ).

Caution: If you set the resolvers parameter incorrectly, you will permanently damage your
configuration and have to reinstall DC/OS.

use_proxy
This parameters specifies whether to enable the DC/OS proxy.
use_proxy:'false' Do not configure DC/OS components to use a custom proxy. This is the default
value.
use_proxy:'true' Configure DC/OS components to use a custom proxy. If you specify
use_proxy:'true' , you can also specify these parameters:
Important: The specified proxies must be resolvable from the provided list of resolvers.

http_proxy:<your_http_proxy> This parameter specifies the HTTP proxy.

https_proxy:<your_https_proxy> This parameter specifies the HTTPS proxy.
no_proxy:<ipaddress> This parameter specifies YAML nested list (-) of addresses to exclude
from the proxy.

For more information, see the examples.

Important: You should also configure an HTTP proxy for Docker.

Performance and Tuning

check_time
This parameter specifies whether to check if Network Time Protocol (NTP) is enabled during DC/OS
startup. It recommended that NTP is enabled for a production environment.
check_time:'true' Check if NTP is enabled during startup. You will receive an error if this is not
enabled. This is the default value.
check_time:'false' Do not check if NTP is enabled during startup.

docker_remove_delay
https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 8/15
11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation

This parameter specifies the amount of time to wait before removing stale Docker images stored on the
agent nodes and the Docker image generated by the installer. It is recommended that you accept the
default value 1 hour.

dcos_audit_logging
This parameter specifies whether security decisions (authentication, authorization) are logged for
Mesos, Marathon, and Jobs.

'dcos_audit_logging':'true' Mesos, Marathon, and Jobs are logged. This is the default value.
'dcos_audit_logging':'false' Mesos, Marathon, and Jobs are not logged.

gc_delay
This parameter specifies the maximum amount of time to wait before cleaning up the executor
directories. It is recommended that you accept the default value of 2 days.

log_directory
This parameter specifies the path to the installer host logs from the SSH processes. By default this is set
to /genconf/logs . In most cases this should not be changed because /genconf is local to the container
that is running the installer, and is a mounted volume.

process_timeout
This parameter specifies the allowable amount of time, in seconds, for an action to begin aer the
process forks. This parameter is not the complete process time. The default value is 120 seconds.

Tip: If have a slower network environment, consider changing to process_timeout:600 .

Example Configurations
DC/OS cluster with three masters, five private agents, security mode specified, and
Exhibitor/ZooKeeper managed internally.

agent_list:
<agentprivateip1>
<agentprivateip2>
<agentprivateip3>
<agentprivateip4>
<agentprivateip5>
bootstrap_url:'file:///opt/dcos_install_tmp'
customer_key:<customerkey>
cluster_name:'<clustername>'
log_directory:/genconf/logs
master_discovery:static
master_list:
<masterprivateip1>
<masterprivateip2>
<masterprivateip3>
process_timeout:120
resolvers:

https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 9/15
11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation
<dnsresolver1>
<dnsresolver2>
#Chooseyoursecuritymode:permissive,strict,ordisabled
security:<securitymode>
ssh_key_path:/genconf/sshkey
ssh_port:'<portnumber>'
ssh_user:<username>

DC/OS cluster with three masters, an Exhibitor/ZooKeeper backed by an AWS S3 bucket, AWS
DNS, five private agents, security mode specified, and one public agent node

agent_list:
<agentprivateip1>
<agentprivateip2>
<agentprivateip3>
<agentprivateip4>
<agentprivateip5>
aws_access_key_id:AKIAIOSFODNN7EXAMPLE
aws_region:uswest2
aws_secret_access_key:wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
bootstrap_url:file:///tmp/dcos
cluster_name:s3example
customer_key:<customerkey>
exhibitor_storage_backend:aws_s3
exhibitor_explicit_keys:'true'
log_directory:/genconf/logs
master_discovery:static
master_list:
<masterprivateip1>
<masterprivateip2>
<masterprivateip3>
process_timeout:120
resolvers:
169.254.169.253
#Chooseyoursecuritymode:permissive,strict,ordisabled
security:<securitymode>
s3_bucket:mybucket
s3_prefix:s3example
ssh_key_path:/genconf/sshkey
ssh_port:'<portnumber>'
ssh_user:<username>

DC/OS cluster with three masters, an Exhibitor/ZooKeeper backed by ZooKeeper,

master_http_loadbalancer master discovery, one public agent node, 5 private agents, security
mode specified, and Google DNS

agent_list:
<agentprivateip1>
<agentprivateip2>
<agentprivateip3>
<agentprivateip4>
<agentprivateip5>
bootstrap_url:file:///tmp/dcos
cluster_name:zkexample
customer_key:<customerkey>
exhibitor_storage_backend:zookeeper
exhibitor_zk_hosts:10.0.0.1:2181,10.0.0.2:2181,10.0.0.3:2181
exhibitor_zk_path:/zkexample
log_directory:/genconf/logs
master_discovery:master_http_loadbalancer

https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 10/15
11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation
num_masters:3
exhibitor_address:67.34.242.55
public_agent_list:
<publicagentprivateip>
process_timeout:120
resolvers:
8.8.4.4
8.8.8.8
#Chooseyoursecuritymode:permissive,strict,ordisabled
security:<securitymode>
ssh_key_path:/genconf/sshkey
ssh_port:'<portnumber>'
ssh_user:<username>

DC/OS cluster with three masters, an Exhibitor/ZooKeeper managed internally, two DC/OS
overlay networks, two private agents, security mode specified, and Google DNS

agent_list:
<agentprivateip1>
<agentprivateip2>
<agentprivateip3>
#Usethisbootstrap_urlvalueunlessyouhavemovedtheDC/OSinstallerassets.
bootstrap_url:file:///opt/dcos_install_tmp
cluster_name:<clustername>
customer_key:<customerkey>
master_discovery:static
master_list:
<masterprivateip1>
<masterprivateip2>
<masterprivateip3>
resolvers:
#YouprobablydonotwanttousethesevaluessincetheypointtopublicDNSservers.
#Insteadusevaluesthataremorespecifictoyourparticularinfrastructure.
8.8.4.4
8.8.8.8
#Chooseyoursecuritymode:permissive,strict,ordisabled
security:<securitymode>
ssh_port:22
ssh_user:centos
dcos_overlay_enable:true
dcos_overlay_mtu:9001
dcos_overlay_config_attempts:6
dcos_overlay_network:
vtep_subnet:44.128.0.0/20
vtep_mac_oui:70:B3:D5:00:00:00
overlays:
name:dcos
subnet:9.0.0.0/8
prefix:26
name:dcos1
subnet:192.168.0.0/16
prefix:24

DC/OS cluster with three masters, an Exhibitor/ZooKeeper managed internally, a custom HTTP
proxy, two private agents, security mode specified, and Google DNS

agent_list:
<agentprivateip1>
<agentprivateip2>
<agentprivateip3>

https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 11/15
11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation
#Usethisbootstrap_urlvalueunlessyouhavemovedtheDC/OSinstallerassets.
bootstrap_url:file:///opt/dcos_install_tmp
cluster_name:<clustername>
customer_key:<customerkey>
master_discovery:static
master_list:
<masterprivateip1>
<masterprivateip2>
<masterprivateip3>
resolvers:
#YouprobablydonotwanttousethesevaluessincetheypointtopublicDNSservers.
#Insteadusevaluesthataremorespecifictoyourparticularinfrastructure.
8.8.4.4
8.8.8.8
#Chooseyoursecuritymode:permissive,strict,ordisabled
security:<securitymode>
ssh_port:22
ssh_user:centos
use_proxy:'true'
http_proxy:http://<your_http_proxy>/
https_proxy:https://<your_https_proxy>/
no_proxy:
'*.int.example.com'

DC/OS cluster with three masters, two private agents, one public agent, security mode
specified, an Exhibitor/ZooKeeper managed internally, and Google DNS

agent_list:
<agentprivateip1>
<agentprivateip2>
<agentprivateip3>
#Usethisbootstrap_urlvalueunlessyouhavemovedtheDC/OSinstallerassets.
bootstrap_url:file:///opt/dcos_install_tmp
cluster_name:<clustername>
customer_key:<customerkey>
master_discovery:static
master_list:
<masterprivateip1>
<masterprivateip2>
<masterprivateip3>
resolvers:
#YouprobablydonotwanttousethesevaluessincetheypointtopublicDNSservers.
#Insteadusevaluesthataremorespecifictoyourparticularinfrastructure.
8.8.4.4
8.8.8.8
#Chooseyoursecuritymode:permissive,strict,ordisabled
security:<securitymode>
ssh_port:22
ssh_user:centos
zk_super_credentials:<userid>:<password>
zk_master_credentials:<userid>:<password>
zk_agent_credentials:<userid>:<password>

https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 12/15
11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation

https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 13/15
11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation

https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 14/15
11/27/2016 ConfigurationparametersMesosphereDC/OSDocumentation

https://docs.mesosphere.com/1.8/administration/installing/custom/configurationparameters/ 15/15