Do you want to request a feature or report a bug?

Documentation improvement

In digestAuth documentation, Kubernetes section does not contain any useful example explaining how to put credentials into a file. The given example is same as users(using base

when showing the graph of the cluster it shows unmanaged pods and containers with names similar to the name of the cluster

so, what is the main job for those unmanaged pods and containers? and why they keep appears and disappears in a short time?

It's not quite clear reading the chronos doc:

https://mesos.github.io/chronos/docs/api.html#adding-a-docker-job

Mesos 0.22.0 added support for forcibly pulling the latest version of your Docker image before launching the task, and this behavior can be enabled in Chronos by adding the forcePullImage boolean to your container configuration.

Chronos will default to not doing a `docker pu

• Add labels appropriate to the issue
  bug

• Describe the expected behaviour and the actual behaviour
  .....
  ervice/rabbitmq created
  deployment.extensions/session-db created
  service/session-db created
  deployment.extensions/shipping created
  service/shipping created
  deployment.extensions/user-db created
  service/user-db created
  deployment.extensions/user created
  service/user created
  Er

If it already is, it serves two masters (which isn't clear).

e.g. better documentation for self-signed certs

Summary

Rexray on CEPH Nautilus ignores env CEPH_ARGS and config.yml
default fall back is try client.admin keyring
config.yml:
libstorage:
service: rbd
rbd:
defaultPool: rbd
cephArgs: --id docker

New Feature

add the CEPH_ARGS to the internal build command

Bug Reports

not a bug on rexray

#Patch
diff rexray/libstorage/drivers/storage/rbd/utils/utils.go

33a34

We've tried for feature parity, but there are certain things that are still specific to one of the proxies. It would be helpful to have some sort of documentation tag for these features.

If you currently have both shuffleTasksForOverloadedSlaves: true and spreadAllSlavesEnabled: trueenabled, and have requests running with SPREAD_ALL_SLAVES placement, then having any busy slaves currently results in a ton of task churn for no reason and ends up causing lots of poller delays and task instability.

I believe a check needs to be [added here](https://github.com/HubSpot/Singular

It's really difficult to read a command like docker run --entrypoint=mesos-master --net=host -d --name=leader --volume=/home/jobStoreParentDir:/jobStoreParentDir quay.io/ucsc_cgl/toil:3.6.0 --registry=in_memory --ip=127.0.0.1 --port=5050 --allocation_interval=500ms on one line.

Would it be possible to split it with \ so that Sphinx shows it all at once? E.g.

docker run \
    --entrypoint

I'm trying to read through the v1 example scheduler but it's very difficult to follow. It calls a lot of APIs that are barely documented. Even when a func is documented it's usually just a very minimal description of what it does.

What's missing is any context. I have no idea why any of these calls are important, nor do I have any clue of how this all fits together.

What I'd like to see is

Hi,

the Haproxy supports h2 frontend support and I tried to enable it with marathon-lb. I took a while but finally I was successful.

I created the following overwrite template HAPROXY_HTTPS_FRONTEND_HEAD file (including the leading and post empty line) and added into the template folder.

``

frontend marathon_https_in
bind *:443 ssl {sslCerts} alpn h2,http/1.1
mode http

``

#245 fixed a build issue in the Add Steps demo by upgrading Grafana. That version bump introduced a "Getting Started" panel in the Grafana dashboard, which should be removed.

Background

Newer versions of Grafana include a "Getting Started" panel that should be disabled for our demo:
<img width="1016" alt="Screen Shot 2019-03-26 at 10 13 19 AM" src="https://user-images.githubusercontent.c

Describe the bug
In a couple places [1] [2], the user is instructed to postfix the ZK connection string with a directory (zk node?) /cook. If the user does this, the scheduler for some reason will never connect to the mesos master.

[1] https://github.com/twosigma/Cook/blob/master/scheduler/docs/configuration.adoc
[2] https://github.com/twosigma/Cook/blob/master/scheduler/example-prod-co

We need to clearly highlight API 1.X features in our documentation.

• Update GoDoc / comments
• Update project README

Please provide docs for various volplugin REST endpoints. It will be nice to document

• Volplugin Operation
• URL
• Request type (POST, GET, PUT, DELETE)
• Input JSON
• Output JSON
• Errors returned including http status codes

I am not familiar with consul. I thought I need to run a consul server along with marathon-consul in Mesos-master. And run consul-agent in each Mesos-agent ?
I am a bit confused on the relationship between marathon-consul and consul-server, because there is no config about consul-server address...

Document how CONFIG_TEMPLATE_PATH has to be used in the configs section of the svc.yml.

         template: {{CONFIG_TEMPLATE_PATH}}/myconfig.yml

For the local yml test BasicServiceSpecTest.java [73] sets CONFIG_TEMPLATE_PATH, for the distribution it has to be set to frameworkname-scheduler in the env section of the marathon.json.mustache.