Marathon is still being developed as an open source Mesos framework. The _UI_ is going to stall out a bit, but it's just the UI.
Chronos is still being developed, but Mesosphere is taking Metronome and folding it into Marathon, making it more like Aurora. Moreover there's Singularity, PaaSTA, and a whole lot more:
Yes, DC/OS is intended to be a (mostly) full stack, but even then, it's still just Mesos under the hood and you can run any Mesos framework on it. The open source edition of DC/OS is fairly full featured, while the enterprise version gives you better account security, networking and integrated secrets (vault) support.
Mesosphere official github repo: "we aren’t planning on updating the old UI further"
Jaaron: "The _UI_ is going to stall out a bit, but its just the UI."
My options are:
a) running latest marathon backend without the user interface
b) running latest marathon backend and clone/maintain the user interface
c) migrate the whole thing to enterprise DC/OS (since I need authentication)
d) migrate to K8s
I view the lack of option "(e) keep using marathon-the-product as it is now", as a breach of trust, so (c) is off the table (whereas, before, it was my expected endpoint). YMMV.
We have to support the company first which has a more integrated solution that actually has to make money at the end of the day. We are also a pretty damn small team with a huge backlog to deliver, so it sucks that we had to abandon the UI outside of DCOS. We hope that the components of the DCOS UI for marathon can become the native UI for marathon, but again, it's a balance of priorities.
Marathon by itself has a lot more coming in the future, some will be restricted to DCOS, but not everything, it's a balancing act. Given our history of changing course publicaly (I wasn't involved in these decisions), I'm waiting to share our plans for 1.5 until I'm confident we're committing to them.
I think that's even more scary. You're confirming that you've halted development on the Marathon-UI-for-Mesos because you are resource constrained. I've got a working Mesos+Marathon cluster. The marathon part is now a dead-end, but more importantly, I now know that dead-ending a user is an option for Mesosphere: and its either because Mesosphere doesn't care, or because it does care, but is so resource constrained that it has no choice. Either option is a huge red-flag.
I wish you had forked it. If you're resource constrained and need to meet goals for LargeCorp, then fork the entire front-end/back-end. The approach of just ditching the UI half of the app while you iterate the same backend but with the DC/OS UI is really what's causing the grief here.
>Dear Marathon Community,
...
>Because of our focus on integrating the experience of using Marathon and DC/OS, we aren’t planning on updating the old UI further.
And by "old UI" they mean the one that works without DC/OS.
So there is no Apache Mesos + Marathon. There's Mesos. With no actively developed frameworks (Chronos is dead too). And then there's DC/OS.