+1
> On Apr 24, 2018, at 11:41 AM, Brandon Gulla wrote:
>
> Possible, maybe, the right thing to do? Probably not.
>
> There are multiple container orchestration platforms these days, and the
> pecking order is k8s -> mesos -> yarn. DC/OS has already implemented
>
Possible, maybe, the right thing to do? Probably not.
There are multiple container orchestration platforms these days, and the
pecking order is k8s -> mesos -> yarn. DC/OS has already implemented
support for kubernetes, but purely because it is seeing k8s as a competitor
and Mesosphere desires to
Probably you are right, however thinking that we have Apache Mesos as
coarse-grained scheduling, and generally we run at least one
fine-grained "general purpose" or "meta-scheduler" such as Marathon,
Aurora or even Kubernetes as framework. Why not apply the same
rationale for Myriad, YARN as
Are you suggesting using Myriad as meta-scheduler for Mesos?
If yes, then:1. Why would one need Mesos or Myriad at all - use YARN for
everything?2. Mesos scheduler is much more robust then YARN scheduler as it's
based on the offers - it was done having multiple subsystems in mind unlike YARN
Hi!
Thinking a little more deeply this YARN feature (Hadoop YARN Service
framework) could affect Apache Myriad regarding new development goals.
Apache Myriad based on YARN 3.x could be a possible substitute for
general purpose meta-scheduling Mesos frameworks such as Marathon or
Apache Aurora.