Re: Apache Mesos Logo for MesosCon Stickers

Hi Tomek Thanks for the response. The main thing I need is just a pdf version of the Mesos logo. I do a lot of the ordering on behalf of the ASF for stickers and promotional giveaways for Apache events such as ApacheCon. As the ASF will be having a booth at MesosCon Europe I'd like to have some

Re: Adding the limited resource to TaskStatus messages

Is it correct to say that the limited resource field is *only* meant to provide machine readable information about what resources limits were exceeded? If so, does it make sense to provide richer reporting fields for all failure reasons? I imagine other failure reasons could benefit from being abl

Re: Updating running tasks in-place

--- Jiang Yan Xu | @xujyan On Wed, Oct 4, 2017 at 11:50 AM, Zhitao Li wrote: > Thanks for taking the lead, Yan! Replying to your points inline: > > On Wed, Oct 4, 2017 at 11:11 AM, Yan Xu wrote: > > > Hi Mesos users/devs, > > > > I am curious about what use cases d

Re: Adding the limited resource to TaskStatus messages

> On Oct 9, 2017, at 1:27 PM, Vinod Kone wrote: > >> In the case that a task is killed because it violated a resource >> constraint (ie. the reason field is REASON_CONTAINER_LIMITATION, >> REASON_CONTAINER_LIMITATION_DISK or REASON_CONTAINER_LIMITATION_MEMORY), >> this field may be populated wit

Re: Adding the limited resource to TaskStatus messages

> In the case that a task is killed because it violated a resource > constraint (ie. the reason field is REASON_CONTAINER_LIMITATION, > REASON_CONTAINER_LIMITATION_DISK or REASON_CONTAINER_LIMITATION_MEMORY), > this field may be populated with the resource that triggered the > limitation. This is i

Re: organizing a "docathon"

Please see this doc for more details as well as ideas for documentation. Please add more yourself! On Wed, Oct 4, 2017 at 6:19 PM Benjamin Hindman wrote: > We've decided on Thursday 10/12! > > If you're inter

Re: Adding the limited resource to TaskStatus messages

+1 On Mon, Oct 9, 2017 at 10:56 AM, James Peach wrote: > Hi all, > > In https://reviews.apache.org/r/62644/, I am proposing to add an optional > Resources field to the TaskStatus message named `limited_resources`. > > In the case that a task is killed because it violated a resource > constraint

Re: Adding the limited resource to TaskStatus messages

Does it make sense to wrap the resources in a `Limitation` message in case we add new fields for it? --- Jiang Yan Xu | @xujyan On Mon, Oct 9, 2017 at 10:56 AM, James Peach wrote: > Hi all, > > In https://reviews.apache.org/r/62644/, I am proposing to add an option

Adding the limited resource to TaskStatus messages

Hi all, In https://reviews.apache.org/r/62644/, I am proposing to add an optional Resources field to the TaskStatus message named `limited_resources`. In the case that a task is killed because it violated a resource constraint (ie. the reason field is REASON_CONTAINER_LIMITATION, REASON_CONTAI

Re: Apache Mesos Logo for MesosCon Stickers

Hi I described the process of ordering Mesos Stickers here https://lists.apache.org/thread.html/932f8fd677ca5c1520e843f2166fbd76bc6bb3d603bd864aedb5eeed@%3Cuser.mesos.apache.org%3E Best Tomek pon., 9 paź 2017 o 16:01 użytkownik Sharan Foga napisał: > Hi > > My name is Sharan. I'm involved with

Apache Mesos Logo for MesosCon Stickers

Hi My name is Sharan. I'm involved with Apache Community Development and I'll be running the Apache Software Foundation booth at MesosCon Europe in Prague in a few weeks. The plan is to give away project stickers and various ASF swag – so if you are coming along then please feel free to drop

Fwd: Singularity failing to create Mesos slave on Rancher with RHEL 7 instances

Hi all, I'm trying to deploy Singularity ( which is a scheduler for running Mesos tasks ) on Rancher with a set of RHEL 7.3 (3.10.0) instances. Everything else works fine but the slave node keeps failing to start giving the following error. 10/9/2017 1:26: