Rob Johnson

I think this could be a good one to go after @matthewbentley . we should chat to @jvperrin to see if the issues we've seen lately with 'unknown' tasks were...

that's true that this won't _always_ be an error condition, but I wonder if the 'norm' here would just be people not having the right limits set. How about a...

This will mean the default is pretty yelpy

@keymone it was mentioned by one of the ads teams that they often had this issue. @solarkennedy I'm fine with that as a less noisy solution.

yeah, the test can be made more resilient by looking for a free port, rather than hardcoding one.

you can do this, though metastatus is a bit more generic. The ``-g`` option to metastatus accepts an arbitrary attribute, and shows you usage per attribute value in the cluster....

@Spritekin there is no way of expressing 'on this schedule, launch _multiple_ tasks'. However, you could doing this by having multiple jobs (named according to the host they run on)...

@batizty Chronos will only run the task on one host: that is, your constraint means that Chronos will make sure that the _one_ host it picks to run the task...

We've implemented Cron support along with a few other changes in our fork at [Yelp/chronos](github.com/Yelp/chronos) but it'll be difficult to merge as is with the recent changes made to the...

just adding a +1 for wanting to see this functionality. From what I can see, the method involving cloudmap attributes won't provide the same capabilities that envoy has natively, particularly...