Re: Mesos-4788: Looking for a shephard

[haosdent]

I could help review. :-)

On Fri, May 20, 2016 at 8:27 AM, Deshna Jain  wrote:

> Hi,
>
> I am looking for a shephard for the following issue:
>
> Issue Mesos-4788  (Mesos
> UI should show role and principal of a framework)
> Can anyone help?
>
> Thanks
>



-- 
Best Regards,
Haosdent Huang

Mesos-4788: Looking for a shephard

[Deshna Jain]

Hi,

I am looking for a shephard for the following issue:

Issue Mesos-4788  (Mesos
UI should show role and principal of a framework)
Can anyone help?

Thanks

Re: volume / mount point error with Unified Containerizer

[Olivier Sallou]

- Mail original -
> De: "Gilbert Song" 
> À: "dev" 
> Envoyé: Jeudi 19 Mai 2016 01:57:16
> Objet: Re: volume / mount point error with Unified Containerizer
> 
> @Olivier,
> In mesos 0.28.1, you are supposed to be able bind mount a volume from
> the host into the mesos container. Did you specify a docker image (we
> determine
> the mount point differently depending whether the container has a rootfs)?

Yes I specified an image, a Docker image URI.

> How
> do you specify your 'container_path' (the mount point in the container)? If
> it is an
> absolute path, we require that dir to be pre-existed. If it is a relative
> path, we will
> mkdir for it.

It is an absolute path, but it does not exists in image (this is the issue). 
Images are custom Docker images (images containing tools for batch computing), 
and I want, for example, to mount some shared resources (user home dir, common 
data, etc.) in the image. Of course those directories do not pre-exists in 
container images as they are specific to the environment. Requiring existence 
of the directory in the image is not issue as it prevents using any existing 
image from a repo.

When using Docker containerizer it works fine, I can mount any external storage 
in the container.

Olivie


> 
> @Joshua,
> Thank for posting your workaround on mesos. As I mentioned above, in 0.28.1
> or
> older, we only mkdir for container_path which is relative path (not
> starting with "/").
> Because if no rootfs specified for a mesos container, the container shares
> the host
> root filesystem. Obviously we don't want any random files to be created
> implicitly
> on your host fs.
> From mesos 0.29 (release by the end of this month), we will mkdir the mount
> point in the container except for the command task case that specify an
> absolute
> container_path without a rootfs. Because we simplify the mounting logic, and
> sandbox bind mount will only be done in container mount namespace instead of
> host mount namespace (what we did before). Please keep tuned.
> 
> Cheers,
> Gilbert
> 
> On Wed, May 18, 2016 at 8:14 AM, Joshua Cohen  wrote:
> 
> > Hi Olivier,
> >
> > I touched on this issue as part of
> > https://issues.apache.org/jira/browse/MESOS-5229. It would be nice if
> > Mesos
> > automatically created container mount points if they don't already exist.
> > In the meantime, as a workaround for this, I've updated my filesystem
> > images to include the path (e.g. in Dockerfile, add `RUN mkdir -p
> > /some/mount/point`). Not the best solution, but the only thing I've seen
> > that works at the moment.
> >
> > Cheers,
> >
> > Joshua
> >
> > On Wed, May 18, 2016 at 7:36 AM, Guangya Liu  wrote:
> >
> > > It's pretty simple for you from scratch with source code
> > >
> > >
> > https://github.com/apache/mesos/blob/master/docs/getting-started.md#building-mesos
> > > ;-)
> > >
> > > Thanks,
> > >
> > > Guangya
> > >
> > > On Wed, May 18, 2016 at 8:30 PM, Olivier Sallou  > >
> > > wrote:
> > >
> > > >
> > > >
> > > > On 05/18/2016 02:31 PM, Guangya Liu wrote:
> > > > > Just saw that you are working with 0.28.1, the "docker volume driver"
> > > > code
> > > > > was not in 0.28.1, can you please have a try with mesos master branch
> > > if
> > > > > you are only doing some test?
> > > > this is indeed test only for the moment. But I will have to
> > > > recompile/install mesos  :-(  (I used packages for install).
> > > >
> > > > I will try when possible, but thanks for the hint.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Guangya
> > > > >
> > > > > On Wed, May 18, 2016 at 8:28 PM, Guangya Liu 
> > > wrote:
> > > > >
> > > > >> Hi Olivier,
> > > > >>
> > > > >> I think that you need to enable "docker volume isolator" if you want
> > > use
> > > > >> external storage with unified container I was writing a document
> > here
> > > > >> https://reviews.apache.org/r/47511/, perhaps you can have a try
> > > > according
> > > > >> to the document and post some comments there if you find any issues.
> > > > >>
> > > > >> Also you can patch mesos-execute here
> > > > https://reviews.apache.org/r/46762/ to
> > > > >> have a try with mesos-execute.
> > > > >>
> > > > >> Thanks,
> > > > >>
> > > > >> Guangya
> > > > >>
> > > > >> On Wed, May 18, 2016 at 7:17 PM, Olivier Sallou <
> > > > olivier.sal...@irisa.fr>
> > > > >> wrote:
> > > > >>
> > > > >>> Answering (partially) to myself.
> > > > >>>
> > > > >>> I seems issue is container_path does not exists inside container.
> > On
> > > > >>> Docker, path is created and mounted. With pure mesos,
> > container_path
> > > > >>> must exists.
> > > > >>>
> > > > >>> mesos.proto says: "If the path is an absolute path, that path must
> > > > >>> already exist."
> > > > >>>
> > > > >>> This is an issue however, using Docker images, the path I want to
> > > mount
> > > > >>> does not exists, and it cannot be 

Re: MESOS-3777: Looking for a shepherd

[Anand Mazumdar]

Hi Jose,

Would you like to work on https://issues.apache.org/jira/browse/MESOS-5359 
 instead? It’s part of the 
Scheduler API v1 improvements 
 epic.

-anand

> On May 19, 2016, at 12:40 PM, José Guilherme Vanz  
> wrote:
> 
> Ok. Do you think I should work on other issue in the roadmap?
> 
> On Thu, 19 May 2016 at 01:18 Vinod Kone  wrote:
> 
>> Hi Jose,
>> 
>> I'm shepherding this epic. Given the complexity of MESOS-3777, I think it
>> is best to move it to Phase 2.
>> 
>> On Wed, May 18, 2016 at 8:00 PM, José Guilherme Vanz <
>> guilherme@gmail.com> wrote:
>> 
>>> Hi guys
>>> 
>>> I'm looking for shepherd in the issue that is in the roadmap:
>>> MESOS-3777: Replace Master/Slave Terminology Phase I - Modify public
>>> interfaces 
>>> 
>>> Thanks
>>> 
>> 

Re: MESOS-3777: Looking for a shepherd

[José Guilherme Vanz]

Ok. Do you think I should work on other issue in the roadmap?

On Thu, 19 May 2016 at 01:18 Vinod Kone  wrote:

> Hi Jose,
>
> I'm shepherding this epic. Given the complexity of MESOS-3777, I think it
> is best to move it to Phase 2.
>
> On Wed, May 18, 2016 at 8:00 PM, José Guilherme Vanz <
> guilherme@gmail.com> wrote:
>
> > Hi guys
> >
> > I'm looking for shepherd in the issue that is in the roadmap:
> > MESOS-3777: Replace Master/Slave Terminology Phase I - Modify public
> > interfaces 
> >
> > Thanks
> >
>

Re: mesos git commit: Removed deprecated annotation for values in a protobuf enum.

[Neil Conway]

Do we need to be source-compatible with protobuf 2.5? If so, why?

Neil

On Wed, May 18, 2016 at 11:15 PM,   wrote:
> Repository: mesos
> Updated Branches:
>   refs/heads/master b7e50fe8b -> 4248b3c3a
>
>
> Removed deprecated annotation for values in a protobuf enum.
>
> Support for deprecated annotation for enums was added in protobuf 2.6.
> Since we should be compatible with 2.5, refrain from using the
> feature.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
> Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/4248b3c3
> Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/4248b3c3
> Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/4248b3c3
>
> Branch: refs/heads/master
> Commit: 4248b3c3a1cbfdf3bef2bebc401cca55407f2b87
> Parents: b7e50fe
> Author: Alexander Rukletsov 
> Authored: Wed May 18 23:14:47 2016 +0200
> Committer: Alexander Rukletsov 
> Committed: Wed May 18 23:14:47 2016 +0200
>
> --
>  include/mesos/authorizer/authorizer.proto | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/mesos/blob/4248b3c3/include/mesos/authorizer/authorizer.proto
> --
> diff --git a/include/mesos/authorizer/authorizer.proto 
> b/include/mesos/authorizer/authorizer.proto
> index b0d9f79..911a227 100644
> --- a/include/mesos/authorizer/authorizer.proto
> +++ b/include/mesos/authorizer/authorizer.proto
> @@ -61,8 +61,8 @@ enum Action {
>// TODO(zhitao): Remove the following two actions at the end of
>// the deprecation cycle which started with 0.29. They will be
>// fully replaced by `UPDATE_QUOTA_WITH_ROLE`.
> -  SET_QUOTA_WITH_ROLE = 8 [deprecated = true];
> -  DESTROY_QUOTA_WITH_PRINCIPAL = 9 [deprecated = true];
> +  SET_QUOTA_WITH_ROLE = 8;  // [deprecated = true];
> +  DESTROY_QUOTA_WITH_PRINCIPAL = 9;  // [deprecated = true];
>
>UPDATE_WEIGHTS_WITH_ROLE = 10;
>GET_ENDPOINT_WITH_PATH = 11;
>