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

Hi Kevin Great initiative. Wanted to point out to earlier proposals on the topic: http://marc.info/?l=mesos-dev=144286256512205=2 -Jojy > On May 20, 2016, at 11:11 AM, Shivam Pathak wrote: > > Great! please add

Design doc: Securing Mesos Containers Using Capabilities

Hi all, As Mesos is adding more features to its Unified Containerizer[1], ability to run Mesos containers in a secure environment has been one of the top priorities. As an initial step, we could use Posix capabilities[2] to create a secure sandbox to run the Mesos containers.

Re: [DISCUSS] Fetching Docker Images Requiring User Credentials.

Have we considered provisioning SSL certs and keys as a separate step (isolation maybe)? This could mean mounting “.ssl” volume inside the container for example. -Jojy > On Mar 15, 2016, at 11:18 AM, Avinash Sridharan wrote: > > Why not follow option 2, but instead of

Re: Making 'curl' a prerequisite for installing Mesos

+1 On Thu, Mar 3, 2016 at 12:52 PM Jake Farrell wrote: > +1 > > -Jake > > On Thu, Mar 3, 2016 at 12:10 PM, Jie Yu wrote: > > > Hi, > > > > I am proposing making 'curl' a prerequisite when installing Mesos. > > Currently, we require 'libcurl' being

Re: Mesos binaries and shared library dependencies.

Maybe have an opt-in (say —with-rpath)? -Jojy > On Feb 12, 2016, at 2:19 PM, Kevin Klues wrote: > > To be clear, I'm actually a bit torn both ways on this. > > On the one hand, including the rpath makes it easy for those who don't > know anything about LD_LIBRARY_PATH, the

Re: Inconsistent naming of support scripts

hyphen++. Is google friendly apparently. Also less keys to press :) -Jojy > On Feb 11, 2016, at 12:43 PM, Greg Mann wrote: > > +1 > > On Thu, Feb 11, 2016 at 11:41 AM, Vinod Kone wrote: > >> Some the scripts in the "support" directory have

Re: MESOS-4581 Docker containers getting stuck in staging.

Hi Travis Thanks for narrowing down the issue. I had a brief look at your patch and it looks like it relies on adding delay before inspect is called. Although that might work mostly, I am wondering if that is the right solution. It would be better if we can have a timeout (using ‘after’ on the

Re: tasks not being scheduled; cfs_rq for /mesos is missing

eriod_us: > 10 > cpu.shares: > 18432 > cpu.stat: > nr_periods 680868 > nr_throttled 254025 > throttled_time 55400010353125 > tasks: > 6473 > ... > > - Erik > > On Sun, Jan 3, 2016 at 10:38 AM, Jojy Varghese <j...@mesospher

Re: tasks not being scheduled; cfs_rq for /mesos is missing

PM, Erik Weathers <eweath...@groupon.com.INVALID> > wrote: > > hey Jojy, Thanks for your reply. Response inline. > > On Thu, Dec 31, 2015 at 11:31 AM, Jojy Varghese <j...@mesosphere.io> wrote: > >>> Are /foo/bar cgroups hierarchical such that /foo miss

Re: tasks not being scheduled; cfs_rq for /mesos is missing

> Are /foo/bar cgroups hierarchical such that /foo missing would prevent > /foo/bar tasks from being scheduled? i.e., might that be the root cause of > why the kernel is ignoring these tasks? Was curious why you said the above. CPU scheduling shares are a function of their parent’s CPU

Re: Injecting data into mesos container

Although its not possible today directly using Mesos, we could always use “nsenter” to enter the container namespace and do things. I haven’t tried it myself but conceptually thats the way to do it. -Jojy > On Nov 28, 2015, at 3:30 AM, Sargun Dhillon wrote: > > You can do

Re: Configuration file?

Thanks for bringing this topic up Alex. I have been thinking about the same and was wondering if we can have subsystem specific flags and some scheme where there can be a namespace instead of a flat space. And as alex suggested, a configuration to represent this? -jojy On Mon, Nov 23, 2015 at

Re: libprocess: ordered message delivery

Ordering in distributed systems is usually a best-effort and only primitive that is required is “happen-before”. I have seen “happen-before” sequencing being implemented in distributed systems using “barriers”. DRBD is a good example of such a system. Another example of that model is the block

Re: Add JIRA ticket# to `TODO`s in comments

If we are going to track these TODOs on JIRA, I hope we add these as sub-tasks to the stories/epics and are not floating free. Which brings the question - how are epic completion timelines effected by these. -Jojy > On Nov 11, 2015, at 9:39 AM, Greg Mann wrote: > > +1 >

Re: Better error reporting in Mesos

I think having recently been through the libprocess “continuations” and callbacks, we do lack a pattern that logs errors that have full context. For example, we don’t have a pattern of logging at “onFailed’/“onDiscarded” sites at each layer of the call stack. What this leads to is a top level

Re: Agent with External Containerizer ignores mesos.internal.RunTaskMessage

Saw this on master log around the time slave was receiving KillTaskMessage: hierarchical.hpp:1326] No resources available to allocate! -Jojy > On Oct 19, 2015, at 9:05 AM, Łukasz Adamczyk wrote: > > Hello, > > TL;DR; > > I have odd problem with Mesos Agent +

Re: Community Sync Interval

+1 bi-weekly > On Oct 15, 2015, at 5:42 PM, Isabel Jimenez > wrote: > > +1 for bi-weekly > > On Thu, Oct 15, 2015 at 4:18 PM, Alex Rukletsov wrote: > >> +1 for bi-weekly. >> >> On Fri, Oct 16, 2015 at 12:50 AM, Elizabeth Lingg

Re: Working Group List

l free to start a separate thread about any > difficulties you're observing that you'd like the dev community to discuss. > > On Mon, Sep 21, 2015 at 3:12 PM, Jojy Varghese <j...@mesosphere.io > <mailto:j...@mesosphere.io>> wrote: > >> Hi Ben >> The ear

Re: Working Group List

you start a thread about the difficulties so that we can > explore them further? > > I just want to avoid hijacking this thread as these should be discussed > independently. I will share my thoughts there, as I'm sure others will :) > > On Wed, Sep 23, 2015 at 4:54 PM, Jojy Varghese

Re: Working Group List

pm> > > It would be great if you could highlight some differences between what we > have now and your proposal, thanks! > > Ben > > On Mon, Sep 21, 2015 at 12:09 PM, Jojy Varghese <j...@mesosphere.io > <mailto:j...@mesosphere.io>> wrote: > >> Proposing a sub

Re: Working Group List

Proposing a subsystem-specific-maintainer model. Subsystem Specific Maintainers Problem statement As Mesos project grows in terms of subsystems, features and contributors, it becomes harder to scale development and maintenance without a model. To list a few problems: -