Re: Updated agent resources with every offer.

So I've thought about this carefully and I've thought of a workaround that doesn't work yet, but maybe will if people can chime in. I have a demon thread that starts when the executor registers with the framework. The demon thread probes the free disk every n seconds and sends an update with a

Re: [VOTE] Release Apache Mesos 0.27.1 (rc1)

On Feb 16, 2016, at 4:52 PM, Michael Park wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 0.27.1. > I filed a bug against 0.27.0 where Mesos can emit totally invalid JSON in response to the /files/read.json endpoint:

[VOTE] Release Apache Mesos 0.27.1 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.27.1. 0.27.1 includes the following: * Improved `systemd` integration. * Ability to disable `systemd` integration. * Additional

Re: Documentation for monitor/statistics endpoint

We are in the process of figuring out how to better document endpoints like these. For now your best bet is to look at the ResourceStatistics protobuf in mesos.proto. On Tue, Feb 16, 2016 at 11:29 AM, Brandon Bercovich

Documentation for monitor/statistics endpoint

Hi, I was looking at the documentation for: http://mesos.apache.org/documentation/latest/endpoints/monitor/statistics/ I compared the example to some output from my agents and I noticed I had a few statistics that weren't listed in the example such as, mem_cache_bytes and mem_unevictable_bytes

Re: Precision of scalar resources

+1 Strong initial first step to remove a huge headache. > On 12 Feb 2016, at 14:25, Neil Conway wrote: > > Additional precision in resource values will be discarded > (via rounding).

Re: Mesos integration with OpenStack HEAT AutoScaling

Hi Everybody, i would also suggest using the Magnum API to do this. For our Canary-testing/releasing & autoscaling platform Vamp (www.vamp.io ) we’re currently setting up a collaboration project to develop a Vamp-Magnum driver. This way Vamp workflows can orchestrate and

Re: Mesos integration with OpenStack HEAT AutoScaling

Hi Petr, It would be great if you can also share your use case here, I can post your feedback/use case to Magnum community to improve Magnum support for Mesos. Thanks, Guangya On Tue, Feb 16, 2016 at 4:20 PM, Guangya Liu wrote: > Hi Peter, > > Have you ever tried Magnum

Re: Mesos integration with OpenStack HEAT AutoScaling

Hi Peter, Have you ever tried Magnum (https://github.com/openstack/magnum) which is the container service in OpenStack leveraging HEAT to integrate with Kubernetes, Swarm and Mesos. With Magnum, you do not need to maintain your own HEAT template but just let Magnum do this for you, it is more

Mesos integration with OpenStack HEAT AutoScaling

Hello, we are considering adopting Mesos but at the same time we need to run it on top of OpenStack at some places. My main questions is about how and if autoscaling defined via HEAT templates works together. And has to be done. I assume that scaling up is not much a problem - when Mesos detects