Hacker News Reader

Comment by lordlarm | Hacker News Reader

Are there many of you actually using Chronos in production? I'm not sold that this project will still be with us in a couple of years..

I'm not saying the idea is bad, but comparing the developer community of Marathon with Chronos you see some obvious differences in commits, developers, issues (and responses), releases etc.

We've been using it in conjunction with Marathon and Mesos, and my impression is that it's a now half-dead project riddled with bugs (especially in the web UI) and I'm unsure whether we should invest more resources and infrastructure around this project.

Aurora does look interesting. But Apache doesn't have a much better reputation, and I'm not particularly keen on going away from Marathon. Any DevOps engineers with container/mesos infrastructures wanting to chime in?

View on HN

Hi, Chronos Product Manager here ('air' on github). Status: Having fun creating issues in the wake of the Jepsen post : )

I can say that Mesosphere is 100% committed to both Marathon and Chronos. You're right that Marathon gets more attention for the moment, but we have grand plans for both.

A strength of Mesos is that it's an open platform. If Chronos isn't right for you, there are solid alternatives. I'd appreciate if you raise issues against Chronos though so we can improve it : )

Excuse the plug, but if you'd like to help us improve these widely-used frameworks we'd love to hear from you: https://mesosphere.com/careers/

Have a look at Lattice (http://lattice.cf), which is extracted from Cloud Foundry.

Disclaimer: I work for Pivotal (in Labs), which donates the largest chunk of engineering effort to Cloud Foundry, including the Lattice team.

Looks like a very interesting project which I'll keep a keen eye on. We're probably not ready to switch our entire stack from Mesos to Lattice though, especially considering you're missing some important bits such as external service discovery etc. (by the looks of it) We're currently doing Marathon on Mesos with gliderlabs/registrator which syncs Docker and Consul - and then we're using consul-template + HAProxy for exposing applications externally. Works quite nice.

The differences (and advantages) between Lattice and Mesos could've been made clearer too I guess, although your docs and FAQs are quite nice.

If you want the full stack, you go from Lattice to Cloud Foundry. It gives you service injection, logging, routing and a bunch of other stuff I forget right now.

And it doesn't require you to build your own snowflake PaaS, which you'll be married to forever at your own expense.

I've worked on CF so I'm biased in its favour. But my actual paying job is helping clients to deliver user value. Tinkering around with various tools is fun, but it's not delivering user value.

Typing

    cf push app-name

Is.

And it works. It just plain old works. That makes my life 100x easier.

Would love to get your feedback on the Singularity framework: https://github.com/HubSpot/Singularity

Currently in use at HubSpot, OpenTable, Groupon (last I heard) and EverTrue.

Reply on news.ycombinator.com