Documentation for Mesos On windows

Hi Is there any other documentation than the one on mesos site http://mesos.apache.org/documentation/latest/windows/ I was able to build mesos on AWS on an windows 2016 server. But I am not able to find any docs for starting the mesos master on windows? I understand that this is not recommended

Re: Welcome Andrew Schwartzmeyer as a new committer and PMC member!

Hi Andrew, It has been great to have you around and I am looking forward to what you’ll take on in the future. Cheers, Benjamin > On Nov 28, 2017, at 12:00 AM, Joseph Wu wrote: > > Hi devs & users, > > I'm happy to announce that Andrew Schwartzmeyer has become a new

Re: Welcome Andrew Schwartzmeyer as a new committer and PMC member!

Congratulations On Tue, Nov 28, 2017 at 3:08 PM Andrew Schwartzmeyer < and...@schwartzmeyer.com> wrote: > Thank you everyone for the welcome! > > It's been great working with you this past year, and I'm glad to > continue making this great project even better. > > Thanks again, > > Andy > >

Re: Marathon deployment without "blue/green" (need to free resources before deploying)

Thanks a lot! On 11/28/2017 02:44 PM, Tomek Janiszewski wrote: Hi It's described here https://mesosphere.github.io/marathon/docs/deployments.html#rolling-restarts > minimumHealthCapacity == 0 : All old instances can be killed before the new version is deployed. Best Tomek wt., 28 lis 2017

Re: Marathon deployment without "blue/green" (need to free resources before deploying)

Hi It's described here https://mesosphere.github.io/marathon/docs/deployments.html#rolling-restarts > minimumHealthCapacity == 0 : All old instances can be killed before the new version is deployed. Best Tomek wt., 28 lis 2017 o 14:42 użytkownik Adam Cecile napisał: > Hi

Marathon deployment without "blue/green" (need to free resources before deploying)

Hi there, We have a limited amount of GPU so when a new deployment occurs (replacing an existing one) in Marathon it gets locked because there's no GPUs left to deploy new version before killing the previous one. Is there any API parameter to force kill of the old instance first ? Thanks

Re: Persistent volumes

I agree with pretty much everything Hendrik just said with the exception of the use of disk quota. The polling mechanism employed for enforcing disk usage implies that any breach of the disk usage limit by a Task also implies loss of access to that data forever. This is true for ROOT volumes at