Re: Join us at MesosCon 2018 next week!

tweet <https://twitter.com/mesosphere/status/1057692455456464897>). > > On Thu, Nov 1, 2018 at 10:33 AM Vaibhav Khanduja < > vaibhavkhand...@gmail.com> wrote: > >> Thanks for the email. >> >> Are there any promotional code available for enterprises? >>

Re: Join us at MesosCon 2018 next week!

Thanks for the email. Are there any promotional code available for enterprises? On Wed, Oct 31, 2018 at 5:06 PM Gastón Kleiman wrote: > MesosCon 2018 is taking place next week! Join us and celebrate the 5th > anniversary of MesosCon November 5th-7th, in the The Village (969 Market > St, San

Re: LibProcess on windows

> > provide > > you with the latest status. > > > > On Thu, Oct 18, 2018 at 1:48 PM Vaibhav Khanduja > > > > wrote: > > > >> Has anybody used libprocess outside of mesos on windows? Thx > >> >

LibProcess on windows

Has anybody used libprocess outside of mesos on windows? Thx

Mesos container on windows

I plan to use mesos container's for windows. Does any body has any production experience? Thx *Sent with Shift *

Re: MesosCon 2018 Location Change

+1 for bay area. Thx On Sat, Aug 25, 2018, 3:20 PM Jörg Schad wrote: > Just one more comment on the reasoning here: > We (i.e., the PC) want MesosCon to be a user-driven conference and hence > have the conference at a location where we can gather most users. > We understand it might be more

Re: Slack as the canonical chat channel

t; >>>>>>>> +1 For Slack >>>>>>>> On Jun 18, 2016 4:04 AM, "Vinod Kone" <vinodk...@apache.org> >>>> wrote: >>>>>>>> >>>>>>>>> Looks like people have jumped the gun he

Re: Slack as the canonical chat channel

gt;> > > > > > >> > > > > > The main reasons for using Slack/Hipchat are >> > > > > > >> > > > > >- In-client chat history >> > > > > >- Discoverability of work group speci

Re: Slack as the canonical chat channel

n reasons for using Slack/Hipchat are >> > > > > > >> > > > > >- In-client chat history >> > > > > >- Discoverability of work group specific channels >> > > > > >- Email notifications when offline &g

Re: Mesos working groups

+1 From: "Wong, Steven" Reply-To: Date: Thursday, June 16, 2016 at 11:36 AM To: "u...@mesos.apache.org" , mesos Subject: RE: Mesos working groups The existence of working groups on external volume

Re: Notification: Community Meeting @ Thu Jun 16, 2016 3pm - 4pm (Apache Mesos)

+ 1 slack Sent from my iPhone. Please excuse for typos and brevity of this message. > On Jun 16, 2016, at 6:46 PM, haosdent wrote: > > +1 For Slack. > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann wrote: >> >> Hello all, >> Here are the notes from

Re: [REVIEW PROCESS] Proposal for new review process working group

+1 I would also like to get added. Sent from my iPhone. Please excuse for typos and brevity of this message. > On May 20, 2016, at 6:10 PM, Guangya Liu wrote: > > +1, please count me in as well. > > Thanks, > > Guangya > > On Sat, May 21, 2016 at 2:11 AM, Shivam

Re: Design Doc for Containerizer Modularization

+1 Sent from my iPhone. Please excuse for typos and brevity of this message. > On May 15, 2016, at 5:36 PM, tommy xiao wrote: > > rocks > > 2016-05-14 0:54 GMT+08:00 haosdent : > >> Dear friends, >> >> I would like to bump this design document again to

Offers to a framework

For a use-case, we need to know offers been sent to a registered framework. For e.g. if we are using marathon as a framework, the master would send offers to it based on DRF as soon as a slave is available. The marathon would then accept the offer if it requires to start a job. Is there is way to

Re: Design Doc for Qemu/KVM containerizer

+1 lkvm should be taken as a separate activity ..prioritized based on it maturity .. On 4/11/16, 1:08 PM, "Du, Fan" wrote: >Thanks to bring *heavy* container to Mesos :) >I have a few comments as below: > >1. >One of reason adding Qemu/KVM is to support scenario where

Re: JIRA Shepherds

ell. How about having these guys as > > shepherds? > > > > At the end a committer may be required to sign off a project, but all the > > work of communicating with the contributor, come up with a design could > be > > lifter off from committers? > > > > What do

Re: JIRA Shepherds

The community is growing with more individuals getting interested in contributing to the project. This definitely brings an extra bit of workload for committers “Shepherds” but at the same time more developers eventually leads more adoptability across organization and enterprises. I am not sure

Re: Contribution Request

Current process makes sure bad code does not get in … though not sure of this swap ... On Fri, Jan 15, 2016 at 11:12 AM, Vinod Kone wrote: > We really need to swap steps 4 (well the assigning part) and 6 in the > "submitting > a patch

Re: Contribution Request

As per process, you need to get a shepherd. Easiest way to send an email to dev community requesting commiters .. On Fri, Jan 15, 2016 at 12:36 PM, Disha Singh wrote: > The documentation says "find a shepherd" but in the "create an issue" > option on JIRA one can

Re: GPGPU SLA support

What is your exact proposal? Having to use GPU as a sharable resource is definately beneficial. It would really makes sense, for any framework to control and schedule jobs, asking for GPU resources similar to sharable resources. Do you have a proposal of changes required (if) in Mesos? On Mon,

Re: Mesos Flocker - Custom Isolator and Docker

Does this not satisfy the usecase? -> https://github.com/ClusterHQ/mesos-module-flocker On Thu, Nov 26, 2015 at 3:26 AM, Timothy Chen wrote: > Hi Tommy, > > We didn't modify MesosContainerizer container creation but only just > added image support and the ability to inherit

Filesystem isolator test fail

On my build setup (using vagrant ubuntu), I am seeing filesystem isolator test fail with error message: E1107 05:24:47.878077 336 slave.cpp:3449] Container '9e31b321-bbc7-4914-b8d6-8a14aeb31985' for executor '162fa75a-18c5-4424-b0ff-6064279ac1e4' of framework

Remove top level CommandInfo::ContainerInfo protobuf message

Hello, Is anybody using CommandInfo::ContainerInfo protobuf message from Mesos 0.19? It was deprecated in Mesos 0.20 in favor of the top-level ContainerInfo message used as a field in TaskInfo/ExecutorInfo. As per MESOS-2315 we’d like to remove

Re: Community Sync Interval

+1 biweekly On Sun, Oct 18, 2015 at 6:32 PM, Alex Clemmer wrote: > (Sorry, just out of ignorance: is anyone allowed to come to the > community sync? I googled around and it looks like the answer is yes, > but I don't see a living schedule anywhere... If the answer

Re: Newbie question on checkpointing resource

Adam Thanks for your reply. I was wondering if you could share more details on the implementation of this falling into docker volumes? I see the code under checkPointResource is creating a volume path under sandbox. Do these checkpointed resource finally get added to Docker:ContainerInfo? If

Re: Any volunteers to be shepherd of MESOS-2875 (Add containerId to ResourceUsage to enable QoS controller to target a container)?

I can take this up ... On Wed, Sep 9, 2015 at 7:05 PM, Klaus Ma wrote: > Hi team, > > I'm working on MESOS-2875, any volunteers to be shepherd of this ticket? > Thanks in advance :). > > -- > Klaus Ma (马达), PMP® | http://www.cguru.net > >

Re: Any volunteers to be shepherd of MESOS-2875 (Add containerId to ResourceUsage to enable QoS controller to target a container)?

Sorry I read wrong .. I cannot be shepherd for the ticket .. On Wed, Sep 9, 2015 at 7:13 PM, Vaibhav Khanduja <vaibhavkhand...@gmail.com> wrote: > I can take this up ... > > On Wed, Sep 9, 2015 at 7:05 PM, Klaus Ma <kl...@cguru.net> wrote: > >> Hi team, >&g

Evaluate issue

https://issues.apache.org/jira/browse/MESOS-3392 Any shepard for this? Would like to understand what is wrong here

Newbie: Mesos issue

Hi I am looking at issue: https://issues.apache.org/jira/browse/MESOS-2863 marked as newbie. I would like to work on it and was wondering if somebody could Shepherd me on this? I believe code being talked here is the sleep in executor for e.g. in docker/executor.cpp - // A hack for now

Re: Newbie: Mesos issue

, Sep 4, 2015 at 10:00 AM, Vaibhav Khanduja > <vaibhavkhand...@gmail.com> wrote: > > Hi > > > > I am looking at issue: https://issues.apache.org/jira/browse/MESOS-2863 > > marked as newbie. I would like to work on it and was wondering if > somebody > > could