Thanks Ben.M for initiative.
You already define the scarce resource and describe the problem clearly.
Just recap the requirements we want to resolved as follows
1) Scarce resource should not be treated as dominated resource during
allocating so that user could continue using non-scarce resource
"Porting Mesos on Power" (Mesos 4312) was one of the near term projects in
the first version, but now is removed. I would like to add it back, however
failed. I have an account there but seem still cannot edit it.
Besides, how does Mesos support Swarm on Mesos after "Deprecate Docker
Thanks Till
Yong
On Sun, Aug 16, 2015 at 6:44 AM, Till Toenshoff toensh...@me.com wrote:
Hey Yong,
added you as a contributor.
Till
On Aug 16, 2015, at 7:53 AM, Yong Feng fengyong...@gmail.com wrote:
Forget to mention, my JIRA ID is luckyfengyong
Thanks,
Yong
On Sat
Forget to mention, my JIRA ID is luckyfengyong
Thanks,
Yong
On Sat, Aug 15, 2015 at 10:25 AM, Yong Feng fengyong...@gmail.com wrote:
Hi Team,
I would like to be added as a contributor for future contribution to
Mesos. Please give a help.
Thanks,
Yong
Hi Team,
I would like to be added as a contributor for future contribution to Mesos.
Please give a help.
Thanks,
Yong
to shrink the number of slaves,
and mesos seems to be in the best position to orchestrate such a process if
you want do this based on framework's SLA constraints (would re-use inverse
offers).
On Sun, Aug 2, 2015 at 5:35 PM, Yong Feng fengyong...@gmail.com wrote:
I prefer an auto-scaler
I prefer an auto-scaler outside mesos as well. As long as Mesos exports
enough statistics, an outside auto-scaler should be able to make the
auto-scale decision as smart as Mesos itself. It will also help to douple
the resource scheduilng from resource infrastructure management. Mesos just
need
Hi Klaus
I assume you would like to learn how Mesos is designed and implemented
feature by feature through design doc of Epic. If that is that case, you
could start with https://github.com/apache/mesos/tree/master/docs which
describes Mesos overall architecture, func spec of main features,