Chronos v2.5.1

[Alex Rukletsov]

Folks,

as a small gift for 2018 Santa brought us a patch release of the stable Chronos flavor: v2.5.1. This release is aimed at users that have not, cannot, or want not to migrate to Chronos 3.0.

Highlights of this Release

Correctly handle TASK_STARTING task status updates.

Support for Mesos 1.3.1.

Tarball: https://github.com/mesos/chronos/archive/2.5.1.tar.gz

Docker image: https://hub.docker.com/r/mesosphere/chronos/ with the tag chronos-2.5.1-0.1.20171211074431.ubuntu1404-mesos-1.3.1

Packages are also available via the Mesosphere repositories, see: https://mesosphere.com/blog/2014/07/17/mesosphere-package-repositories/

Please report any issue you experience here: https://github.com/mesos/chronos/issues

AlexR,

on behalf of the Chronos contributors.

[Yuki Ishibashi]

Hello,

Is there a release plan going forward for Chronos support continuing in.... v2.x.x? 

I understand that v3 is no longer being actively developed / supported. 

We have been using Chronos as are scheduler with Apache Mesos, and are now in the process of porting over to DC/OS and while we experimented with using Metronome, Metronome is now being deprecated in favor of a non-yet-released folding of a scheduler into DC/OS or Marathon (not clear what / when the future is for that). 

In the meantime, we'd like to use Chronos! I finally am starting to get a picture of the v3 vs v2.5 releases, but I'm a bit nervous, and I realize that there is no real milestone or timeline in the github repo for v2. 

Is v2 now the branch that is being supported actively and will be in the future? 

Thanks. 

-Yuki

[Judith Malnick]

Hi Yuki,

 

Good questions. 

If you don't want to change your jobs framework yet or need features that aren't in Metronome, we suggest that you use the 2.5.x version of Chronos. Mesosphere isn't actively developing it anymore, but we're accepting PRs and being careful not to break the functionality that's already there. There may eventually be more 2.5.x releases, depending on how many contributions we get and how long it takes us to consolidate jobs solutions. 

Chronos 3.0 introduced new functionality, but also some breaking changes that were a big problem for some users. We aren't planning on going further with the 3.0 branch, and aren't recommending that people rely on it. 

We do also have users running jobs with Metronome, and since there isn't any concrete plan for its eventual replacement, that is quite a ways off. I wouldn't hesitate to use it if it has all the features you need. 

Hope this helps! 

Judith 

--
You received this message because you are subscribed to the Google Groups "chronos-scheduler" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chronos-scheduler+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Judith Malnick

Community Manager

310-709-1517