jdef

would it help to be able to use some of the newer kubelet network drivers? e.g. https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/network/kubenet/kubenet_linux.go On Mon, Feb 8, 2016 at 7:46 AM, Brandon [email protected] wrote: > Thanks...

It appears to do some bridge reconfiguration and uses a specific subnet that may be passed in as a command line flag. Basically, it configures the node just like the...

Can you post your executor logs somewhere? Perhaps as a gist or pastebin? On Mon, Feb 8, 2016 at 10:02 AM, Brandon [email protected] wrote: > OK, after setting that flag,...

you may be interested in #785 (which should be merged to master shortly); i've also spent some time trying to get this working. relatively successful with the changes from #785...

I've tried running both my hosts's docker daemon, as well as the slave's docker daemon, in forced cgroupfs mode. I experience the same symptoms. `/proc//cgroup` includes cgroup paths that make...

related to #355

Is the same error that you sent to the mesos-dev mailing list? If so it's already been suggested that you should enable the `mesos` containerizer for your mesos slave/agent procs....

My understanding is that k8s "node ports" are essentially host ports, which are allocated from the host's netns, in contrast to service ports which are magical and are defined in...

otherwise, if we don't want to wait for global resources in mesos, we the scheduler could just simply refuse to launch executors on slave's that don't have all the ports...

It looks like "quotas" is where future Mesos work will happen: https://docs.google.com/document/d/16iRNmziasEjVOblYp5bbkeBZ7pnjNlaIzPQqMTHQ-9I/edit# In the meantime, perhaps we should modify the scheduler so that it attempts to reserve the same range...