> On Jun 6, 2016, at 10:18 AM, Rob Nagler wrote:
>
> Ralph,
> FWIW: I haven’t seen it before.
>
> Good to know.
>
>
> Not sure I understand the issue, but I have no knowledge of Jupyter or why
> you are using it. From what I can see, it appears that your choice of tools
> may be complica
Ralph,
> FWIW: I haven’t seen it before.
>
Good to know.
>
> Not sure I understand the issue, but I have no knowledge of Jupyter or why
> you are using it. From what I can see, it appears that your choice of tools
> may be complicating your solution - I’d suggest perhaps focusing on solving
> t
> On Jun 6, 2016, at 8:32 AM, Rob Nagler wrote:
>
> Thanks, John. I sometimes wonder if I'm the only one out there with this
> particular problem.
FWIW: I haven’t seen it before.
>
> Ralph, thanks for sticking with me. :) Using a pool of uids doesn't really
> work due to the way cgroups/con
Thanks, John. I sometimes wonder if I'm the only one out there with this
particular problem.
Ralph, thanks for sticking with me. :) Using a pool of uids doesn't really
work due to the way cgroups/containers works. It also would require
changing the permissions of all of the user's files, which wou
That's why they have acl in ZoL, no?
just bring up a new filesystem for each container, with acl so only
the owning container can use that fs, and you should be done, no?
To be clear, each container would have to have a unique uid for this
to work, but together
Is this really required here ?
I was under the impression the web server already run user tasks in a
container.
all tasks run with the same unix id, but that is fine since isolation is
provided by the container.
did I get it right ?
I was thinking of an other approach, which is run the containers
Perhaps it would help if you could give us some idea of the interest here? The
prior Mesos integration was done as an academic project, which is why it died
once the student graduated.
Is there some long-term interest here? Or is this part of an academic effort?
> On Jun 5, 2016, at 7:22 PM, R
Thought about this some more, and I wonder if there isn’t a simpler solution:
* create a worker pool of userid’s that represents the maximum number of
simultaneous users you are willing to support. This could be very large, if you
want
* when a worker id becomes available, pull the next email f
Rob, I am not familair with wakari.io
However what you say about the Unix userid problem is very relevant to many
'shared infrastructure' projects and is a topic which comes up in
discussions about them.
Teh concern there is, as you say, if the managers of the system have a
global filesystem, with
