[no subject]

2017-05-09 Thread Lasya Marla 
Resolved on my own!

Mistake in Error Message

2017-05-09 Thread Lasya Marla 
I  actually realized I made a mistake with the error message. The error I am 
seeing is 

Received status update TASK_FAILED for task 'something'
  message: 'Container exited with status 1'
  source: SOURCE_EXECUTOR

Docker Containerization on Mesos

2017-05-09 Thread Lasya Marla 
I am trying to run a simple hello_world image on my agent. I started my
master on my local machine like so.
./bin/mesos-agent.sh --master=127.0.0.1:5050 --work_dir=/var/lib/mesos
--containerizers=docker,mesos

Then I started my agent like so.
./bin/mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos

Then I tried to execute a docker image command on my agent like so.
mesos-execute --ip=127.0.0.1:5050 --name=something --command=sleep
--containerizer=docker --docker_image=hello_world

I recieved the following error message

message: 'Failed to launch container: Failed to run 'docker -H
unix:///var/run/docker.sock pull hello_world:latest': exited with status 1;
stderr='Error response from daemon: repository hello_world not found: does
not exist or no pull access

I have docker running locally which is where the agent and master are
running as well so I am not sure what the issue is. I am on OSX and the
most recent versions of both docker and mesos.

Thanks

Re: [VOTE] Release Apache Mesos 1.3.0 (rc1)

2017-05-09 Thread Benjamin Mahler 
-1 (binding)

Two upgrade blockers, these need to be backported to 1.2.x as well:

https://issues.apache.org/jira/browse/MESOS-7478 (I have a patch already)
https://issues.apache.org/jira/browse/MESOS-7460 (mpark is working on this)

Re: MESOS-7378
Any updates on whether this will be fixed?

On Tue, May 9, 2017 at 1:02 AM, Jie Yu  wrote:

> -1
>
> I want to get this fix into 1.3.0
> https://issues.apache.org/jira/browse/MESOS-7471
>
> - Jie
>
> On Tue, May 9, 2017 at 1:14 AM, Yan Xu  wrote:
>
>> We work around autotools and protobuf bugs and glibc is only harder for
>> users and developers to upgrade. :)
>>
>> I agree that we can establish the minimum glibc version/linux distro
>> releases etc we support but currently we don't and there are folks who use
>> Mesos that depend on this version.
>>
>> We should follow http://mesos.apache.org/documentation/latest/versioning/
>> and when answers are not in there, we should seek consensus to improve the
>> process and update the doc and give folks adequate time to adjust to the
>> new or better defined) process. In the meantime, I think we shouldn't break
>> the current users.
>>
>> ---
>> Jiang Yan Xu  | @xujyan 
>>
>> On Mon, May 8, 2017 at 3:59 PM, Neil Conway 
>> wrote:
>>
>>> Personally, I'm not convinced that we need to fix MESOS-7378. The
>>> problem is essentially a bug in glibc that was fixed 6 years ago. (As
>>> a point of reference, the oldest version of g++ we support was
>>> released 2 years ago... :) )
>>>
>>> Neil
>>>
>>> On Mon, May 8, 2017 at 3:45 PM, Yan Xu  wrote:
>>> > I am still hoping that we get
>>> > https://issues.apache.org/jira/browse/MESOS-7378 fixed before shipping
>>> > 0.13.0. :)
>>> >
>>> > ---
>>> > Jiang Yan Xu  | @xujyan
>>> >
>>> > On Fri, May 5, 2017 at 6:31 PM, Michael Park  wrote:
>>> >>
>>> >> Hi all,
>>> >>
>>> >> Please vote on releasing the following candidate as Apache Mesos
>>> 1.3.0.
>>> >>
>>> >>
>>> >> 1.3.0 includes the following:
>>> >>
>>> >> 
>>> 
>>> >>   - Multi-role framework support
>>> >>   - Executor authentication support
>>> >>   - Allow frameworks to modify their roles.
>>> >>   - Hierarchical roles (*EXPERIMENTAL*)
>>> >>
>>> >> The CHANGELOG for the release is available at:
>>> >>
>>> >> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_p
>>> lain;f=CHANGELOG;hb=1.3.0-rc1
>>> >>
>>> >> 
>>> 
>>> >>
>>> >> The candidate for Mesos 1.3.0 release is available at:
>>> >> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc1/mesos
>>> -1.3.0.tar.gz
>>> >>
>>> >> The tag to be voted on is 1.3.0-rc1:
>>> >> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit
>>> ;h=1.3.0-rc1
>>> >>
>>> >> The MD5 checksum of the tarball can be found at:
>>> >>
>>> >> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc1/mesos
>>> -1.3.0.tar.gz.md5
>>> >>
>>> >> The signature of the tarball can be found at:
>>> >>
>>> >> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc1/mesos
>>> -1.3.0.tar.gz.asc
>>> >>
>>> >> The PGP key used to sign the release is here:
>>> >> https://dist.apache.org/repos/dist/release/mesos/KEYS
>>> >>
>>> >> The JAR is up in Maven in a staging repository here:
>>> >> https://repository.apache.org/content/repositories/orgapache
>>> mesos-1190
>>> >>
>>> >> Please vote on releasing this package as Apache Mesos 1.3.0!
>>> >>
>>> >> The vote is open until Wed May 10 11:59:59 PDT 2017 and passes if a
>>> >> majority of at least 3 +1 PMC votes are cast.
>>> >>
>>> >> [ ] +1 Release this package as Apache Mesos 1.3.0
>>> >> [ ] -1 Do not release this package because ...
>>> >>
>>> >> Thanks,
>>> >>
>>> >> MPark & Neil
>>> >
>>> >
>>>
>>
>>
>

RE: [Req]Starting Japan User Group

2017-05-09 Thread Kitayama, Shingo 

Hi Jie and members,

Thank you for your approval to create MUG in Tokyo.
At once we are just starting to extend values and make collaboration thr Mesos 
in Japan.
At the begging after making the first meetup clear, we will announce the detail 
to you.

Thanks

Shingo

[PointNext]
Services to Accelerate your Digital Transformation
by Hewlett-Packard Enterprise Japan, Ltd.

 〒136-8711 東京都江東区大島2丁目2番1号
テクノロジーコンサルティング事業統括
クロス・インダストリ・ソリューション統括本部
テクノロジーアーキテクト部 (EG TSC CIS TA)
 北山晋吾 Shingo.Kitayama (21958016)
TEL: 090-1269-8125
 Mail Stop: HQ5-B22
 Mailto:shingo.kitay...@hpe.com

From: Jie Yu [mailto:yujie@gmail.com]
Sent: Tuesday, May 9, 2017 4:53 PM
To: user 
Subject: Re: [Req]Starting Japan User Group

Shingo,

This is great! Can you send a pull request to update this doc?
https://github.com/apache/mesos/blob/master/site/source/community/user-groups.html.md

- Jie

On Tue, May 9, 2017 at 9:50 AM, Kitayama, Shingo 
> wrote:

Hi, owners of Mesos User Groups.

This is Shingo.Kitayama from Hewlett Packard Enterprise Japan Ltd.
I’m in charge of open source solution delivery including Apache Mesos or other 
cloud orchestration tools.

You may know that Hewlett Packard Enterprise announced the relationship with 
Mesosphere,
after that, I am giving high priority to convey to Japanese engineers the 
appeal of Mesos.

Additionally I and my team members are planning to held the Mesos Meetup in 
Tokyo and to extend its value continuously.
In this meetup, we will foster the adoption of Mesos, exchange tips or issues, 
and make up collaborative solutions with participants.
So could you approve to establish Japan User group at Tokyo? Of course we are 
going to form a commercial-free community group!

Best regards,
Shingo from Japan@Tokyo

[PointNext]
Services to Accelerate your Digital Transformation
by Hewlett-Packard Enterprise Japan, Ltd.

 〒136-8711 東京都江東区大島2丁目2番1号
テクノロジーコンサルティング事業統括
クロス・インダストリ・ソリューション統括本部
テクノロジーアーキテクト部 (EG TSC CIS TA)

北山晋吾 Shingo.Kitayama (21958016)
TEL: 090-1269-8125
 Mail Stop: HQ5-B22
 Mailto:shingo.kitay...@hpe.com

Re: [Req]Starting Japan User Group

2017-05-09 Thread Vinod Kone 
On Tue, May 9, 2017 at 8:10 AM, Kitayama, Shingo 
wrote:

> In Japan, usually engineers will take tech event information from
> CONNPASS, not from Meetup.com
>
> ※CONNPASS  https://connpass.com/ (Sorry all Japanese)
>
>
>
>
I think using whatever portal works for you is fine. If it's not too much
work though, I would suggest to create a meetup.com group as well and just
link to connpass event when you schedule meetups.

RE: [Req]Starting Japan User Group

2017-05-09 Thread Kitayama, Shingo 

Hi Tobias,

Thank you for your quick response.
Now we are adjusting schedule and place to held the first meetup.
But maybe it will be held in middle of June at near our office.
After decided, we announce you to the details.

In Japan, usually engineers will take tech event information from CONNPASS, not 
from Meetup.com
※CONNPASS  https://connpass.com/ (Sorry all Japanese)

So, do we need to make official TOKYO Mesos User Groups in Meetup.com ?
If possible, we’d like to manage the announcement for Japan event in CONNPASS.
CONNPASS portal can manage owner and users in created groups.

Thanks.

[PointNext]
Services to Accelerate your Digital Transformation
by Hewlett-Packard Enterprise Japan, Ltd.

 〒136-8711 東京都江東区大島2丁目2番1号
テクノロジーコンサルティング事業統括
クロス・インダストリ・ソリューション統括本部
テクノロジーアーキテクト部 (EG TSC CIS TA)
 北山晋吾 Shingo.Kitayama (21958016)
TEL: 090-1269-8125
 Mail Stop: HQ5-B22
 Mailto:shingo.kitay...@hpe.com

From: Tobias Pfeiffer [mailto:t...@preferred.jp]
Sent: Tuesday, May 9, 2017 5:12 PM
To: user@mesos.apache.org
Subject: Re: [Req]Starting Japan User Group

Hi Shingo,

On Tue, May 9, 2017 at 4:50 PM, Kitayama, Shingo 
> wrote:
Additionally I and my team members are planning to held the Mesos Meetup in 
Tokyo and to extend its value continuously.
In this meetup, we will foster the adoption of Mesos, exchange tips or issues, 
and make up collaborative solutions with participants.

Great news, happy to hear that!  I am very much interested in that, please let 
us know where the meetups will take place, how to register, etc. – thank you!

Kind regards,
Tobias

--
Tobias Pfeiffer, Lead Engineer
Preferred Networks Inc,

Re: [Req]Starting Japan User Group

2017-05-09 Thread Tobias Pfeiffer 
Hi Shingo,

On Tue, May 9, 2017 at 4:50 PM, Kitayama, Shingo 
wrote:
>
> Additionally I and my team members are planning to held the Mesos Meetup
> in Tokyo and to extend its value continuously.
>
> In this meetup, we will foster the adoption of Mesos, exchange tips or
> issues, and make up collaborative solutions with participants.
>

Great news, happy to hear that!  I am very much interested in that, please
let us know where the meetups will take place, how to register, etc. –
thank you!

Kind regards,
Tobias

-- 
Tobias Pfeiffer, Lead Engineer
Preferred Networks Inc,

Re: [VOTE] Release Apache Mesos 1.1.2 (rc1)

2017-05-09 Thread Jie Yu 
-1

I suggest we include this fix in 1.1.2
https://issues.apache.org/jira/browse/MESOS-7471

On Thu, May 4, 2017 at 12:07 PM, Alex Rukletsov  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.1.2.
>
> 1.1.2 includes the following:
> 
> 
> ** Bug
>   * [MESOS-2537] - AC_ARG_ENABLED checks are broken.
>   * [MESOS-5028] - Copy provisioner cannot replace directory with symlink.
>   * [MESOS-5172] - Registry puller cannot fetch blobs correctly from http
> Redirect 3xx urls.
>   * [MESOS-6327] - Large docker images causes container launch failures:
> Too many levels of symbolic links.
>   * [MESOS-7057] - Consider using the relink functionality of libprocess in
> the executor driver.
>   * [MESOS-7119] - Mesos master crash while accepting inverse offer.
>   * [MESOS-7152] - The agent may be flapping after the machine reboots due
> to provisioner recover.
>   * [MESOS-7197] - Requesting tiny amount of CPU crashes master.
>   * [MESOS-7210] - HTTP health check doesn't work when mesos runs with
> --docker_mesos_image.
>   * [MESOS-7237] - Enabling cgroups_limit_swap can lead to "invalid
> argument" error.
>   * [MESOS-7265] - Containerizer startup may cause sensitive data to leak
> into sandbox logs.
>   * [MESOS-7350] - Failed to pull image from Nexus Registry due to
> signature missing.
>   * [MESOS-7366] - Agent sandbox gc could accidentally delete the entire
> persistent volume content.
>   * [MESOS-7383] - Docker executor logs possibly sensitive parameters.
>   * [MESOS-7422] - Docker containerizer should not leak possibly sensitive
> data to agent log.
>
> The CHANGELOG for the release is available at:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_
> plain;f=CHANGELOG;hb=1.1.2-rc1
> 
> 
>
> The candidate for Mesos 1.1.2 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.1.2-rc1/mesos-1.1.2.tar.gz
>
> The tag to be voted on is 1.1.2-rc1:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.1.2-rc1
>
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.1.2-rc1/
> mesos-1.1.2.tar.gz.md5
>
> The signature of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.1.2-rc1/
> mesos-1.1.2.tar.gz.asc
>
> The PGP key used to sign the release is here:
> https://dist.apache.org/repos/dist/release/mesos/KEYS
>
> The JAR is up in Maven in a staging repository here:
> https://repository.apache.org/content/repositories/orgapachemesos-1188
>
> Please vote on releasing this package as Apache Mesos 1.1.2!
>
> The vote is open until Tue May 9 12:12:12 CEST 2017 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 1.1.2
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Alex & Till
>

Re: [VOTE] Release Apache Mesos 1.3.0 (rc1)

2017-05-09 Thread Jie Yu 
-1

I want to get this fix into 1.3.0
https://issues.apache.org/jira/browse/MESOS-7471

- Jie

On Tue, May 9, 2017 at 1:14 AM, Yan Xu  wrote:

> We work around autotools and protobuf bugs and glibc is only harder for
> users and developers to upgrade. :)
>
> I agree that we can establish the minimum glibc version/linux distro
> releases etc we support but currently we don't and there are folks who use
> Mesos that depend on this version.
>
> We should follow http://mesos.apache.org/documentation/latest/versioning/
> and when answers are not in there, we should seek consensus to improve the
> process and update the doc and give folks adequate time to adjust to the
> new or better defined) process. In the meantime, I think we shouldn't break
> the current users.
>
> ---
> Jiang Yan Xu  | @xujyan 
>
> On Mon, May 8, 2017 at 3:59 PM, Neil Conway  wrote:
>
>> Personally, I'm not convinced that we need to fix MESOS-7378. The
>> problem is essentially a bug in glibc that was fixed 6 years ago. (As
>> a point of reference, the oldest version of g++ we support was
>> released 2 years ago... :) )
>>
>> Neil
>>
>> On Mon, May 8, 2017 at 3:45 PM, Yan Xu  wrote:
>> > I am still hoping that we get
>> > https://issues.apache.org/jira/browse/MESOS-7378 fixed before shipping
>> > 0.13.0. :)
>> >
>> > ---
>> > Jiang Yan Xu  | @xujyan
>> >
>> > On Fri, May 5, 2017 at 6:31 PM, Michael Park  wrote:
>> >>
>> >> Hi all,
>> >>
>> >> Please vote on releasing the following candidate as Apache Mesos 1.3.0.
>> >>
>> >>
>> >> 1.3.0 includes the following:
>> >>
>> >> 
>> 
>> >>   - Multi-role framework support
>> >>   - Executor authentication support
>> >>   - Allow frameworks to modify their roles.
>> >>   - Hierarchical roles (*EXPERIMENTAL*)
>> >>
>> >> The CHANGELOG for the release is available at:
>> >>
>> >> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_p
>> lain;f=CHANGELOG;hb=1.3.0-rc1
>> >>
>> >> 
>> 
>> >>
>> >> The candidate for Mesos 1.3.0 release is available at:
>> >> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc1/mesos
>> -1.3.0.tar.gz
>> >>
>> >> The tag to be voted on is 1.3.0-rc1:
>> >> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit
>> ;h=1.3.0-rc1
>> >>
>> >> The MD5 checksum of the tarball can be found at:
>> >>
>> >> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc1/mesos
>> -1.3.0.tar.gz.md5
>> >>
>> >> The signature of the tarball can be found at:
>> >>
>> >> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc1/mesos
>> -1.3.0.tar.gz.asc
>> >>
>> >> The PGP key used to sign the release is here:
>> >> https://dist.apache.org/repos/dist/release/mesos/KEYS
>> >>
>> >> The JAR is up in Maven in a staging repository here:
>> >> https://repository.apache.org/content/repositories/orgapachemesos-1190
>> >>
>> >> Please vote on releasing this package as Apache Mesos 1.3.0!
>> >>
>> >> The vote is open until Wed May 10 11:59:59 PDT 2017 and passes if a
>> >> majority of at least 3 +1 PMC votes are cast.
>> >>
>> >> [ ] +1 Release this package as Apache Mesos 1.3.0
>> >> [ ] -1 Do not release this package because ...
>> >>
>> >> Thanks,
>> >>
>> >> MPark & Neil
>> >
>> >
>>
>
>

Re: [Req]Starting Japan User Group

2017-05-09 Thread Jie Yu 
Shingo,

This is great! Can you send a pull request to update this doc?
https://github.com/apache/mesos/blob/master/site/source/community/user-groups.html.md

- Jie

On Tue, May 9, 2017 at 9:50 AM, Kitayama, Shingo 
wrote:

>
>
> Hi, owners of Mesos User Groups.
>
>
>
> This is Shingo.Kitayama from Hewlett Packard Enterprise Japan Ltd.
>
> I’m in charge of open source solution delivery including Apache Mesos or
> other cloud orchestration tools.
>
>
>
> You may know that Hewlett Packard Enterprise announced the relationship
> with Mesosphere,
>
> after that, I am giving high priority to convey to Japanese engineers the
> appeal of Mesos.
>
>
>
> Additionally I and my team members are planning to held the Mesos Meetup
> in Tokyo and to extend its value continuously.
>
> In this meetup, we will foster the adoption of Mesos, exchange tips or
> issues, and make up collaborative solutions with participants.
>
> So could you approve to establish Japan User group at Tokyo? Of course we
> are going to form a commercial-free community group!
>
>
>
> Best regards,
>
> Shingo from Japan@Tokyo
>
>
>
> [image: PointNext] 
>
> Services to Accelerate your Digital Transformation
>
> by *Hewlett-Packard Enterprise Japan, Ltd*.
>
>
>
>  〒136-8711 東京都江東区大島2丁目2番1号
>
> テクノロジーコンサルティング事業統括
>
> クロス・インダストリ・ソリューション統括本部
>
> テクノロジーアーキテクト部 (EG TSC CIS TA)
>
>
>
> *北山晋吾** Shingo.Kitayama* (21958016)
>
> TEL: 090-1269-8125
>  Mail Stop: HQ5-B22
>  Mailto:shingo.kitay...@hpe.com
>
>
>

[Req]Starting Japan User Group

2017-05-09 Thread Kitayama, Shingo 

Hi, owners of Mesos User Groups.

This is Shingo.Kitayama from Hewlett Packard Enterprise Japan Ltd.
I’m in charge of open source solution delivery including Apache Mesos or other 
cloud orchestration tools.

You may know that Hewlett Packard Enterprise announced the relationship with 
Mesosphere,
after that, I am giving high priority to convey to Japanese engineers the 
appeal of Mesos.

Additionally I and my team members are planning to held the Mesos Meetup in 
Tokyo and to extend its value continuously.
In this meetup, we will foster the adoption of Mesos, exchange tips or issues, 
and make up collaborative solutions with participants.
So could you approve to establish Japan User group at Tokyo? Of course we are 
going to form a commercial-free community group!

Best regards,
Shingo from Japan@Tokyo

[PointNext]
Services to Accelerate your Digital Transformation
by Hewlett-Packard Enterprise Japan, Ltd.

 〒136-8711 東京都江東区大島2丁目2番1号
テクノロジーコンサルティング事業統括
クロス・インダストリ・ソリューション統括本部
テクノロジーアーキテクト部 (EG TSC CIS TA)

北山晋吾 Shingo.Kitayama (21958016)
TEL: 090-1269-8125
 Mail Stop: HQ5-B22
 Mailto:shingo.kitay...@hpe.com