mesos-master job from mesos/1
Github source:
d07b570b
or
master branch
Properties¶
mesos
¶
cluster_name
¶Human readable name for the Apache Mesos cluster
- Default
Mesos Cluster
framework_credentials
¶Array of credentials. Each item contains a ‘principal’ and ‘secret’ separated by whitespace
- Default
[]
master
¶
allocation_interval
¶Amount of time to wait between performing (batch) allocations
- Default
1secs
authenticate
¶Only authenticated frameworks are allowed to register?
- Default
false
framework_sorter
¶Policy to use for allocating resources between a given user’s frameworks
- Default
drf
group
¶Group which will own the Apache Mesos Master services
- Default
vcap
listen_address
¶IP address where Apache Mesos Master will listen on
- Default
0.0.0.0
logbufsecs
¶How many seconds to buffer log messages for
- Default
0
port
¶Port where Apache Mesos Master will listen on
- Default
80
roles
¶A comma seperated list of the allocation roles that frameworks in this cluster may belong to
- Default
""
root_submissions
¶Can root submit frameworks?
- Default
true
user
¶User which will own the Apache Mesos Master services
- Default
root
user_sorter
¶Policy to use for allocating resources between users
- Default
drf
weights
¶A comma seperated list of role/weight pairs of the form ‘role=weight,role=weight’
- Default
""
zk_state
¶Path in ZooKeeper for storing Apache Mesos state
- Default
mesos
zookeeper
¶
client_port
¶Port at which the clients will connect to Apache Zookeeper
- Default
2181
servers
¶List of all Apache Zookeeper server host IP/hostnames
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/mesos-master/
directory
(learn more).
bin/job_properties.sh
(frombin/job_properties.sh.erb
)bin/master_ctl
(frombin/master_ctl.erb
)config/framework_credentials.cfg
(fromconfig/framework_credentials.cfg.erb
)config/zoo_mesos.cfg
(fromconfig/zoo_mesos.cfg.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.