containers should probably have one recommended model and if that does
not satisfy there are ways to achieve it.
Thx
From: Yan Xu <xuj...@apple.com>
To: dev <dev@mesos.apache.org>
Sent: Wednesday, June 21, 2017 11:29 AM
Subject: Re: [Proposal] Multiple Containers in Singl
Thanks for the proposal! Sorry about the late reply on this.
My take on this is: we should avoid introducing APIs that allow folks to do
the same thing using different ways. Looks like the proposal here would
allow frameworks to launch pod like workload in different ways (via
TaskGroup or via
hi zhitao,
in task definition, on task only one instance, you introduce multiple
containers it broke the defined convention, need more committer comments.
2017-06-19 23:46 GMT+08:00 Zhitao Li :
> Hi Tommy,
>
> Are you suggesting to either replace Task with Pod, or adding
Hi Tommy,
Are you suggesting to either replace Task with Pod, or adding a new concept
of Pod? Former would be too destructive to users and I don't see enough
value. For adding new concept of pod: task has reliable status update and
are modeled all around in Mesos and I feel doing that for another
it looks like Pod. how about upgrade TASK to POD concept?
2017-06-16 23:57 GMT+08:00 Zhitao Li :
> Hi Ben,
>
> Thanks for reading the proposal. There are several motivations, although
> scalability is the primary one:
>
> 1) w.r.t. scalability, it's not only Mesos's own
Hi Ben,
Thanks for reading the proposal. There are several motivations, although
scalability is the primary one:
1) w.r.t. scalability, it's not only Mesos's own scalability, but also many*
additional infra tools* which need to integrate with Mesos and process
*every* task in the cluster: a 2-3x
>From reading this, the motivation is that TaskGroup having 1 task per
container "could create a scalability issue for a large scale Mesos cluster
since many endpoints/operations scale with the total number of Tasks in the
cluster."
Is that the only motivation here?
On Thu, Jun 15, 2017 at 11:45