Re: marathon bug(?)
On Mon, 28 Jun 2021, 20:41 Marc, wrote > > I think it's too late for that, your best bet is probably to pick a fork > > which is still maintained. > > Why late? Login accounts do not die not? Is not the right thing that > Qian Zhang gets control of accounts like https://github.com/apache/mesos, > https://github.com/mesosphere/marathon and > https://github.com/mesosphere/mesos-dns? > Accounts don't die but communities do - giving anyone control of accounts won't magically revive them. Also, from a diversification point of view having a single person in charge of all these is probably a bad idea - lack of diversification of probably one of the factors behind Mesos failure. Really, you'd be better off moving on :).
RE: marathon bug(?)
> There are now forks being created of mesos-dns and marathon to > update code. Maybe it is better to have these changes done on the > original repositories for now. > With whom can we discuss this to make this happen? > > > > I think it's too late for that, your best bet is probably to pick a fork > which is still maintained. Why late? Login accounts do not die not? Is not the right thing that Qian Zhang gets control of accounts like https://github.com/apache/mesos, https://github.com/mesosphere/marathon and https://github.com/mesosphere/mesos-dns?
Re: marathon bug(?)
Hi Marc, Here are the issue tracker and support info of Marathon: https://github.com/mesosphere/marathon/issues https://mesosphere.github.io/marathon/support.html You may want to report issues there, but I am not sure if D2IQ folks still maintains Marathon. Regards, Qian Zhang On Tue, Jun 22, 2021 at 3:50 PM Marc wrote: > > Where should marathon bugs be reported? > > I have switched from marathon 1.9 to 1.11.24 > > I have a task with dedicated ip address and I used to restart a such a > task via the gui by 'changing' the config and click something like 'change > and deploy'. > This 'change and deploy' is not working any more, it does nothing. > > PS. Choosing the restart does not work because the restart first creates a > new task and then kills the old, which of course never works with a > dedicated ip. (I reported this before) > > >