Re: cron-like scheduling in mesos framework?

Apache Aurora does also support cron scheduling (in addition to adhoc jobs and long running services). In contrast to chronos however, it does not support dependency chains. From: l vic lvic4...@gmail.com Reply-To: "user@mesos.apache.org" Date:

Threshold-based CPU and Memory Oversubscription

Hi everyone, we are happy to announce that we have open sourced two simple threshold-based oversubscription modules for Mesos. We use them for CPU and memory oversubscription and have them running in production. https://github.com/blue-yonder/mesos-threshold-oversubscription The

Re: Scheduler for distributed builds

?FWIW, Apache Aurora is also supporting ad-hoc jobs. In contrast to to chronos however, only without job dependencies. From: Guangya Liu Sent: Wednesday, April 27, 2016 09:59 To: user@mesos.apache.org Subject: Re: Scheduler for distributed

Re: SharedFilesystemIsolator (filesystem/shared)

moving filesystem/shared before we fix that issue. - Jie On Tue, Apr 12, 2016 at 2:16 AM, Erb, Stephan <stephan@blue-yonder.com<mailto:stephan@blue-yonder.com>> wrote: Hi Jie, I tried the new isolator and ran into an issue. Details are available in this ticket: https://issu

Re: SharedFilesystemIsolator (filesystem/shared)

retire filesystem/shared isolator in the next Mesos release. I'll send out an announcement shortly. - Jie On Mon, Apr 11, 2016 at 5:34 AM, Erb, Stephan <stephan@blue-yonder.com<mailto:stephan@blue-yonder.com>> wrote: Given that the "filesystem/linux" isolator has

Re: SharedFilesystemIsolator (filesystem/shared)

Given that the "filesystem/linux" isolator has landed, is it now considered to be a drop-in replacement for the "filesystem/shared" isolator? ____________ From: Erb, Stephan <stephan@blue-yonder.com> Sent: Wednesday, July 29, 2015 21:08 To: use

Re: Current state of the oversubscription feature

on, Mar 21, 2016 at 8:54 PM, Erb, Stephan <stephan@blue-yonder.com<mailto:stephan@blue-yonder.com>> wrote: Hi everyone, I am interested in the current state of the Mesos oversubscription feature [1]. In particular, I would like to know if anyone has taken a closer look at

Current state of the oversubscription feature

Hi everyone, I am interested in the current state of the Mesos oversubscription feature [1]. In particular, I would like to know if anyone has taken a closer look at non-compressible resources such as memory. Anything I should be aware of? Thanks and Best Regards, Stephan [1]

Re: Use cases for revocable resources

Revocable offers are currently implemented in Apache Aurora. Here is the design document https://docs.google.com/document/d/1r1WCHgmPJp5wbrqSZLsgtxPNj3sULfHrSFmxp2GyPTo/edit and here is the corresponding epic https://issues.apache.org/jira/browse/AURORA-1343. Best Regards, Stephan ?

Re: Mesos sometimes not allocating the entire cluster

Hi Tom, have you checked if any of the starvation issues explained in the Ebay blog post applies to you as well? http://www.ebaytechblog.com/2014/04/04/delivering-ebays-ci-solution-with-apache-mesos-part-i/? Best Regards, Stephan From: Tom Arnfeld

Re: Monitoring

There is also Prometheus. It tends to integrate with the Mesos-ecosystem in various ways: * There are exporters that can be used to scrape Mesos metrics (https://github.com/prometheus/mesos_exporter or https://github.com/mesosphere/mesos_exporter) * And exporters to scrape metrics of

Managing Secrets

Hi everyone, I'd like to explore mechanisms to provide secrets to applications deployed on Mesos (e.g. via Marathon or Apache Aurora). The classical workflow of having the passwords encrypted in the local git repository and only decrypted during deployment (for example via ansible vault)