Re: [BULK]Re: [BULK]Call for active contributors

[Tomek Janiszewski]

I'm in
I can help with ARM CI, UI and some C++

czw., 4 mar 2021 o 16:04 Thomas Langé  napisał(a):

> Same for me, I'm available to share my knowledge and actively contribute
> to Mesos project.
>
> Thomas
> --
> *From:* Haijiang Chen 
> *Sent:* Thursday, 4 March 2021 16:01
> *To:* user@mesos.apache.org 
> *Cc:* mesos 
> *Subject:* [BULK]Re: [BULK]Call for active contributors
>
> I am willing to contribute to Mesos on windows based on my current
> experiences.
>
> - Haijiang
>
> On Thu, Mar 4, 2021 at 10:56 PM Grégoire Seux  wrote:
>
> Already answered to the other thread. I'm in.
>
> -- ​
> Grégoire
> --
> *From:* Qian Zhang 
> *Sent:* Thursday, March 4, 2021 3:38 PM
> *To:* mesos ; user 
> *Subject:* [BULK]Call for active contributors
>
> Hi folks,
>
> Please reply to this mail if you plan to actively contribute to Mesos and
> want to become a committer and PMC member in future.
>
>
> Regards,
> Qian Zhang
>
>

Re: Next Steps

[Tomek Janiszewski]

I think we can elect new committers. Currently we have 49 but most of them
have left the project long ago.
https://projects.apache.org/committee.html?mesos

czw., 18 lut 2021 o 18:18 Charles-François Natali 
napisał(a):

> Speaking as someone who contributed a few patches and would like to get
> more involved, I find it a bit difficult to get MRs reviewed and merged.
> I think it's probably because the current committers have other priorities
> now that D2iQ focus has shifted, which is understandable but makes it
> harder for outsiders to contribute.
> Is there anything which could be done about that?
>
> Cheers,
>
>
>
> On Thu, 18 Feb 2021, 14:30 Qian Zhang,  wrote:
>
>> Hi Vinod,
>>
>> I am still interested in the project. As other folks said, we need to
>> have a direction for the project. I think there are still a lot of Mesos
>> users/customers in the mail list, can you please send another mail to
>> collect their requirements / pain points on Mesos, and then we can try to
>> set up a roadmap for the project to move forward.
>>
>>
>> Regards,
>> Qian Zhang
>>
>>
>> On Thu, Feb 18, 2021 at 9:16 PM Andrei Sekretenko 
>> wrote:
>>
>>> IIUC, Attic is not intended for projects which still have active users
>>> and thus might be in need of fixing bugs.
>>>
>>> Key items about moving project to Attic:
>>> > It is not intended to:
>>> > - Rebuild community
>>> > - Make bugfixes
>>> > - Make releases
>>>
>>> >Projects whose PMC are unable to muster 3 votes for a release, who have
>>> no active committers or are unable to fulfill their reporting duties to the
>>> board are all good candidates for the Attic.
>>>
>>> As a D2iQ employee, I can say that if we find a bug critical for our
>>> customers, we will be interested in fixing that. Should the project be
>>> moved into Attic, the fix will be present only in forks (which might
>>> mean our internal forks).
>>>
>>> I could imagine that other entities and people using Mesos are in a
>>> similar position with regards to bugfixes.
>>> If this is true, then moving the project to Attic in the near future
>>> is not a proper solution to the issue of insufficient bandwidth of the
>>> active PMC members/chair.
>>>
>>> ---
>>> A long-term future of the project is a different story, which, in my
>>> personal view, will "end" either in moving the project into Attic or
>>> in shifting the project direction from what it used to be in the
>>> recent few years to something substantially different. IMO, this
>>> requires a  _separate_ discussion.
>>>
>>> Damien's questions sound like a good starting point for that
>>> discussion, I'll try to answer them from my committer/PMC member
>>> perspective when I have enough time.
>>>
>>> On Thu, 18 Feb 2021 at 12:49, Charles-François Natali
>>>  wrote:
>>> >
>>> > Thanks Tomek, that's what I suspected.
>>> > It would therefore make it much more difficult for anyone to carry on
>>> since it would effectively have to be a fork, etc.
>>> > I think it'd be a bit of a shame, but I understand Benjamin's point.
>>> > I hope it can be avoided.
>>> >
>>> >
>>> > Cheers,
>>> >
>>> >
>>> >
>>> > On Thu, 18 Feb 2021, 11:02 Tomek Janiszewski, 
>>> wrote:
>>> >>
>>> >> Moving to attic is making project read only
>>> >> https://attic.apache.org/
>>> >> https://attic.apache.org/projects/aurora.html
>>> >>
>>> >> czw., 18 lut 2021, 11:56 użytkownik Charles-François Natali <
>>> cf.nat...@gmail.com> napisał:
>>> >>>
>>> >>> I'm not familiar with the attic but would it still allow to actually
>>> >>> develop, make commits to the repository etc?
>>> >>>
>>> >>>
>>> >>> On Thu, 18 Feb 2021, 08:27 Benjamin Bannier, 
>>> wrote:
>>> >>>
>>> >>> > Hi Vinod,
>>> >>> >
>>> >>> > > I would like to start a discussion around the future of the Mesos
>>> >>> > project.
>>> >>> > >
>>> >>> > > As you are probably aware, the number of active committers and
>>> >>> > contributors
>>> >>> > > to the project h

Re: Next Steps

[Tomek Janiszewski]

Moving to attic is making project read only
https://attic.apache.org/
https://attic.apache.org/projects/aurora.html

czw., 18 lut 2021, 11:56 użytkownik Charles-François Natali <
cf.nat...@gmail.com> napisał:

> I'm not familiar with the attic but would it still allow to actually
> develop, make commits to the repository etc?
>
>
> On Thu, 18 Feb 2021, 08:27 Benjamin Bannier,  wrote:
>
> > Hi Vinod,
> >
> > > I would like to start a discussion around the future of the Mesos
> > project.
> > >
> > > As you are probably aware, the number of active committers and
> > contributors
> > > to the project have declined significantly over time. As of today,
> > there's
> > > no active development of any features or a public release planned. On
> the
> > > flip side, I do know there are a few companies who are still actively
> > using
> > > Mesos.
> >
> > Thanks for starting this discussion Vinod. Looking at Slack, mailing
> > lists, JIRA and reviewboard/github the project has wound down a lot in
> > the last 12+ months.
> >
> > > Given that, we need to assess if there's interest in the community to
> > keep
> > > this project moving forward. Specifically, we need some active
> committers
> > > and PMC members who are going to manage the project. Ideally, these
> would
> > > be people who are using Mesos in some capacity and can make code
> > > contributions.
> >
> > While I have seen a few non-committer folks contribute patches in the
> > last months, I feel it might be too late to bootstrap an active
> > community at this point.
> >
> > Apache Mesos is still mentioned prominently in the docs of a number of
> > other projects which gives off the impression of an active and
> > maintained project. In reality almost nobody is working on issues or
> > available to help users, and basing a new project on Apache Mesos these
> > days is probably not a good idea. I honestly do not see that to change
> > should new people step up and IMO the most honest way forward would be
> > to move the project to the attic to clearly communicate that the project
> > has moved into another phase; this wouldn't preclude folks from using or
> > further developing Apache Mesos, but would give a clear signal to users.
> >
> > > If there is no active interest, we will likely need to figure out steps
> > for
> > > retiring the project.
> > >
> > > *Call for action: If you are interested in becoming a committer/PMC
> > member
> > > (including PMC chair) and actively maintain the project, please reply
> to
> > > this email.*
> >
> > Like I wrote above, I would be in favor of a vote to move Apache Mesos
> > to the attic.
> >
> >
> > Cheers,
> >
> > Benjamin
> >
>

Re: Suddenly all tasks gone, framework at completed, cannot start framework

[Tomek Janiszewski]

See: https://stackoverflow.com/a/42544023/1387612

wt., 25 sie 2020 o 15:07 Marc Roos  napisał(a):

>
>
> Today all my tasks are down and framework marathon is at completed. Any
> idea how this can happen?
>
>
>
> ed.cpp:520] Successfully authenticated with master
> master@192.168.10.151:5050
> I0825 13:03:27.961248   108 sched.cpp:1188] Got error 'Framework has
> been removed'
>
>

Re: Advice on alternative for marathon framework

[Tomek Janiszewski]

You can try https://github.com/HubSpot/Singularity
Aurora was moved to attic 

śr., 15 lip 2020 o 16:29 Marc Roos  napisał(a):

>
>
> I am having problems[1] getting marathon to run since march (can only
> run 1.7) and the only emails I receive from d2iq is how to rate their
> support. I wonder if this Marathon is still best to be used with mesos.
> I have aurora running, but it looks to have less options.
>
> What I like about the Marathon framework is of course the web interface
> and some plugins that allowed me to use capabilities. I know I
> should/could launch application directly in mesos via the command line.
> But I am just starting with the mesos and I prefer now to have a gui.
>
> Can anyone advice on a good alternative to marathon?
>
>
> [1]
> https://jira.d2iq.com/browse/MARATHON-8729
> https://github.com/mesosphere/marathon/issues/7136
>

Re: Task list node

[Tomek Janiszewski]

You can just mimic UI behaviour and use /state endpoint and filter it with
jq.

wt., 1 paź 2019 o 13:56 Marc Roos  napisał(a):

>
>
> Hmmm, if do something like this[0] I get only 3 tasks, and the mesos gui
> on 5050 is showing all (I guess, at least more than three) Also if I
> grep the unfiltered json output for a task string, it does not find it.
>
> [0]
> curl -s --user test:xxx --cacert /etc/pki/ca-trust/source/ca-test.crt -X
> GET https://m01.local:5050/tasks  | jq '.tasks[] |
> select(.state=="TASK_RUNNING")'
>
> curl -s --user test:xxx --cacert /etc/pki/ca-trust/source/ca-test.crt -X
> GET https://m01.local:5050/master/tasks  | jq '.tasks[] |
> select(.state=="TASK_RUNNING") | del(.statuses, .discovery,
> .health_check, .container)  | "\(.name) \(.state) \(.slave_id)" '
>
>
> -Original Message-
> To: user
> Subject: Re: Task list node
>
> You can list them with agent containers endpoint
> http://mesos.apache.org/documentation/latest/endpoints/slave/containers/
> Or with master tasks endpoint and filter them localy with jq
> http://mesos.apache.org/documentation/latest/endpoints/master/tasks/
>
> czw., 26 wrz 2019 o 22:09 Marc Roos 
> napisał(a):
>
>
>
> What would be the easiest way to list running tasks on a
> node/agent/slave?
>
>
>
>
>
>
>
>
>
>
>

Re: Maybe new feature/option for the health check

[Tomek Janiszewski]

It there but with different name:

   - delay_seconds is the amount of time to wait until starting health
   checking the task
   - grace_period_seconds is the amount of time after the task is launched
   during which health check failures are ignored. Once a health check
   succeeds for the first time, the grace period does not apply anymore. Note
   that it includes delay_seconds, i.e., setting grace_period_seconds <
   delay_seconds has no effect

http://mesos.apache.org/documentation/latest/health-checks/#common-options-1

pon., 30 wrz 2019, 22:46 użytkownik Marc Roos 
napisał:

>
> I have a few tasks that take a while before they get started. Sendmail
> eg. Is not to happy you cannot set the hostname (in marathon) and then
> gives a timeout of 1 minute. I think there is something similar when
> starting openldap. If I enable a regular health check there, it will
> fail the task before it finished launching. Maybe it is interesting to
> add an option for this initDelay?
>
>
> {
>   "path": "/api/health",
>   "portIndex": 0,
>   "protocol": "MESOS_HTTP",
>   "initDelay": 60,  <
>   "gracePeriodSeconds": 300,
>   "intervalSeconds": 60,
>   "timeoutSeconds": 20,
>   "maxConsecutiveFailures": 3
> }
>
>

Re: Task list node

[Tomek Janiszewski]

You can list them with agent containers endpoint
http://mesos.apache.org/documentation/latest/endpoints/slave/containers/
Or with master tasks endpoint and filter them localy with jq
http://mesos.apache.org/documentation/latest/endpoints/master/tasks/

czw., 26 wrz 2019 o 22:09 Marc Roos  napisał(a):

>
> What would be the easiest way to list running tasks on a
> node/agent/slave?
>
>
>
>
>
>
>
>

Re: Where are error codes listed?

[Tomek Janiszewski]

This is a command exit code not executor. You need to investigate command
you try to run.

śr., 13 lut 2019 o 20:29 Marc Roos  napisał(a):

>
> Where can I find a list of returned error codes?
>
> I0213 20:20:57.778371  8382 executor.cpp:1003] Command exited with
> status 100
>

Re: Clean up old unused data

[Tomek Janiszewski]

Messo has builtin GC. See this question
https://stackoverflow.com/q/50819091/1387612

śr., 13 lut 2019 o 12:28 Marc Roos  napisał(a):

>
>
>
>
>
>
>
>
> And these
>
>
> [@m03 executors]# ls -l
> /var/lib/mesos/meta/slaves/976957d9-40ee-4b5d-b41c-1b13e90dd913-S1/frame
> works/8eeccf5c-18ab-44f0-8dde-89336e900d2c-/executors
>
>
> drwxr-xr-x3 root root39 Feb 13 12:05
> mariadb.3d8c2f0c-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:05
> mariadb.4089697d-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:05
> mariadb.43862ebe-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:05
> mariadb.49807c8f-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:05
> mariadb.4f7b1880-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:05
> mariadb.55756651-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:06
> mariadb.5b6fb422-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:06
> mariadb.616a5013-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:06
> mariadb.6764c4f4-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:06
> mariadb.6d60c075-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:06
> mariadb.735b5c66-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:07
> mariadb.7c53cf07-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:07
> mariadb.854da138-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:07
> mariadb.8e42df89-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:07
> mariadb.97386bfa-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:08
> mariadb.a32d55bb-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:08
> mariadb.af2091cc-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:08
> mariadb.bc46f6ad-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:09
> mariadb.ca81157e-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:09
> mariadb.da9d88df-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:10
> mariadb.ed09dfb0-2f7f-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:10
> mariadb.01f2cf41-2f80-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:12
> mariadb.19dfb002-2f80-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:12
> mariadb.4993c113-2f80-11e9-b19a-5051143001a1
> drwxr-xr-x3 root root39 Feb 13 12:13
> mariadb.6906e6d4-2f80-11e9-b19a-5051143001a1
>
>
> [@m03 mesos]# ls -l /var/lib/mesos/meta/slaves/
> total 0
> drwxr-xr-x 4 root root 76 Feb 13 12:08
> 5c859c22-6183-4f39-a343-8c3f6bb87b69-S2
> drwxr-xr-x 2 root root 24 Oct 10  2017
> 8eeccf5c-18ab-44f0-8dde-89336e900d2c-S0
> drwxr-xr-x 3 root root 58 Feb  9 17:20
> 976957d9-40ee-4b5d-b41c-1b13e90dd913-S0
> drwxr-xr-x 4 root root 76 Feb  9 20:18
> 976957d9-40ee-4b5d-b41c-1b13e90dd913-S1
> drwxr-xr-x 2 root root 24 Oct 21  2017
> a26aed49-a710-41aa-95d6-22b219f78232-S0
> drwxr-xr-x 2 root root 24 Oct 22  2017
> a26aed49-a710-41aa-95d6-22b219f78232-S1
> drwxr-xr-x 2 root root 24 Oct 22  2017
> a26aed49-a710-41aa-95d6-22b219f78232-S2
> drwxr-xr-x 2 root root 24 Oct 22  2017
> a26aed49-a710-41aa-95d6-22b219f78232-S3
> drwxr-xr-x 2 root root 24 Oct 22  2017
> a26aed49-a710-41aa-95d6-22b219f78232-S4
> drwxr-xr-x 2 root root 24 Oct 22  2017
> a26aed49-a710-41aa-95d6-22b219f78232-S5
> lrwxrwxrwx 1 root root 66 Feb  9 18:14 latest ->
> /var/lib/mesos/meta/slaves/976957d9-40ee-4b5d-b41c-1b13e90dd913-S1
>
>
>
>
>
>
>
>

Re: Mesos / Marathon - Application wiped out automically

[Tomek Janiszewski]

Marathon often changes schema and perform data migration. I think migration
is done only from previous minor version.
With Mesos there are detailed instructions for each releases
http://mesos.apache.org/documentation/latest/upgrades/

śr., 29 sie 2018, 17:16 użytkownik Antony A 
napisał:

> Any reason to step the upgrade process? Just curious.
>
> On Wed, Aug 29, 2018 at 4:50 AM Tomek Janiszewski 
> wrote:
>
>> AFAIK there are no breaking changes only some deprecations/removals. You
>> might want to see changelog and do not skip versions when doing upgrade
>> https://github.com/apache/mesos/blob/master/CHANGELOG#L368
>>
>> śr., 29 sie 2018 o 02:43 użytkownik Antony A 
>> napisał:
>>
>>> Thank you. I will try upgrading marathon. I am also planing to upgrade
>>> mesos1.6.
>>>
>>> Please can you let me know if I have to be aware of any breaking
>>> releases from 1.2 to 1.6?
>>>
>>> Thanks
>>> Antony
>>>
>>> Sent from my mobile. *Please excuse any typos.*
>>>
>>> On Aug 24, 2018, at 10:45 AM, Tomek Janiszewski 
>>> wrote:
>>>
>>> Please attach logs.
>>> You should update to 1.4.12 there were a lot of bugs fixed and there's a
>>> chance you run into one of them
>>> https://github.com/mesosphere/marathon/blob/v1.4.12/changelog.md
>>>
>>> pt., 24 sie 2018, 18:00 użytkownik Harold Dost 
>>> napisał:
>>>
>>>> Are there any indications in the logs? Generally scheduling and
>>>> de-scheduling should show there.
>>>>
>>>> On Fri, Aug 24, 2018, 11:14 Antony A  wrote:
>>>>
>>>>> I am relative new to Mesos/Marathon. In my marathon framework I
>>>>> noticed recently couple of times all the applications got deleted. I had 
>>>>> to
>>>>> redeploy from my artifact to get the application available again.Has 
>>>>> anyone
>>>>> noticed the same. Any pointers on where to look for errors/changes?
>>>>>
>>>>>
>>>>> Here are the version of mesos and marathon.
>>>>>
>>>>> mesos 1.2.0 (5 node master and 5 node zk) running on the 5 VMs.
>>>>> mesos 1.3.0 (agent)
>>>>> marathon-1.4.3
>>>>>
>>>>> Thanks
>>>>> AAA
>>>>>
>>>>>

Re: Mesos / Marathon - Application wiped out automically

[Tomek Janiszewski]

AFAIK there are no breaking changes only some deprecations/removals. You
might want to see changelog and do not skip versions when doing upgrade
https://github.com/apache/mesos/blob/master/CHANGELOG#L368

śr., 29 sie 2018 o 02:43 użytkownik Antony A 
napisał:

> Thank you. I will try upgrading marathon. I am also planing to upgrade
> mesos1.6.
>
> Please can you let me know if I have to be aware of any breaking releases
> from 1.2 to 1.6?
>
> Thanks
> Antony
>
> Sent from my mobile. *Please excuse any typos.*
>
> On Aug 24, 2018, at 10:45 AM, Tomek Janiszewski  wrote:
>
> Please attach logs.
> You should update to 1.4.12 there were a lot of bugs fixed and there's a
> chance you run into one of them
> https://github.com/mesosphere/marathon/blob/v1.4.12/changelog.md
>
> pt., 24 sie 2018, 18:00 użytkownik Harold Dost 
> napisał:
>
>> Are there any indications in the logs? Generally scheduling and
>> de-scheduling should show there.
>>
>> On Fri, Aug 24, 2018, 11:14 Antony A  wrote:
>>
>>> I am relative new to Mesos/Marathon. In my marathon framework I noticed
>>> recently couple of times all the applications got deleted. I had to
>>> redeploy from my artifact to get the application available again.Has anyone
>>> noticed the same. Any pointers on where to look for errors/changes?
>>>
>>>
>>> Here are the version of mesos and marathon.
>>>
>>> mesos 1.2.0 (5 node master and 5 node zk) running on the 5 VMs.
>>> mesos 1.3.0 (agent)
>>> marathon-1.4.3
>>>
>>> Thanks
>>> AAA
>>>
>>>

Re: New Mesos User Groups in the Netherlands and Belgium

[Tomek Janiszewski]

PR: https://github.com/apache/mesos/pull/298/files

czw., 21 cze 2018, 14:29 użytkownik Mats Uddenfeldt <
mats.uddenfe...@gmail.com> napisał:

> Hi there,
>
> We've recently launched Mesos User Groups in the Netherlands (
> https://www.meetup.com/Dutch-Mesos-User-Group/) and Belgium (
> https://www.meetup.com/Belgian-Mesos-User-Group/) and also noticed that
> the old Amsterdam Mesos User Group has changed its topic away from Mesos.
>
> I tried to reach out to the creator of the old group, but he has no
> interest in changing the topic back.
>
> Could you please update the list on the web site by removing the old
> Amsterdam group and adding the new ones? If it would be possible to send
> out a tweet for each group from the official Apache Mesos account it would
> be great to boost awareness of the groups! Thanks!
>
> Cheers,
>
> Mats.
>

Re: mesos-execute cmd

[Tomek Janiszewski]

IMO it requires a custom framework that will handle spiting task into
multiple nodes. I need more details to help.

śr., 20 cze 2018 o 15:38 użytkownik Abel Souza  napisał:

> Anyone that could suggest me anything? Is it a problem that could be fixed
> by writing a custom framework?
>
> /Abel
>
> On 06/13/2018 06:05 AM, Abel Souza wrote:
>
> Did you mean through ‘mesos-execute’ command or is it a Mesos general
> behavior?
>
> Best,
>
> /Abel Souza
>
> On Jun 13, 2018, at 02:04, Qian Zhang  wrote:
>
> It is possible to use multiple offers from a single agent node to launch a
> task, but I do not think you can use multiple offers from different agent
> nodes to launch a task.
>
>
> Regards,
> Qian Zhang
>
> On Tue, Jun 12, 2018 at 9:12 PM, Abel Souza  wrote:
>
>> Hello,
>>
>> I believe this question relates to the framework used by the
>> mesos-execute command (available by default in Mesos installation):
>>
>> When I request a number of cores greater than what is available in one
>> single node, the mesos-execute automatically turn down all offers made
>> by Mesos and hangs forever. E.g.: Each agent node in my cluster has 8
>> cores, and when I request 9 cores through mesos-execute
>> --resources='cpus:9', the command waits forever. But If I execute 
>> mesos-execute
>> --resources='cpus:8', tasks start execution right away.
>>
>> So I would like to know if there is a way to enable the mesos-execute to
>> handle situations where multiple nodes are needed to satisfy a resource
>> request. If so, what would be needed?
>>
>> Thank you,
>>
>> /Abel Souza
>>
>
>
>

Re: reserving resources for host/mesos

[Tomek Janiszewski]

Just measure CPU/MEM usage on clean agent (when no task is running) and
ensure you leave a little bit more than that.

wt., 12 cze 2018 o 15:01 użytkownik Paul Mackles  napisał:

> Hi - Basic question that I couldn’t find an answer to in existing docs…
> when configuring the available resources on a slave, is it appropriate to
> leave some resources over for the mesos-agent itself (and the host OS)? Any
> pointers on existing configs folks are using would be appreciated.
>
>
> --
> Thanks,
> Paul
>

Re: High availability feature

[Tomek Janiszewski]

Marathon has its own mechanism. In theory it's similar but differs in
implementation but both rely on Zookeeper (ZK) for leader election. Mesos
uses replica log for keeping data while Marathon stores everything in ZK.

pt., 20.04.2018, 16:06 użytkownik Mahmood Naderan 
napisał:

> Hi,
> I want to know if the high availability feature of mesos is related to
> high availability of Marathon? In other word, mesos supports multiple
> master nodes with an election policy and so on. Does that provide high
> availability feature for marathon? Or marathon has its own mechanism?
>
>
> Regards,
> Mahmood
>

[GSoC] Google Summer of Code

[Tomek Janiszewski]

Hi

It looks like Apache Foundation was selected to Google Summer of Code
https://summerofcode.withgoogle.com/organizations/5718432427802624/
Do we plan to submit any project related to Mesos. I was thinking about a
project to refresh Mesos UI (catch up with features, upgrade to latest
Angular (or rethink the framework)).
What do you think?

Best
Tomek

Re: Build Failure

[Tomek Janiszewski]

Do you have unzip installed? Can you try unzipping file like it's done in
the test?

pon., 19.03.2018, 22:53 użytkownik Shiv Deepak 
napisał:

> Hello,
>
> I am trying to build Mesos 1.5.0 from source on Ubuntu 16.04.
>
> I tried on Docker, VM, and EC2. Three test cases are failing no matter
> what.
>
> Here is the list.
>
> *[  PASSED  ] 1904 tests.*
> *[  FAILED  ] 3 tests, listed below:*
> *[  FAILED  ] FetcherTest.Unzip_ExtractFile*
> *[  FAILED  ] FetcherTest.Unzip_ExtractInvalidFile*
> *[  FAILED  ] FetcherTest.Unzip_ExtractFileWithDuplicatedEntries*
>
> Here is the test output:
>
> *[ RUN  ] FetcherTest.Unzip_ExtractFile*
> *../../src/tests/fetcher_tests.cpp:870: Failure*
> *(fetch).failure(): Failed to fetch all URIs for container
> '709de28f-5f71-439d-a032-072df865090f': exited with status 1*
> *[  FAILED  ] FetcherTest.Unzip_ExtractFile (297 ms)*
> *[ RUN  ] FetcherTest.Unzip_ExtractInvalidFile*
> *../../src/tests/fetcher_tests.cpp:936: Failure*
> *Value of: os::exists(extractedFile)*
> *  Actual: false*
> *Expected: true*
> *[  FAILED  ] FetcherTest.Unzip_ExtractInvalidFile (201 ms)*
> *[ RUN  ] FetcherTest.Unzip_ExtractFileWithDuplicatedEntries*
> *../../src/tests/fetcher_tests.cpp:997: Failure*
> *(fetch).failure(): Failed to fetch all URIs for container
> 'dd749015-3d16-4926-b7f3-e1c96211a461': exited with status 1*
> *[  FAILED  ] FetcherTest.Unzip_ExtractFileWithDuplicatedEntries (201 ms)*
>
> Is this expected or do I need to fix something? Can someone please point
> me in the right direction?
>
> Thank you
>
> --
>
> 
>
> Shiv Deepak▌
> Engineering Manager
>
> HackerRank
>
> Blog  / Twitter
>  / Linkedin
>  / Facebook
> 
>
>

Re: Container user '27' is not supported

[Tomek Janiszewski]

This might be the following limitations

> If the --switch_user flag is set on the agent and the framework specifies
a user (either CommandInfo.user or FrameworkInfo.user), we expect that user
exists in the container image and its uid and gids matches that on the
host. User namespace is not supported yet. If the user is not
specified, root will be used by default. The operator or the framework can
limit the capabilities of the container by using
the linux/capabilities isolator.

niedz., 24.12.2017, 14:20 użytkownik Marc Roos 
napisał:

>
> I am seeing this in the logs:
>
> Container user '27' is not supported yet for container
> d823196a-4ec3-41e3-a4c0-6680ba5cc99
>
> I guess this means that the container requests to run under a specific
> user id, and this is not yet available in mesos?
>
> mesos-1.4.1-2.0.1.x86_64
>

Re: Enabling marathon for cni networks

[Tomek Janiszewski]

Take a look here
https://mesosphere.github.io/marathon/docs/networking.html#enabling-container-mode
Or if you are running older version of Marathon here
https://mesosphere.github.io/marathon/docs/ip-per-task.html

pon., 11 gru 2017 o 13:29 użytkownik Marc Roos 
napisał:

>
> I have a default marathon setup that attaches containers to the host
> network.
>
> Where should I put this configuration of NetworkInfo? In
> /etc/marathon/conf?
>
>
> http://mesos.apache.org/documentation/cni/#attaching-containers-to-cni-networks
>

Re: How to add static ip to application

[Tomek Janiszewski]

You can achieve it with Mesos-DNS. Here is a small overview how to do it
https://stackoverflow.com/a/37822870/1387612

pon., 11 gru 2017 o 11:48 użytkownik Marc Roos <m.r...@f1-outsourcing.eu>
napisał:

>
> Ok should this be available in mesos/marathon also, because I did not
> install dcos yet?
>
>
>
>
> -Original Message-
> From: Alvaro Brandon [mailto:alvarobran...@gmail.com]
> Sent: maandag 11 december 2017 11:46
> To: user@mesos.apache.org
> Subject: Re: How to add static ip to application
>
> You can consider influxdb.marathon.agentip.dcos.thisdcos.directory as
> the static IP. This will allow you to do exactly what you are saying.
>
>
> If for any reason a DNS name is not enough and you want an IP for the
> service like 10.158.79.241, I'm pretty sure that there is no way of
> doing so.
>
>
> 2017-12-11 11:39 GMT+01:00 Marc Roos <m.r...@f1-outsourcing.eu>:
>
>
>
>
> Is it possible to configure just a static ip for now, just for the
> purpose of my education? I want to see if I can access the task on
> this
> ip when I am starting it on different hosts.
>
>
>
>
>
> -Original Message-
> From: Alvaro Brandon [mailto:alvarobran...@gmail.com
> <mailto:alvarobran...@gmail.com> ]
> Sent: maandag 11 december 2017 11:20
> To: user@mesos.apache.org
> Subject: Re: How to add static ip to application
>
> I think its DNS what you need. The DNS name for your task can be
> used as
> an static reference to the influxdb instance, independently of the
> host.
>
>
> https://docs.mesosphere.com/1.10/networking/dns-overview/
> <https://docs.mesosphere.com/1.10/networking/dns-overview/>
>
>
> Take a look at the link, but I think you can use
> influxdb.marathon.agentip.dcos.thisdcos.directory as the task's
> address
>
> 2017-12-11 11:11 GMT+01:00 Marc Roos <m.r...@f1-outsourcing.eu>:
>
>
>
> For now I would like to have the ip bound to the
> application/task/container, no matter on what host the
> application
> will
> be started. And in this case I would like to be able to
> access the
> influxdb server as if I would have been created a dedicated
> vm for
> it.
>
> Is there some page explaining the syntax of ipAddress? This
> are not
> working, I tried also with removing the portDefinitions
> section.
>
>
> {
>   "id": "/influxdb",
>   "cmd": null,
>   "cpus": 0.5,
>   "mem": 128,
>   "disk": 0,
>   "instances": 1,
>   "acceptedResourceRoles": [],
>   "container": {
> "type": "MESOS",
> "volumes": [],
> "docker": {
>   "image": "influxdb",
>   "credential": null,
>   "forcePullImage": false
>     }
>   },
> "ipAddress": {},
>   "portDefinitions": [
> {
>   "port": 10001,
>   "protocol": "tcp",
>   "labels": {}
> }
>   ]
> }
>
>
> -Original Message-
> From: Tomek Janiszewski [mailto:jani...@gmail.com]
> Sent: maandag 11 december 2017 10:41
> To: user@mesos.apache.org
> Subject: Re: How to add static ip to application
>
> What do you mean by "bind to a static IP"?
>
> 1.  IP Per Container?
>
> https://mesosphere.github.io/marathon/docs/ip-per-task.html
> <https://mesosphere.github.io/marathon/docs/ip-per-task.html>
> <https://mesosphere.github.io/marathon/docs/ip-per-task.html
> <https://mesosphere.github.io/marathon/docs/ip-per-task.html> >
> 2.  IP of one dedicated host?
>
> https://mesosphere.github.io/marathon/docs/constraints.ht

Re: How to add static ip to application

[Tomek Janiszewski]

What do you mean by "bind to a static IP"?

   1. IP Per Container?
   https://mesosphere.github.io/marathon/docs/ip-per-task.html
   2. IP of one dedicated host?
   https://mesosphere.github.io/marathon/docs/constraints.html
   3. Layer 3/4 loadbalancer that will create Virtual IP (VIP)?


niedz., 10 gru 2017 o 23:33 użytkownik Marc Roos 
napisał:

>
>
> I downloaded the influxdb docker image and am running it from Marathon,
> I would like to bind it to a static ip. What would be the 'best' way to
> do this? Sorry for if this is a very basic question. Link to an
> appropriate howto is also welcome.
>
>
>
> {
>   "id": "/influxdb",
>   "cmd": null,
>   "cpus": 0.5,
>   "mem": 128,
>   "disk": 0,
>   "instances": 1,
>   "acceptedResourceRoles": [],
>   "container": {
> "type": "MESOS",
> "volumes": [],
> "docker": {
>   "image": "influxdb",
>   "credential": null,
>   "forcePullImage": false
> }
>   },
>   "portDefinitions": [
> {
>   "port": 10001,
>   "protocol": "tcp",
>   "labels": {}
> }
>   ]
> }
>
>
>
> I have a default setup on centos7:
> marathon-1.4.8-1.0.660.el7.x86_64
> mesosphere-zookeeper-3.4.6-0.1.20141204175332.centos7.x86_64
> chronos-2.5.0-0.1.20170816233446.el7.x86_64
> mesos-1.4.0-2.0.1.x86_64
>
> Running mesos-dns in Marathon
>
>
>
>
>
> ​
>
>
>
>
>

Re: Marathon deployment without "blue/green" (need to free resources before deploying)

[Tomek Janiszewski]

Hi

It's described here
https://mesosphere.github.io/marathon/docs/deployments.html#rolling-restarts
> minimumHealthCapacity == 0 : All old instances can be killed before the
new version is deployed.

Best
Tomek

wt., 28 lis 2017 o 14:42 użytkownik Adam Cecile 
napisał:

> Hi there,
>
>
> We have a limited amount of GPU so when a new deployment occurs
> (replacing an existing one) in Marathon it gets locked because there's
> no GPUs left to deploy new version before killing the previous one.
>
> Is there any API parameter to force kill of the old instance first ?
>
> Thanks in advance,
>
>
> Best regards, Adam.
>
>

Re: Can't really understand how do Executors can be injected...

[Tomek Janiszewski]

Task contains information about resources for an executor [1] by default
its 0.1 CPU and 32 MEM [2]

1: https://github.com/apache/mesos/blob/1.4.1/include/mesos/mesos.proto#L736
2:
https://github.com/apache/mesos/blob/1.4.1/src/slave/constants.hpp#L101-L105

czw., 23 lis 2017 o 10:15 użytkownik Alex Kotelnikov <
alex.kotelni...@diginetica.com> napisał:

> A-ha.
>
> This means that there is no resources reservation for an executor,
> resources are totally dedicated to tasks, correct?
>
>
> On 22 November 2017 at 22:20, Vinod Kone  wrote:
>
>> If you have an executor running on a agent, wait for an offer from *that
>> agent* and launch a new task with the *same* ExecutorInfo as the one you
>> originally used to launch the executor. In this case, mesos will not launch
>> a new executor but passes the task to the already running executor. Note
>> that, if for some reason your original executor died just as you were
>> launching the new task, mesos will launch a new instance of that executor
>> and pass the new task. So your executor needs to handle this race.
>>
>> On Wed, Nov 22, 2017 at 10:45 AM, Alex Kotelnikov <
>> alex.kotelni...@diginetica.com> wrote:
>>
>>> Vihod,
>>>
>>> much more clear. Thanks.
>>>
>>> I refined first question inline.
>>>
>>> On 22 November 2017 at 21:15, Vinod Kone  wrote:
>>>
 Hi Alex,

 See my answers below

 1. Launch a task without accepting an offer (on already existing
> executor).
>

 This is not currently possible. Every task needs some non-zero
 resources, and hence an offer, to be launched. What's your use case?

>>>
>>> Basically if I have an executor running, how to launch a task on it?
>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>>
>>> *Alexander Kotelnikov*
>>>
>>> *Team Lead*
>>>
>>> DIGINETICA
>>> Retail Technology Company
>>>
>>> m: +7.921.915.06.28 <+7%20921%20915-06-28>
>>>
>>> *www.diginetica.com *
>>>
>>
>>
>
>
> --
>
> Best Regards,
>
>
> *Alexander Kotelnikov*
>
> *Team Lead*
>
> DIGINETICA
> Retail Technology Company
>
> m: +7.921.915.06.28 <+7%20921%20915-06-28>
>
> *www.diginetica.com *
>

Re: .deb packages of mesos releases

[Tomek Janiszewski]

That will be awesome. We have ARM Jenkins agent so we can prepare packages
for ARM too.

wt., 14.11.2017, 23:56 użytkownik Kapil Arya <ka...@mesosphere.io> napisał:

> Hi Adam,
>
> I am wondering if you would have some time to bring your debian packaging
> into Mesos source tree. We can then use the ASF Jenkins CI to build and
> publish packages to bintray just like we started doing for CentOS 6/7? This
> will also allow the community to more actively participate in maintaining
> it in future.
>
> Best,
> Kapil
>
> On Wed, Sep 13, 2017 at 2:08 PM, Adam Cécile <adam.cec...@hitec.lu> wrote:
>
> > In case someone's interrested in, I added 1.1.3 debs on my repository:
> >
> > https://packages.le-vert.net/mesos/
> >
> >
> > On 09/09/2017 06:40 PM, Adam Cecile wrote:
> >
> > Hey,
> >
> > Well that's not really a problem, I can provide 1.1.x packages if your
> > interested in.
> >
> > Regards, Adam.
> >
> > On September 8, 2017 10:47:23 AM GMT+02:00, Tomek Janiszewski
> > <jani...@gmail.com> <jani...@gmail.com> wrote:
> >>
> >> @Adam Thanks for taking care of this. There is one problem, Mesos 1.1.3
> >> is missing in provided repository.
> >>
> >> @Kapil What is the status of official Apache Mesos packages? At Mesos
> >> Developer Community Meeting (Jan 26, 2017) you presented a proposal for
> >> this: https://youtu.be/m7WzKia68Rg
> >>
> >> wt., 5 wrz 2017 o 15:31 użytkownik Adam Cecile <adam.cec...@hitec.lu>
> >> napisał:
> >>
> >>> On 09/05/2017 11:55 AM, Oskar Jagodziński wrote:
> >>> > Hi all,
> >>> >
> >>> > What is standard interval between release of mesos package and
> >>> > 'official' .deb build by Mesosphere? Mesos 1.1.3 was released 11 days
> >>> > ago and there is no package at
> >>> > https://open.mesosphere.com/downloads/mesos/ only rc-packages
> >>> > https://open.mesosphere.com/downloads/mesos-rc/ are up to date.
> >>> >
> >>> Hello,
> >>>
> >>>
> >>> First, I like to make an important statement:
> >>>
> >>> *I'm not an official mesosphere guy*
> >>>
> >>> That being said, Mesosphere package are binary copy of CentOS built
> file
> >>> into a deb container. That's not what I call a Debian package at all
> and
> >>> I already had severe issue with that (libcurl-nss backed built which
> >>> does not support https on Debian-based system).
> >>>
> >>> For this reason, I create my own Mesos package, as a REAL debian
> >>> package, built from sources in a clean environment using pbuilder. I
> >>> also provide armhf and arm64 build because I've plan for that ;-)
> >>>
> >>> These package are in-use at three customers place and work just fine. I
> >>> provide multiple branches packages and build them with additional
> >>> network isolator using libnl and XFS disk isolator.
> >>>
> >>>
> >>> It's available there:
> >>>
> >>> https://packages.le-vert.net/mesos/
> >>>
> >>> Feel free to do what the f*** you want, use the repository directly,
> >>> sync it, rebuild debs from sources packages...
> >>>
> >>>
> >>> Regards, Adam.
> >>>
> >>>
> > --
> > Sent from my Android device with K-9 Mail. Please excuse my brevity.
> >
> >
> >
>

Re: Mesos , Java & hardware isolation

[Tomek Janiszewski]

@Justin Take a look at this answer
https://stackoverflow.com/a/22762558/1387612 we are using similar approach
to change CPU/MEM seen by JVM running in a container.

wt., 7.11.2017, 17:06 użytkownik Justin Lee  napisał:

> It may also depend on the version of Java you're using - depending on the
> version of Java that you're using, they may or may not properly pick up the
> cgroup settings vs. the total number of cores available.
>
> I don't know which version(s) of Java work, but I think the later versions
> have better support.
>
> Thanks,
> Justin Lee
>
> On Tue, Nov 7, 2017 at 10:18 AM, deadbrain 
> wrote:
>
>> Thanks Thodoris for you help I will need to check with people managing
>> the infrastructure to see what parameters are passed to our agents...
>>
>> Thanks again for the tips
>>
>> Regards
>>
>>
>>
>> On 11/07/2017 04:10 PM, Thodoris Zois wrote:
>>
>>> Hello,
>>>
>>> I don't really know if i can help you but i used Docker containers in
>>> Mesos with isolation and everything was perfect. So are you using Mesos
>>> containerizer? Did you enable cgroups/mem, cgroups/cpu on each agent? As it
>>> concerns CPU, cgroups do not limit the anount of CPU if its the only
>>> running application. In order to limit exactly CPU you need to enable cfs
>>> on each agent.
>>>
>>> Thodoris
>>>
>>> On 7 Nov 2017, at 15:28, deadbrain  wrote:

 Hi all,

 I expect to be at the right place for my question...

 We are hosting Java micro services exposed as docker containers (Spring
 Boot applications inside) inside Mesos

 We face 2 major problems:

 - hardware isolation (number of cores seen by Java Virtual Machines)
 makes our applications go crazy because JVM sees all cores and not the only
 ones given in the Mesos config parameters as a consequence GC heuristics
 are wrong and  some config values in some libraries are false too (Undertow
 web server spawns 8*number of cores as workers thread pool)...

 In Linux since the 2.4.19 kernel we have the per process namespace
 option to limit the hardware vision of any container... What would  be the
 solution on Mesos ?


 - CPU starvation : some micro services do not seem to have the required
 CPU time to work, what kind of advices could you give me to have a better
 understanding regarding this problem

 Statement: we can see very long partial GC times (about 4 seconds) ,
 standard times would be about 50ms


 Thanks for your help

 Kind regards

 Jerome


>>
>

Re: Apache Mesos Logo for MesosCon Stickers

[Tomek Janiszewski]

Hi

I described the process of ordering Mesos Stickers here
https://lists.apache.org/thread.html/932f8fd677ca5c1520e843f2166fbd76bc6bb3d603bd864aedb5eeed@%3Cuser.mesos.apache.org%3E

Best
Tomek

pon., 9 paź 2017 o 16:01 użytkownik Sharan Foga  napisał:

> Hi
>
> My name is Sharan. I'm involved with Apache Community Development and I'll
> be running the Apache Software Foundation booth at MesosCon Europe in
> Prague in a few weeks. The plan is to give away project stickers and
> various ASF swag – so if you are coming along then please feel free to drop
> by, say hello and pick something up.
>
> I'm currently in the process of ordering some more stickers and am looking
> for the Apache Mesos logo to get some printed. Please can anyone tell me
> (or send me a link to) where I can find the Apache Mesos logo artwork?
>
> Thanks
> Sharan
>

Re: [Proposal] Mesos on ARM

[Tomek Janiszewski]

@Matt I think Java runs on ARM and I saw some fixes for Zookeeper on ARM so
the main problem in running DC/OS is Mesos. Maybe there are other
components that might need to be fixed.

@Brock Thanks for interest. If you encourage any issue with ARM please ping
me. You can also report it on Apache JIRA with arm64 label.

wt., 26 wrz 2017 o 16:36 użytkownik Matt Jarvis <mjar...@mesosphere.com>
napisał:

> As a stretch goal, I'd also be interested in understanding what's required
> to run the rest of DC/OS on ARM - action is on me to reach out to the
> relevant folks inside Mesosphere for that.
>
> On 26 September 2017 at 14:39, Tomek Janiszewski <jani...@gmail.com>
> wrote:
>
>> Hi all
>>
>> I'd like to propose to add ARM64 support in Mesos. Currently, the only
>> Agent can run on ARM but it's not officially supported. This means build
>> failures on ARM are not considered as a bug.
>>
>> I know there were a couple of tries to run Mesos on ARM (mostly on
>> Raspberry PI) but this process is not straightforward and requires some
>> tuning.
>>
>> I'd like, in cooperation with WorksOnArm, to add ARM-based build to our
>> required test suit. Before, we need to make code to build on ARM and pass
>> all tests.
>>
>> Unfortunately, I do not know what exactly needs to be fixed because I
>> haven't started yet. I hope we can do it step by step. Once we got ARM
>> server we can use it to find problems when running on this architecture.
>>
>> What do you think about this? Is anybody interested in running Mesos on
>> ARM?
>>
>>
>> https://docs.google.com/document/d/1Hs40tGSUyoQa78ifVvn7VO5iSqe8nMc7VYWSugOqGFw/edit?usp=sharing
>> https://github.com/WorksOnArm/cluster/issues/9
>>
>> Thanks!
>>
>> –
>> Tomasz Janiszewski
>>
>
>

[Proposal] Mesos on ARM

[Tomek Janiszewski]

Hi all

I'd like to propose to add ARM64 support in Mesos. Currently, the only
Agent can run on ARM but it's not officially supported. This means build
failures on ARM are not considered as a bug.

I know there were a couple of tries to run Mesos on ARM (mostly on
Raspberry PI) but this process is not straightforward and requires some
tuning.

I'd like, in cooperation with WorksOnArm, to add ARM-based build to our
required test suit. Before, we need to make code to build on ARM and pass
all tests.

Unfortunately, I do not know what exactly needs to be fixed because I
haven't started yet. I hope we can do it step by step. Once we got ARM
server we can use it to find problems when running on this architecture.

What do you think about this? Is anybody interested in running Mesos on ARM?

https://docs.google.com/document/d/1Hs40tGSUyoQa78ifVvn7VO5iSqe8nMc7VYWSugOqGFw/edit?usp=sharing
https://github.com/WorksOnArm/cluster/issues/9

Thanks!

–
Tomasz Janiszewski

Re: .deb packages of mesos releases

[Tomek Janiszewski]

@Adam Thanks for taking care of this. There is one problem, Mesos 1.1.3 is
missing in provided repository.

@Kapil What is the status of official Apache Mesos packages? At Mesos
Developer Community Meeting (Jan 26, 2017) you presented a proposal for
this: https://youtu.be/m7WzKia68Rg

wt., 5 wrz 2017 o 15:31 użytkownik Adam Cecile 
napisał:

> On 09/05/2017 11:55 AM, Oskar Jagodziński wrote:
> > Hi all,
> >
> > What is standard interval between release of mesos package and
> > 'official' .deb build by Mesosphere? Mesos 1.1.3 was released 11 days
> > ago and there is no package at
> > https://open.mesosphere.com/downloads/mesos/ only rc-packages
> > https://open.mesosphere.com/downloads/mesos-rc/ are up to date.
> >
> Hello,
>
>
> First, I like to make an important statement:
>
> *I'm not an official mesosphere guy*
>
> That being said, Mesosphere package are binary copy of CentOS built file
> into a deb container. That's not what I call a Debian package at all and
> I already had severe issue with that (libcurl-nss backed built which
> does not support https on Debian-based system).
>
> For this reason, I create my own Mesos package, as a REAL debian
> package, built from sources in a clean environment using pbuilder. I
> also provide armhf and arm64 build because I've plan for that ;-)
>
> These package are in-use at three customers place and work just fine. I
> provide multiple branches packages and build them with additional
> network isolator using libnl and XFS disk isolator.
>
>
> It's available there:
>
> https://packages.le-vert.net/mesos/
>
> Feel free to do what the f*** you want, use the repository directly,
> sync it, rebuild debs from sources packages...
>
>
> Regards, Adam.
>
>

Re: Mesos-Metrics per task

[Tomek Janiszewski]

What isolators are you using? To get CPU usage you need to enable
cgroups/cpu [1]

1:
https://gist.github.com/chetan/9c519c68549b55d71709cb8cc62206ae#cgroupscpu

pt., 30.06.2017, 09:59 użytkownik Thodoris Zois  napisał:

> From the resources that Mesos allocated for a specific task, i would like
> to get somehow how much the task truly used with percentage. Maybe it
> wasn’t clear before, that’s why i am mentioning it. At Mesos UI for some
> reason i don’t see enough info for tasks etc. They are all the time empty….
>
>
>
> > On 30 Jun 2017, at 02:38, James Peach  wrote:
> >
> >
> >> On Jun 29, 2017, at 3:53 PM, Thodoris Zois  wrote:
> >>
> >> Hello, i would like to get some metrics per task. E.g memory/cpu usage
> is there any way?
> >>
> >> Thank you!
> >
> > You can use the GET_CONTAINERS agent API call <
> http://mesos.apache.org/documentation/latest/operator-http-api/> to get
> resource usage for a container, then match up the container to a task by
> using other master and agent APIs to match the framework ID and executor ID.
> >
> > J
>
>

Re: Mesos-Metrics per task

[Tomek Janiszewski]

You can capture it for Mesos API. Take a look at Mesos UI to see how it's
doing it or use Diamond Mesos Collector [1] to query Mesos API and push
metrics to metrics store.

1:
https://github.com/python-diamond/Diamond/blob/master/src/collectors/mesos/mesos.py

pt., 30.06.2017, 00:53 użytkownik Thodoris Zois  napisał:

> Hello, i would like to get some metrics per task. E.g memory/cpu usage is
> there any way?
>
> Thank you!
>

Re: [Marathon] Weird restart behaviour

[Tomek Janiszewski]

Can you provide some logs? Why do you have to restart Mesos masters? What
happen to Mesos?

wt., 27 cze 2017 o 15:49 użytkownik Jean-Baptiste 
napisał:

> Hi there,
>
>
> I have new question for you guys. I’ve noticed that each time I have to
> restart Marathon, I have to restart Mesos masters services too.
>
>
> So in the order:
>
>
>1. Restart Marathon (fail by doesn’t allow to deploy anything)
>2. Restart Mesos masters
>3. Restart Marathon
>
>
> Then it works.
>
>
> Actually, I really have no idea of what is going on because I can’t see
> the link they could have together to generate this.
>
> Do you guys think that it could be related to *Debian* startup scripts?
> Or any idea?
>
>
> Thanks!
>
> *Misc:*
>
>- *Marathon version:** 1.4.5-1.0.654.debian81
>- *Mesos version:** 1.1.0-2.0.107.debian81
>- *Debian version:** 8.7
>
>
> --
>
> Jean-Baptiste FAREZ
>

Re: Mesos (and Marathon) port mapping

[Tomek Janiszewski]

I have a question that is related to this topic. In "docker support and
current limitations" section [1] there is a following statement:
> Only host network is supported. We will add bridge network support soon
using CNI support in Mesos (MESOS-4641
)
Mentioned issue is resolved. Does this means bridge network is working for
Mesos containerizer?

[1]:
https://github.com/apache/mesos/blob/master/docs/container-image.md#docker-support-and-current-limitations

pt., 31 mar 2017 o 02:04 użytkownik Jie Yu  napisał:

> are you talking about the NAT feature of docker in BRIDGE m
>
>
> Yes
>
>  - regarding the "port mapping isolator giving network namespace" : what
> confuses me is that, given the previous answers, I thought that in that
> case, the non-ephemeral port range was *shared* (as a ressource) between
> containers, which sounds to me at the opposite of the namespace concept (as
> a slightly different example 2 docker container have their own private 80
> port for instance).
>
>
> The port mapping isolator is for the case where ip per container is not
> possible (due to ipam restriction, etc), but the user still wants to have
> network namespace per container (for isolation, getting statistics, etc.)
>
> Since all containers, even if they are in separate namespaces, share the
> same IP, we have to use some other mechanism to tell which packet belongs
> to which container. We use ports in that case. You can find more details
> about port mapping isolator in this talk I gave in 2015 MesosCon:
> https://www.youtube.com/watch?v=ZA96g1M4v8Y
>
> - Jie
>
> On Thu, Mar 30, 2017 at 2:13 AM, Thomas HUMMEL 
> wrote:
>
>
> On 03/29/2017 07:25 PM, Jie Yu wrote:
>
> Thomas,
>
> I think you are confused about the port mapping for NAT purpose, and the port
> mapping isolator
> .
> Those two very different thing. The port mapping isolator (unfortunate
> naming), as described in the doc, gives you network namespace per container
> without requiring ip per container. No NAT is involved. I think for you
> case, you should not use it and it does not work for DockerContainerizer.
>
> Thanks,
>
> I'm not sure to understand what you say :
>
> - are you talking about the NAT feature of docker in BRIDGE mode ?
>
> - regarding the "port mapping isolator giving network namespace" : what
> confuses me is that, given the previous answers, I thought that in that
> case, the non-ephemeral port range was *shared* (as a ressource) between
> containers, which sounds to me at the opposite of the namespace concept (as
> a slightly different example 2 docker container have their own private 80
> port for instance).
>
> What am I missing ?
>
> Thanks
>
> --
> TH
>
>
>

Re: Detect when mesos agent needs work directory cleanup

[Tomek Janiszewski]

1. Cleanup in required when agent configuration is not compatible with
previous version. This mean task runtime change. This occurs when:
resources, isolators, attributes or containerizers change.
2. IMO it's OK. When you reboot node all its tasks are gone so you won't
lose anything. Node will be registered as a new node.

śr., 22.03.2017, 15:55 użytkownik Michele Bertasi <
michele.bert...@brightcomputing.com> napisał:

> Hi everybody,
>
> I'm having troubles with the cleanup of the mesos agent work directory.
> When we change some configuration parameters to the agent (e.g. the
> --resource flag), the agent refuses to start and asks the removal of
> */var/lib/mesos-agent/meta/slaves/latest* in the logs.
>
> Since we are automating these changes, we would like to know when to
> perform this cleanup programmatically.
>
> Right now we are doing that *after every single change*, but that's not
> ideal, since every time mesos master assigns a new ID to the slave. It
> seems unnecessary to me.
>
> My questions are:
>
>- is there a way to know when this cleanup is needed (without looking
>at the logs)?
>- do we have problems if we clean up the work directory every time the
>node boots (so the configuration might or might not have been changed at
>all)?
>
>
> Thanks, kind regards,
>
> Mike
>

Re: best practices for log rotation

[Tomek Janiszewski]

We are using logrotate to rotate, compress and delete old data. To keep
logs easier to search we put them into Elastic/Kibana.

wt., 24.01.2017, 18:20 użytkownik Charles Allen <
charles.al...@metamarkets.com> napisał:

> Anyone have good hints for best practices for log rotation?
>
> Our mesos master ended up with many gigabytes of logs once we started
> running SPARK on it (approx 2GB of master INFO logs per day).
>

Re: Why task environment variables are set for executor/containerizer?

[Tomek Janiszewski]

Created issue: https://issues.apache.org/jira/browse/MESOS-6945

śr., 18 sty 2017 o 17:54 użytkownik Jie Yu  napisał:

> Can you create a ticket for that? I personally want to fix that for
> command executor.
>
> - Jie
>
> On Wed, Jan 18, 2017 at 5:52 PM, Jie Yu  wrote:
>
> Daniel,
>
> Yes, this is a tech debt in the old command executor. The new default
> executor does not have this issue.
>
> - Jie
>
> On Wed, Jan 18, 2017 at 5:49 PM, Daniel Krawczyk 
> wrote:
>
> Hi,
>
> When I set an environment variable for my task it is as well applied both
> to mesos-containerizer and mesos-executor.
> This may lead to problems, for example when loading dynamic libraries with
> LD_PRELOAD.
>
> Is setting task variables to executor/containerizer a bug?
>
> Cheers,
> Daniel
>
>
>
>

Re: Default executor grace period

[Tomek Janiszewski]

Created issue for this: https://issues.apache.org/jira/browse/MESOS-6933

pon., 16 sty 2017 o 17:13 użytkownik Tomek Janiszewski <jani...@gmail.com>
napisał:

> I looks like it's supported because executor prints grace period[1]. On
> the other hand executor launches sh that launch command and shell executes
> faster then command after receiving SIGTERM. Causing process to be attached
> to init and leaked. In my opinion default executor should not sent SIGTERM
> to sh but only to its children. This will allow proper escalation to
> SIGKILL because sh will leave as long its children are alive.
>
> 1:
> https://github.com/apache/mesos/blob/c4667d6f1b49d30089e6cb5874b6737a9bd3f044/src/launcher/executor.cpp#L479-L480
>
> pon., 16 sty 2017 o 16:35 użytkownik haosdent <haosd...@gmail.com>
> napisał:
>
> It looks like default-executor have not yet handle
> `--executor_shutdown_grace_period`。
>
> On Mon, Jan 16, 2017 at 7:41 PM, Tomek Janiszewski <jani...@gmail.com>
> wrote:
>
> Hi
>
> I tried to use grace period with default Mesos executor. I assumed it
> works as follow:
>
>1. Start command: sh -c "command ..."
>2. Sent SIGSTOP to process tree: sh, command
>3. Sent SIGTERM to process tree: sh, command
>4. Wait for processes to finish or grace period to elapse
>5. sh finish while command could be still running and attached to init
>6. Sent SIGKILL to process tree: command
>
> I notice that SIGKILL is not sent and executor finished when sh returns.
> When Mesos is running with POSIX contenerizer this leads command to live
> forever (if it ignores SIGTERM). When contenerizer is used command is
> killed when it's container is destroyed.
>
> Is this desired behavior? How to use grace period with default executor?
>
> Thanks
> Tomek
>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>
>

Re: Default executor grace period

[Tomek Janiszewski]

I looks like it's supported because executor prints grace period[1]. On the
other hand executor launches sh that launch command and shell executes
faster then command after receiving SIGTERM. Causing process to be attached
to init and leaked. In my opinion default executor should not sent SIGTERM
to sh but only to its children. This will allow proper escalation to
SIGKILL because sh will leave as long its children are alive.

1:
https://github.com/apache/mesos/blob/c4667d6f1b49d30089e6cb5874b6737a9bd3f044/src/launcher/executor.cpp#L479-L480

pon., 16 sty 2017 o 16:35 użytkownik haosdent <haosd...@gmail.com> napisał:

> It looks like default-executor have not yet handle
> `--executor_shutdown_grace_period`。
>
> On Mon, Jan 16, 2017 at 7:41 PM, Tomek Janiszewski <jani...@gmail.com>
> wrote:
>
> Hi
>
> I tried to use grace period with default Mesos executor. I assumed it
> works as follow:
>
>1. Start command: sh -c "command ..."
>2. Sent SIGSTOP to process tree: sh, command
>3. Sent SIGTERM to process tree: sh, command
>4. Wait for processes to finish or grace period to elapse
>5. sh finish while command could be still running and attached to init
>6. Sent SIGKILL to process tree: command
>
> I notice that SIGKILL is not sent and executor finished when sh returns.
> When Mesos is running with POSIX contenerizer this leads command to live
> forever (if it ignores SIGTERM). When contenerizer is used command is
> killed when it's container is destroyed.
>
> Is this desired behavior? How to use grace period with default executor?
>
> Thanks
> Tomek
>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Re: Command healthcheck failed but status KILLED

[Tomek Janiszewski]

Thanks Gastón. Do we have a shepherd for this? It's not critical but make
it hard to distinguish task killed by failed health check from killed by
scheduler.

wt., 13.12.2016 o 16:55 użytkownik Gastón Kleiman <gas...@mesosphere.io>
napisał:

> On Mon, Dec 12, 2016 at 12:47 PM, Tomek Janiszewski <jani...@gmail.com>
> wrote:
>
> > It there any information that kill is the result of failed healthcheck?
> > TaskHealthStatus should have some details on what was wrong. When default
> > executor is killing task it should add a reason and details to
> TaskStatus.
> > What do you think?
> >
>
> I agree with you, so I created
> https://issues.apache.org/jira/browse/MESOS-6786 with some ideas.
>
> -Gastón
>

Re: Command healthcheck failed but status KILLED

[Tomek Janiszewski]

It there any information that kill is the result of failed healthcheck?
TaskHealthStatus should have some details on what was wrong. When default
executor is killing task it should add a reason and details to TaskStatus.
What do you think?

pon., 12.12.2016 o 11:11 użytkownik Alex Rukletsov <a...@mesosphere.com>
napisał:

> Technically the task hast not failed but was killed by the executor
> (because it failed a health check).
>
> On Fri, Dec 9, 2016 at 11:27 AM, Tomek Janiszewski <jani...@gmail.com>
> wrote:
>
> > Hi
> >
> > What is desired behavior when command health check failed? On Mesos 1.0.2
> > when health check fails task has state KILLED instead of FAILED with
> reason
> > specifying it was killed due to failing health check.
> >
> > Thanks
> > Tomek
> >
>

Command healthcheck failed but status KILLED

[Tomek Janiszewski]

Hi

What is desired behavior when command health check failed? On Mesos 1.0.2
when health check fails task has state KILLED instead of FAILED with reason
specifying it was killed due to failing health check.

Thanks
Tomek

Re: Failure reason documentation

[Tomek Janiszewski]

Hi

Are you referring to task state? If yes then take a look at comments in
proto
https://github.com/apache/mesos/blob/master/include/mesos/mesos.proto#L1552
http://mesos.apache.org/api/latest/java/org/apache/mesos/Protos.TaskState.html

Best
Tomek

pt., 2.12.2016, 21:31 użytkownik Wil Yegelwel  napisał:

> Hey mesos users!
>
> I can't seem to find any documentation about the various reasons mesos
> includes when a job fails. Is there a place that describes what the reasons
> mean?
>
> Thanks,
> Wil
>

Re: Docker snadbox disk statistics

[Tomek Janiszewski]

Thanks. I was suspecting Mesos isolators do not work for Docker but hoping
there is some trick to turn it on.

Thanks
Tomek

czw., 3.11.2016 o 17:46 użytkownik Jie Yu <yujie@gmail.com> napisał:

> posix/disk isolator is for MesosContaineizer only. If you're using docker
> containerizer, this won't work.
>
> Or you can use MesosContainerizer to launch you docker image, and then,
> you'll get the sandbox size properly.
> https://github.com/apache/mesos/blob/master/docs/container-image.md
>
>
> - Jie
>
> On Thu, Nov 3, 2016 at 9:41 AM, Tomek Janiszewski <jani...@gmail.com>
> wrote:
>
> Hi
>
> Is it possible to get information about Docker sandboxes size? When I
> visit monitor/statistics there is no information about disk? I have enabled
> posix/disk isolation and working on 0.28.2
>
> Thanks
> Tomek
>
>
>

Re: Programmatically retrieve stdout/stderr from a node

[Tomek Janiszewski]

Oh, now I got it. To get path you need to query agent for it's state
with /slave(1)/state. In response you will get JSON. Path to sandbox is
stored in .frameworks[].executors[].directory.

śr., 10.08.2016 o 17:34 użytkownik June Taylor <j...@umn.edu> napisał:

> Tomek,
>
> I'm not sure I understand your suggestion. We know how to ask for a file
> from an HTTP endpoint, but it is the construction of the correct URL which
> is not currently clear.
>
> We are not sure how to determine the Run ID of the executor.
>
>
> Thanks,
> June Taylor
> System Administrator, Minnesota Population Center
> University of Minnesota
>
> On Wed, Aug 10, 2016 at 10:08 AM, Tomek Janiszewski <jani...@gmail.com>
> wrote:
>
>> Hi
>>
>> If you need simplest method then python SimpleHTTPServer could help. Just
>> launch it in background before command you want to run, assign it port and
>> query sandbox with : that can be obtained from state
>> endpoint.
>>
>> -
>> Tomek
>>
>> śr., 10.08.2016 o 16:53 użytkownik June Taylor <j...@umn.edu> napisał:
>>
>>> We are trying to retrieve the stdout and stderr files from an executor
>>> programmatically.
>>>
>>> It appears that these are available via HTTP request, however,
>>> constructing the correct URL is posing to be a challenge.
>>>
>>> Our scenario is:
>>>
>>> 1. Use mesos-execute to submit a job. A framework ID is available at
>>> this point.
>>> 2. Using the framework ID, one can inquire with mesos-state to determine
>>> which slave ID is executing the task.
>>> 3. Using the slave ID, one can inquire with mesos-state to find the
>>> hostname for that slave ID
>>> 4. HTTP can be used to ask the /browse/ endpoint for a file, however,
>>> there is an Executor ID which we cannot programmatically determine, to
>>> complete this URL.
>>>
>>> Please advise the simplest option for retrieving the sandbox files given
>>> the scenario starts with mesos-execute commands.
>>>
>>> Thanks!
>>> June Taylor
>>> System Administrator, Minnesota Population Center
>>> University of Minnesota
>>>
>>
>

Re: Programmatically retrieve stdout/stderr from a node

[Tomek Janiszewski]

Hi

If you need simplest method then python SimpleHTTPServer could help. Just
launch it in background before command you want to run, assign it port and
query sandbox with : that can be obtained from state
endpoint.

-
Tomek

śr., 10.08.2016 o 16:53 użytkownik June Taylor  napisał:

> We are trying to retrieve the stdout and stderr files from an executor
> programmatically.
>
> It appears that these are available via HTTP request, however,
> constructing the correct URL is posing to be a challenge.
>
> Our scenario is:
>
> 1. Use mesos-execute to submit a job. A framework ID is available at this
> point.
> 2. Using the framework ID, one can inquire with mesos-state to determine
> which slave ID is executing the task.
> 3. Using the slave ID, one can inquire with mesos-state to find the
> hostname for that slave ID
> 4. HTTP can be used to ask the /browse/ endpoint for a file, however,
> there is an Executor ID which we cannot programmatically determine, to
> complete this URL.
>
> Please advise the simplest option for retrieving the sandbox files given
> the scenario starts with mesos-execute commands.
>
> Thanks!
> June Taylor
> System Administrator, Minnesota Population Center
> University of Minnesota
>

Re: How could Mesos work with docker?

[Tomek Janiszewski]

Hi

Docker support is described here
http://mesos.apache.org/documentation/latest/docker-containerizer/

Best
Tomek

wt., 9.08.2016 o 16:04 użytkownik Yu Wei  napisał:

> Hi guys,
>
> I start learning mesos.
>
> How could mesos work with docker? Is there any document about this?
>
>
> Any other advice?
>
>
> Thx,
>
>
> Jared, (韦煜）
> Software developer
> Interested in open source software, big data, Linux
>

Re: Having slaves notify masters of other resources/properties of the slave?

[Tomek Janiszewski]

To run tasks on Mesos you need scheduler/framework
http://mesos.apache.org/documentation/latest/architecture/ You can write
one on your own or use some existing  like Marathon depending on your
needs.
Both HTTP API and native API supports constraints but at offer accepting
level.

sob., 23.07.2016, 15:04 użytkownik Mark Hammons <
mark.hamm...@inaf.cnrs-gif.fr> napisał:

> Should I be using marathon on top of my Mesos? Or just the raw mesos http
> apis? The java api for mesos does not seem to have the ability to use
> constraints.
>
>
>
> On Saturday, July 23, 2016 12:44:10 PM Tomek Janiszewski wrote:
>
> > You can define roles that allows you to reserve resources for specific
>
> > frameworks http://mesos.apache.org/documentation/latest/roles/
>
> > You can also mark agents with attributes. Then framework could filter
>
> > offers based on that attributes
>
> > http://mesos.apache.org/documentation/latest/attributes-resources/
>
> > What framework are you using? If marathon then attributes will be easiest
>
> > option. After adding agent attributes, add constraints to you app
>
> > definition https://mesosphere.github.io/marathon/docs/constraints.html
>
> >
>
> > sob., 23.07.2016, 14:37 użytkownik Mark Hammons <
>
> >
>
> > mark.hamm...@inaf.cnrs-gif.fr> napisał:
>
> > > I'm sorry, I'm still fairly new to mesos, so I'm not sure what this
> means
>
> > > or how to do that. Could you link to some documentation or an example
> that
>
> > > discusses this in more detail?
>
> > >
>
> > > On Saturday, July 23, 2016 12:32:52 PM Tomek Janiszewski wrote:
>
> > > > You can mark all slave resources as cuda role or add attribute to run
>
> > >
>
> > > tasks
>
> > >
>
> > > > on this agent.
>
> > >
>
> > > --
>
> > >
>
> > > Mark Hammons - +33 06 03 69 56 56
>
> > >
>
> > > Research Engineer @ BioEmergences <http://bioemergences.iscpif.fr>
>
> > >
>
> > > Lab Phone: 01 69 82 34 19
> --
>
> Mark Hammons - +33 06 03 69 56 56
>
> Research Engineer @ BioEmergences <http://bioemergences.iscpif.fr>
>
> Lab Phone: 01 69 82 34 19
>

Re: Having slaves notify masters of other resources/properties of the slave?

[Tomek Janiszewski]

You can define roles that allows you to reserve resources for specific
frameworks http://mesos.apache.org/documentation/latest/roles/
You can also mark agents with attributes. Then framework could filter
offers based on that attributes
http://mesos.apache.org/documentation/latest/attributes-resources/
What framework are you using? If marathon then attributes will be easiest
option. After adding agent attributes, add constraints to you app
definition https://mesosphere.github.io/marathon/docs/constraints.html

sob., 23.07.2016, 14:37 użytkownik Mark Hammons <
mark.hamm...@inaf.cnrs-gif.fr> napisał:

> I'm sorry, I'm still fairly new to mesos, so I'm not sure what this means
> or how to do that. Could you link to some documentation or an example that
> discusses this in more detail?
>
>
>
> On Saturday, July 23, 2016 12:32:52 PM Tomek Janiszewski wrote:
>
> > You can mark all slave resources as cuda role  or add attribute to run
> tasks
>
> > on this agent.
> --
>
> Mark Hammons - +33 06 03 69 56 56
>
> Research Engineer @ BioEmergences <http://bioemergences.iscpif.fr>
>
> Lab Phone: 01 69 82 34 19
>

Re: Having slaves notify masters of other resources/properties of the slave?

[Tomek Janiszewski]

Hi

You can mark all slave resources as cuda role  or add attribute to run
tasks on this agent.

Best
Tomek

sob., 23.07.2016, 14:21 użytkownik Mark Hammons <
mark.hamm...@inaf.cnrs-gif.fr> napisał:

> Is there any way to have a slave specify that it is capable of running
> cuda apps, and make it to where tasks that request cuda resources are only
> executed on those slaves?
> --
>
> Mark Hammons - +33 06 03 69 56 56
>
> Research Engineer @ BioEmergences 
>
> Lab Phone: 01 69 82 34 19
>

Re: What's the official pronounce of mesos?

[Tomek Janiszewski]

This question was answered at MesosCon Europe last year
https://youtu.be/K-x7yOy8Ymk?t=28m37s

czw., 14.07.2016 o 04:12 użytkownik Paul  napisał:

> Sadly, I don't understand a whole lot about Mesos, but I did learn Ancient
> Greek in college, taught it for a couple of years, and have even translated
> parts of Homer's Iliad.
>
>  *μέσος*
>
> The 'e' (epsilon) in 'Mesos' would be pronounced like the 'e' in the
> English word 'pet'. The 'o' (omicron) as in 'hot'.
>
> But, at least to English ears, that pronunciation feels a bit stilted. So
> I think Rodrick's right to sound the 'o' as long, as in 'tone'.
>
> -Paul
>
> On Jul 13, 2016, at 9:12 PM, Rodrick Brown 
> wrote:
>
> Mess-O's
>
> Get Outlook for iOS 
>
>
>
>
> On Wed, Jul 13, 2016 at 7:56 PM -0400, "zhiwei"  wrote:
>
> Hi,
>>
>> I saw in some videos, different people pronounce 'mesos' differently.
>>
>> Can someone add the official pronounce of mesos to wikipedia?
>>
>
> *NOTICE TO RECIPIENTS*: This communication is confidential and intended
> for the use of the addressee only. If you are not an intended recipient of
> this communication, please delete it immediately and notify the sender by
> return email. Unauthorized reading, dissemination, distribution or copying
> of this communication is prohibited. This communication does not constitute
> an offer to sell or a solicitation of an indication of interest to purchase
> any loan, security or any other financial product or instrument, nor is it
> an offer to sell or a solicitation of an indication of interest to purchase
> any products or services to any persons who are prohibited from receiving
> such information under applicable law. The contents of this communication
> may not be accurate or complete and are subject to change without notice.
> As such, Orchard App, Inc. (including its subsidiaries and affiliates,
> "Orchard") makes no representation regarding the accuracy or completeness
> of the information contained herein. The intended recipient is advised to
> consult its own professional advisors, including those specializing in
> legal, tax and accounting matters. Orchard does not provide legal, tax or
> accounting advice.
>
>

Re: Executor downloads for every task

[Tomek Janiszewski]

You can use Fetching through the cache
 to download file
only once.

śr., 29.06.2016 o 15:19 użytkownik Scott Weiss  napisał:

> Every time my framework launches a task, it downloads the (custom)
> executor from the URI I provide. then when the task finishes executing, the
> framework gets the message Executor lost. this seems to cause the slaves to
> download the executor binary every time they launch a task. Is there a way
> to keep the executor binary on the slaves so it only has to be downloaded
> one time?
>

Re: Shell Environment Variables

[Tomek Janiszewski]

$HOME could be unset then homedir is looked in passwd. I had the same issue
when I was trying to map homedir with Shared Filesystem Isolator but I
thought it was issue with my setup. It will be great if this get resolved.

pt., 17.06.2016, 19:11 użytkownik Jie Yu  napisał:

> Hansel, I think it was definitely not intentional. I am wondering what
> happens if the user does not have a home directory, what should $HOME be?
>
> - Jie
>
> On Fri, Jun 17, 2016 at 9:08 AM,  wrote:
>
>> Hi Haosdent,
>>
>> Yes, I had confirmed that setuid does get called correctly, and the shell
>> environment is not set up. My question is more along the lines of "is this
>> expected? is it a bug? is it intentional?"
>> If it wasn't intentional, I was thinking maybe I'll try a making a small
>> patch to see if it works out.
>>
>> I couldn't find the JIRA ticket. Happen to know what it was or anything
>> it might be referring to?
>>
>> Thanks,
>> -Hansel
>>
>> On Jun 16, 2016, at 8:00 PM, haosdent  wrote:
>>
>> Hi, @Hansel Chung As I checked, if --swithc_user=true (default variable
>> is true) when you launch Mesos agent, executor would call os::setuid
>> and os::setgroups before launch your tasks. But the shell environment may
>> not set. (I remember we have a ticket for this.) You could use `id` as your
>> task command to verify if user set correctly.
>>
>>
>> On Fri, Jun 17, 2016 at 9:17 AM, Hansel Chung 
>> wrote:
>>
>>> Hi,
>>>
>>> I had a question, I noticed that if mesos frameworks request that
>>> executors use a certain user, the env variables aren't set up for that
>>> user, but what the agent daemon was run as.
>>>
>>> As an example:
>>> Run mesos-slave as root:
>>> HOME=/root
>>> USER=root
>>>
>>> If I have an executor to be launched as testuser, the env looks like:
>>> HOME=/root
>>> USER=root
>>> instead of:
>>> HOME=/home/testuser
>>> USER=testuser
>>>
>>> This is normally set by login or sudo when running as a user, but I
>>> can't seem to find a way to use these to set up a proper environment as the
>>> target user. Is there a reason we don't call getpwuid() to set a
>>> $HOME during setup of execlp() from executor.cpp? (Oh, and might as well
>>> populate $USER while we're at it)
>>>
>>> Thanks,
>>> -Hansel
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Haosdent Huang
>>
>>
>>
>

Re: Proposal: move content in Wiki to docs in code repo

[Tomek Janiszewski]

It's working.
Thanks

czw., 9.06.2016 o 17:06 użytkownik Vinod Kone <vinodk...@apache.org>
napisał:

> Done. Let me know if you have edit access now.
>
> On Thu, Jun 9, 2016 at 11:01 AM, Tomek Janiszewski <jani...@gmail.com>
> wrote:
>
> > @Vinod I've just create the account - Tomasz Janiszewski (janisz)
> >
> > Thanks
> >
> > czw., 9.06.2016, 16:52 użytkownik Vinod Kone <vinodk...@apache.org>
> > napisał:
> >
> >> I can give you edit access if you send me your account name (you might
> >> have to create one if you haven't already) on cwiki.apache.org
> >>
> >> On Thu, Jun 9, 2016 at 4:48 AM, Tomek Janiszewski <jani...@gmail.com>
> >> wrote:
> >>
> >>> @Jie could you sent me a markup from confluence editor. I have no edit
> >>> access and it will be easier to work with markup than scraping web
> page to
> >>> get data.
> >>>
> >>> czw., 9.06.2016 o 09:37 użytkownik Tomek Janiszewski <
> jani...@gmail.com>
> >>> napisał:
> >>>
> >>>> I'll post patches by the end of the week.
> >>>>
> >>>> czw., 9.06.2016 o 02:23 użytkownik Jie Yu <yujie@gmail.com>
> >>>> napisał:
> >>>>
> >>>>> Great! Looks like we have a consensus here!
> >>>>>
> >>>>> Tomek, you mentioned that you're interested in helping the move.
> Thank
> >>>>> you so much. Can you start with moving the following wiki pages
> first as
> >>>>> they are quite important:
> >>>>>
> >>>>> 1)
> >>>>>
> https://cwiki.apache.org/confluence/display/MESOS/Apache+Mesos+Working+Groups
> >>>>> 2)
> >>>>>
> https://cwiki.apache.org/confluence/display/MESOS/Design+docs+--+Shared+Links
> >>>>> 3)
> >>>>>
> https://cwiki.apache.org/confluence/display/MESOS/Mesos+Release+Planning
> >>>>>
> >>>>> Thanks a lot!
> >>>>> - Jie
> >>>>>
> >>>>> On Tue, Jun 7, 2016 at 5:39 AM, tommy xiao <xia...@gmail.com> wrote:
> >>>>>
> >>>>>> +1, good point.
> >>>>>>
> >>>>>> 2016-06-07 3:18 GMT+08:00 Vinod Kone <vinodk...@apache.org>:
> >>>>>>
> >>>>>>> Works for me. Some things we might miss from wiki would be comments
> >>>>>>> and ability to watch for updates; but I don't think many people
> use them.
> >>>>>>>
> >>>>>>> On Mon, Jun 6, 2016 at 3:15 PM, Gilbert Song <
> gilb...@mesosphere.io>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> +1.
> >>>>>>>>
> >>>>>>>> At least I personally rarely touch the wiki.
> >>>>>>>>
> >>>>>>>> Gilbert
> >>>>>>>>
> >>>>>>>> On Mon, Jun 6, 2016 at 11:51 AM, Zhou Z Xing <xingz...@cn.ibm.com
> >
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> +1
> >>>>>>>>>
> >>>>>>>>> It's good idea to collect and gather every thing in one single
> >>>>>>>>> repo, would be easier for users to find out.
> >>>>>>>>>
> >>>>>>>>> Thanks & Best Wishes,
> >>>>>>>>>
> >>>>>>>>> Tom Xing(邢舟)
> >>>>>>>>> Emerging Technology Institute, IBM China Software Development Lab
> >>>>>>>>> --
> >>>>>>>>> IBM China Software Development Laboratory (CSDL)
> >>>>>>>>> Notes ID:Zhou Z Xing/China/IBM
> >>>>>>>>> Phone :86-10-82450442
> >>>>>>>>> e-Mail :xingz...@cn.ibm.com
> >>>>>>>>> Address :Building No.28, ZhongGuanCun Software Park, No.8 Dong
> Bei
> >>>>>>>>> Wang West Road, Haidian District, Beijing, P.R.China 100193
> >>>>>>>>> 地址 :中国北京市海淀区东北旺西路8号 中关村软件园28号楼 100193
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> [image: Inactive hide details for Jie Yu ---2016-06-06 上午
> >>>>>>>>> 11:29:42---Hi folks, I am proposing moving our content in Wiki
> (e.g., wor]Jie
> >>>>>>>>> Yu ---2016-06-06 上午 11:29:42---Hi folks, I am proposing moving
> our content
> >>>>>>>>> in Wiki (e.g., working groups, release
> >>>>>>>>>
> >>>>>>>>> From: Jie Yu <yujie@gmail.com>
> >>>>>>>>> To: mesos <d...@mesos.apache.org>, "user@mesos.apache.org" <
> >>>>>>>>> user@mesos.apache.org>
> >>>>>>>>> Date: 2016-06-06 上午 11:29
> >>>>>>>>> Subject: Proposal: move content in Wiki to docs in code repo
> >>>>>>>>> --
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Hi folks,
> >>>>>>>>>
> >>>>>>>>> I am proposing moving our content in Wiki (e.g., working groups,
> >>>>>>>>> release
> >>>>>>>>> tracking, etc.) to our docs in the code repo. I personally found
> >>>>>>>>> that wiki
> >>>>>>>>> is hard to use and there's no reviewing process for changes in
> the
> >>>>>>>>> Wiki.
> >>>>>>>>> The content in Wiki historically received less attention than
> that
> >>>>>>>>> in the
> >>>>>>>>> docs.
> >>>>>>>>>
> >>>>>>>>> What do you think?
> >>>>>>>>>
> >>>>>>>>> - Jie
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Deshi Xiao
> >>>>>> Twitter: xds2000
> >>>>>> E-mail: xiaods(AT)gmail.com
> >>>>>>
> >>>>>
> >>>>>
> >>
>

Re: Proposal: move content in Wiki to docs in code repo

[Tomek Janiszewski]

@Vinod I've just create the account - Tomasz Janiszewski (janisz)

Thanks

czw., 9.06.2016, 16:52 użytkownik Vinod Kone <vinodk...@apache.org> napisał:

> I can give you edit access if you send me your account name (you might
> have to create one if you haven't already) on cwiki.apache.org
>
> On Thu, Jun 9, 2016 at 4:48 AM, Tomek Janiszewski <jani...@gmail.com>
> wrote:
>
>> @Jie could you sent me a markup from confluence editor. I have no edit
>> access and it will be easier to work with markup than scraping web page to
>> get data.
>>
>> czw., 9.06.2016 o 09:37 użytkownik Tomek Janiszewski <jani...@gmail.com>
>> napisał:
>>
>>> I'll post patches by the end of the week.
>>>
>>> czw., 9.06.2016 o 02:23 użytkownik Jie Yu <yujie@gmail.com> napisał:
>>>
>>>> Great! Looks like we have a consensus here!
>>>>
>>>> Tomek, you mentioned that you're interested in helping the move. Thank
>>>> you so much. Can you start with moving the following wiki pages first as
>>>> they are quite important:
>>>>
>>>> 1)
>>>> https://cwiki.apache.org/confluence/display/MESOS/Apache+Mesos+Working+Groups
>>>> 2)
>>>> https://cwiki.apache.org/confluence/display/MESOS/Design+docs+--+Shared+Links
>>>> 3)
>>>> https://cwiki.apache.org/confluence/display/MESOS/Mesos+Release+Planning
>>>>
>>>> Thanks a lot!
>>>> - Jie
>>>>
>>>> On Tue, Jun 7, 2016 at 5:39 AM, tommy xiao <xia...@gmail.com> wrote:
>>>>
>>>>> +1, good point.
>>>>>
>>>>> 2016-06-07 3:18 GMT+08:00 Vinod Kone <vinodk...@apache.org>:
>>>>>
>>>>>> Works for me. Some things we might miss from wiki would be comments
>>>>>> and ability to watch for updates; but I don't think many people use them.
>>>>>>
>>>>>> On Mon, Jun 6, 2016 at 3:15 PM, Gilbert Song <gilb...@mesosphere.io>
>>>>>> wrote:
>>>>>>
>>>>>>> +1.
>>>>>>>
>>>>>>> At least I personally rarely touch the wiki.
>>>>>>>
>>>>>>> Gilbert
>>>>>>>
>>>>>>> On Mon, Jun 6, 2016 at 11:51 AM, Zhou Z Xing <xingz...@cn.ibm.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> It's good idea to collect and gather every thing in one single
>>>>>>>> repo, would be easier for users to find out.
>>>>>>>>
>>>>>>>> Thanks & Best Wishes,
>>>>>>>>
>>>>>>>> Tom Xing(邢舟)
>>>>>>>> Emerging Technology Institute, IBM China Software Development Lab
>>>>>>>> --
>>>>>>>> IBM China Software Development Laboratory (CSDL)
>>>>>>>> Notes ID:Zhou Z Xing/China/IBM
>>>>>>>> Phone :86-10-82450442
>>>>>>>> e-Mail :xingz...@cn.ibm.com
>>>>>>>> Address :Building No.28, ZhongGuanCun Software Park, No.8 Dong Bei
>>>>>>>> Wang West Road, Haidian District, Beijing, P.R.China 100193
>>>>>>>> 地址 :中国北京市海淀区东北旺西路8号 中关村软件园28号楼 100193
>>>>>>>>
>>>>>>>>
>>>>>>>> [image: Inactive hide details for Jie Yu ---2016-06-06 上午
>>>>>>>> 11:29:42---Hi folks, I am proposing moving our content in Wiki (e.g., 
>>>>>>>> wor]Jie
>>>>>>>> Yu ---2016-06-06 上午 11:29:42---Hi folks, I am proposing moving our 
>>>>>>>> content
>>>>>>>> in Wiki (e.g., working groups, release
>>>>>>>>
>>>>>>>> From: Jie Yu <yujie@gmail.com>
>>>>>>>> To: mesos <d...@mesos.apache.org>, "user@mesos.apache.org" <
>>>>>>>> user@mesos.apache.org>
>>>>>>>> Date: 2016-06-06 上午 11:29
>>>>>>>> Subject: Proposal: move content in Wiki to docs in code repo
>>>>>>>> --
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi folks,
>>>>>>>>
>>>>>>>> I am proposing moving our content in Wiki (e.g., working groups,
>>>>>>>> release
>>>>>>>> tracking, etc.) to our docs in the code repo. I personally found
>>>>>>>> that wiki
>>>>>>>> is hard to use and there's no reviewing process for changes in the
>>>>>>>> Wiki.
>>>>>>>> The content in Wiki historically received less attention than that
>>>>>>>> in the
>>>>>>>> docs.
>>>>>>>>
>>>>>>>> What do you think?
>>>>>>>>
>>>>>>>> - Jie
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Deshi Xiao
>>>>> Twitter: xds2000
>>>>> E-mail: xiaods(AT)gmail.com
>>>>>
>>>>
>>>>
>

Re: Proposal: move content in Wiki to docs in code repo

[Tomek Janiszewski]

@Jie could you sent me a markup from confluence editor. I have no edit
access and it will be easier to work with markup than scraping web page to
get data.

czw., 9.06.2016 o 09:37 użytkownik Tomek Janiszewski <jani...@gmail.com>
napisał:

> I'll post patches by the end of the week.
>
> czw., 9.06.2016 o 02:23 użytkownik Jie Yu <yujie@gmail.com> napisał:
>
>> Great! Looks like we have a consensus here!
>>
>> Tomek, you mentioned that you're interested in helping the move. Thank
>> you so much. Can you start with moving the following wiki pages first as
>> they are quite important:
>>
>> 1)
>> https://cwiki.apache.org/confluence/display/MESOS/Apache+Mesos+Working+Groups
>> 2)
>> https://cwiki.apache.org/confluence/display/MESOS/Design+docs+--+Shared+Links
>> 3)
>> https://cwiki.apache.org/confluence/display/MESOS/Mesos+Release+Planning
>>
>> Thanks a lot!
>> - Jie
>>
>> On Tue, Jun 7, 2016 at 5:39 AM, tommy xiao <xia...@gmail.com> wrote:
>>
>>> +1, good point.
>>>
>>> 2016-06-07 3:18 GMT+08:00 Vinod Kone <vinodk...@apache.org>:
>>>
>>>> Works for me. Some things we might miss from wiki would be comments and
>>>> ability to watch for updates; but I don't think many people use them.
>>>>
>>>> On Mon, Jun 6, 2016 at 3:15 PM, Gilbert Song <gilb...@mesosphere.io>
>>>> wrote:
>>>>
>>>>> +1.
>>>>>
>>>>> At least I personally rarely touch the wiki.
>>>>>
>>>>> Gilbert
>>>>>
>>>>> On Mon, Jun 6, 2016 at 11:51 AM, Zhou Z Xing <xingz...@cn.ibm.com>
>>>>> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> It's good idea to collect and gather every thing in one single repo,
>>>>>> would be easier for users to find out.
>>>>>>
>>>>>> Thanks & Best Wishes,
>>>>>>
>>>>>> Tom Xing(邢舟)
>>>>>> Emerging Technology Institute, IBM China Software Development Lab
>>>>>> --
>>>>>> IBM China Software Development Laboratory (CSDL)
>>>>>> Notes ID:Zhou Z Xing/China/IBM
>>>>>> Phone :86-10-82450442
>>>>>> e-Mail :xingz...@cn.ibm.com
>>>>>> Address :Building No.28, ZhongGuanCun Software Park, No.8 Dong Bei
>>>>>> Wang West Road, Haidian District, Beijing, P.R.China 100193
>>>>>> 地址 :中国北京市海淀区东北旺西路8号 中关村软件园28号楼 100193
>>>>>>
>>>>>>
>>>>>> [image: Inactive hide details for Jie Yu ---2016-06-06 上午
>>>>>> 11:29:42---Hi folks, I am proposing moving our content in Wiki (e.g., 
>>>>>> wor]Jie
>>>>>> Yu ---2016-06-06 上午 11:29:42---Hi folks, I am proposing moving our 
>>>>>> content
>>>>>> in Wiki (e.g., working groups, release
>>>>>>
>>>>>> From: Jie Yu <yujie@gmail.com>
>>>>>> To: mesos <d...@mesos.apache.org>, "user@mesos.apache.org" <
>>>>>> user@mesos.apache.org>
>>>>>> Date: 2016-06-06 上午 11:29
>>>>>> Subject: Proposal: move content in Wiki to docs in code repo
>>>>>> --
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi folks,
>>>>>>
>>>>>> I am proposing moving our content in Wiki (e.g., working groups,
>>>>>> release
>>>>>> tracking, etc.) to our docs in the code repo. I personally found that
>>>>>> wiki
>>>>>> is hard to use and there's no reviewing process for changes in the
>>>>>> Wiki.
>>>>>> The content in Wiki historically received less attention than that in
>>>>>> the
>>>>>> docs.
>>>>>>
>>>>>> What do you think?
>>>>>>
>>>>>> - Jie
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Deshi Xiao
>>> Twitter: xds2000
>>> E-mail: xiaods(AT)gmail.com
>>>
>>
>>

Re: Proposal: move content in Wiki to docs in code repo

[Tomek Janiszewski]

I'll post patches by the end of the week.

czw., 9.06.2016 o 02:23 użytkownik Jie Yu  napisał:

> Great! Looks like we have a consensus here!
>
> Tomek, you mentioned that you're interested in helping the move. Thank you
> so much. Can you start with moving the following wiki pages first as they
> are quite important:
>
> 1)
> https://cwiki.apache.org/confluence/display/MESOS/Apache+Mesos+Working+Groups
> 2)
> https://cwiki.apache.org/confluence/display/MESOS/Design+docs+--+Shared+Links
> 3)
> https://cwiki.apache.org/confluence/display/MESOS/Mesos+Release+Planning
>
> Thanks a lot!
> - Jie
>
> On Tue, Jun 7, 2016 at 5:39 AM, tommy xiao  wrote:
>
>> +1, good point.
>>
>> 2016-06-07 3:18 GMT+08:00 Vinod Kone :
>>
>>> Works for me. Some things we might miss from wiki would be comments and
>>> ability to watch for updates; but I don't think many people use them.
>>>
>>> On Mon, Jun 6, 2016 at 3:15 PM, Gilbert Song 
>>> wrote:
>>>
 +1.

 At least I personally rarely touch the wiki.

 Gilbert

 On Mon, Jun 6, 2016 at 11:51 AM, Zhou Z Xing 
 wrote:

> +1
>
> It's good idea to collect and gather every thing in one single repo,
> would be easier for users to find out.
>
> Thanks & Best Wishes,
>
> Tom Xing(邢舟)
> Emerging Technology Institute, IBM China Software Development Lab
> --
> IBM China Software Development Laboratory (CSDL)
> Notes ID:Zhou Z Xing/China/IBM
> Phone :86-10-82450442
> e-Mail :xingz...@cn.ibm.com
> Address :Building No.28, ZhongGuanCun Software Park, No.8 Dong Bei
> Wang West Road, Haidian District, Beijing, P.R.China 100193
> 地址 :中国北京市海淀区东北旺西路8号 中关村软件园28号楼 100193
>
>
> [image: Inactive hide details for Jie Yu ---2016-06-06 上午
> 11:29:42---Hi folks, I am proposing moving our content in Wiki (e.g., 
> wor]Jie
> Yu ---2016-06-06 上午 11:29:42---Hi folks, I am proposing moving our content
> in Wiki (e.g., working groups, release
>
> From: Jie Yu 
> To: mesos , "user@mesos.apache.org" <
> user@mesos.apache.org>
> Date: 2016-06-06 上午 11:29
> Subject: Proposal: move content in Wiki to docs in code repo
> --
>
>
>
> Hi folks,
>
> I am proposing moving our content in Wiki (e.g., working groups,
> release
> tracking, etc.) to our docs in the code repo. I personally found that
> wiki
> is hard to use and there's no reviewing process for changes in the
> Wiki.
> The content in Wiki historically received less attention than that in
> the
> docs.
>
> What do you think?
>
> - Jie
>
>
>
>

>>>
>>
>>
>> --
>> Deshi Xiao
>> Twitter: xds2000
>> E-mail: xiaods(AT)gmail.com
>>
>
>

Re: Proposal: move content in Wiki to docs in code repo

[Tomek Janiszewski]

+1
For a long time I didn't knew that wiki exists. It's hidden from a new
users and search engines - I remember only one place where it's linked in
docs.
I can help with move.

pon., 6.06.2016, 20:29 użytkownik Jie Yu  napisał:

> Hi folks,
>
> I am proposing moving our content in Wiki (e.g., working groups, release
> tracking, etc.) to our docs in the code repo. I personally found that wiki
> is hard to use and there's no reviewing process for changes in the Wiki.
> The content in Wiki historically received less attention than that in the
> docs.
>
> What do you think?
>
> - Jie
>

Re: [MesosCon] Live streaming?

[Tomek Janiszewski]

That's awesome. Thanks!

czw., 26.05.2016, 20:05 użytkownik David Greenberg <dsg123456...@gmail.com>
napisał:

> And now, you can sign up to stream the keynotes here:
> http://events.linuxfoundation.org/events/mesoscon-north-america/program/live-video-stream
>
> Enjoy!
>
> On Wed, May 25, 2016 at 10:10 AM David Greenberg <dsg123456...@gmail.com>
> wrote:
>
>> Great news! This year, the keynotes will be live streamed--there will be
>> a registration page for the keynote streams up sometime tomorrow. Let us
>> know if you have any other questions :)
>>
>> Best,
>> David Greenberg, Kiersten Gaffney, Dave Lester (your friendly co-chairs)
>>
>> On Wed, May 25, 2016 at 7:19 AM haosdent <haosd...@gmail.com> wrote:
>>
>>> Oh, I remember it now. Someone use Periscope to live #MesosCon at that
>>> time https://twitter.com/TonyDong3/status/634824541244493824 , so I
>>> could see the scene from their share links.
>>>
>>> On Wed, May 25, 2016 at 9:08 PM, Tomek Janiszewski <jani...@gmail.com>
>>> wrote:
>>>
>>>> @haosdent Are you sure? I remember that everything was recorded but
>>>> not live - according to
>>>> https://twitter.com/mesoscon/status/495259388089614336 there was no
>>>> official stream.
>>>>
>>>> śr., 25.05.2016 o 15:03 użytkownik haosdent <haosd...@gmail.com>
>>>> napisał:
>>>>
>>>>> I remember last year have live streaming. :-)
>>>>>
>>>>> On Wed, May 25, 2016 at 8:57 PM, Tomek Janiszewski <jani...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi
>>>>>>
>>>>>> Will the event be transmitted?
>>>>>> It will be great to enable Mesos Users Groups from Europe to watch
>>>>>> Keynotes live.
>>>>>>
>>>>>> Best
>>>>>> Tomek
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Haosdent Huang
>>>>>
>>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Haosdent Huang
>>>
>>

Re: [MesosCon] Live streaming?

[Tomek Janiszewski]

@haosdent Are you sure? I remember that everything was recorded but not
live - according to
https://twitter.com/mesoscon/status/495259388089614336 there
was no official stream.

śr., 25.05.2016 o 15:03 użytkownik haosdent <haosd...@gmail.com> napisał:

> I remember last year have live streaming. :-)
>
> On Wed, May 25, 2016 at 8:57 PM, Tomek Janiszewski <jani...@gmail.com>
> wrote:
>
>> Hi
>>
>> Will the event be transmitted?
>> It will be great to enable Mesos Users Groups from Europe to watch
>> Keynotes live.
>>
>> Best
>> Tomek
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>

[MesosCon] Live streaming?

[Tomek Janiszewski]

Hi

Will the event be transmitted?
It will be great to enable Mesos Users Groups from Europe to watch Keynotes
live.

Best
Tomek

Re: Running Mesos agent on ARM (Raspberry Pi)?

[Tomek Janiszewski]

Cool. Did you hit any trubles with that setup?

pt., 13.05.2016, 03:13 użytkownik Sharma Podila 
napisał:

> We have Mesos agents running on Pi3's taking tasks from master running on
> a Linux laptop.
>
> https://twitter.com/aspyker/status/730924571440779264
>
> More info to follow.
>
> Thanks for all the pointers.
>
>
> On Fri, Apr 29, 2016 at 1:09 PM, Sharma Podila 
> wrote:
>
>> Fyi- Things are progressing, we have a build on Pi. The agent was able to
>> come up and register with a master running on a regular Linux server.
>>
>> https://twitter.com/aspyker/status/725923864031559681
>>
>> The master has problem running with this build on the Pi, but, that isn't
>> a goal for us. We are running Mesos 0.24.1 for now. We'll document our
>> build steps, etc. here soon.
>>
>>
>>
>> On Mon, Apr 25, 2016 at 10:21 AM, Sharma Podila 
>> wrote:
>>
>>> This is for an internal hackday project, not for a production setup.
>>>
>>>
>>> On Mon, Apr 25, 2016 at 1:05 AM, Aaron Carey  wrote:
>>>
 Out of curiosity... is this for fun or production workloads? I'd be
 curious to hear about raspis being used in production!

 --

 Aaron Carey
 Production Engineer - Cloud Pipeline
 Industrial Light & Magic
 London
 020 3751 9150

 --
 *From:* Sharma Podila [spod...@netflix.com]
 *Sent:* 22 April 2016 17:53
 *To:* user@mesos.apache.org; dev
 *Subject:* Running Mesos agent on ARM (Raspberry Pi)?

 We are working on a hack to run Mesos agents on Raspberry Pi and are
 wondering if anyone here has done that before. From the Google search
 results we looked at so far, it seems like it has been compiled, but we
 haven't seen an indication that anyone has run it and launched tasks on
 them. And does it sound right that it might take 4 hours or so to compile?

 We are looking to run just the agents. The master will be on a regular
 Ubuntu laptop or a server.

 Appreciate any pointers.



>>>
>>
>

Re: Configuring failover timeouts?

[Tomek Janiszewski]

Hi

What is configuration of health-check. If it's configured to have 5 min
interval and allow 3 consequential fails you end up with 15 min delay
between marking task unhealthy and spawning new one.

Best
Tomek

wt., 10.05.2016 o 18:54 użytkownik Ruturaj Dhekane 
napisał:

> Hi all,
>
> I have a Mesos+Marathon setup deployed on 3 master 6 slaves mode. I have
> deployed a MySQL docker container and another front end container.
>
> I have health check enabled on the MySQL container.
>
> When i turn off the slave that contains the MySQL, DCOS detects bad
> health, marks the slave as unhealthy. but it takes about 15 minutes before
> marathon reschedules it on to a new host.
>
> How to reduce this time to say 2 minutes? Why doesn't Marathon schedule it
> the moment the health has gone bad? Any params I can change to enable this?
>
> I checked the documentation and asked on IRC - not much help. Please point
> me to a documentation if I have missed something.
>
> Thank you,
> Ruturaj
>

Re: Running Mesos agent on ARM (Raspberry Pi)?

[Tomek Janiszewski]

Current master version should build on Pi3 but there still could be a
problem with leveldb.

wt., 3.05.2016 o 16:40 użytkownik Andreas Fritzler <
andreas.fritz...@gmail.com> napisał:

> Did anybody try to build and run Mesos on a Raspberry Pi3? Will that work
> out of the box (due to the 64bit ARM)?
>
> On Sat, Apr 30, 2016 at 5:54 AM, haosdent  wrote:
>
>> >The master has problem running with this build on the Pi
>> You need launch master with `--registry=in_memory`, replicated_log with
>> leveldb has problem in Mesos master.
>>
>> On Sat, Apr 30, 2016 at 4:09 AM, Sharma Podila 
>> wrote:
>>
>> > Fyi- Things are progressing, we have a build on Pi. The agent was able
>> to
>> > come up and register with a master running on a regular Linux server.
>> >
>> > https://twitter.com/aspyker/status/725923864031559681
>> >
>> > The master has problem running with this build on the Pi, but, that
>> isn't
>> > a goal for us. We are running Mesos 0.24.1 for now. We'll document our
>> > build steps, etc. here soon.
>> >
>> >
>> >
>> > On Mon, Apr 25, 2016 at 10:21 AM, Sharma Podila 
>> > wrote:
>> >
>> >> This is for an internal hackday project, not for a production setup.
>> >>
>> >>
>> >> On Mon, Apr 25, 2016 at 1:05 AM, Aaron Carey  wrote:
>> >>
>> >>> Out of curiosity... is this for fun or production workloads? I'd be
>> >>> curious to hear about raspis being used in production!
>> >>>
>> >>> --
>> >>>
>> >>> Aaron Carey
>> >>> Production Engineer - Cloud Pipeline
>> >>> Industrial Light & Magic
>> >>> London
>> >>> 020 3751 9150
>> >>>
>> >>> --
>> >>> *From:* Sharma Podila [spod...@netflix.com]
>> >>> *Sent:* 22 April 2016 17:53
>> >>> *To:* user@mesos.apache.org; dev
>> >>> *Subject:* Running Mesos agent on ARM (Raspberry Pi)?
>> >>>
>> >>> We are working on a hack to run Mesos agents on Raspberry Pi and are
>> >>> wondering if anyone here has done that before. From the Google search
>> >>> results we looked at so far, it seems like it has been compiled, but
>> we
>> >>> haven't seen an indication that anyone has run it and launched tasks
>> on
>> >>> them. And does it sound right that it might take 4 hours or so to
>> compile?
>> >>>
>> >>> We are looking to run just the agents. The master will be on a regular
>> >>> Ubuntu laptop or a server.
>> >>>
>> >>> Appreciate any pointers.
>> >>>
>> >>>
>> >>>
>> >>
>> >
>>
>>
>> --
>> Best Regards,
>> Haosdent Huang
>>
>
>

Re: Running Mesos agent on ARM (Raspberry Pi)?

[Tomek Janiszewski]

@haosdent Here you are https://reviews.apache.org/r/46610/ I hope I'll find
more time to hack on RPI next week.

niedz., 24.04.2016 o 12:04 użytkownik haosdent <haosd...@gmail.com> napisał:

> Tomek's Mesos on ARM seems out of date, and it is a bit painful to set up
> a Raspberry Pi development environment in x86 machine.
>
> So I create a docker image `haosdent/raspberry` to simple this and
> document how to patch, compile and running mesos on the Raspberry Pi in
> this [post](http://blog.haosdent.me/2016/04/24/mesos-on-arm/). Hope it is
> helpful for you if you are seeking to run Mesos on ARM.
>
> In additional, thanks to @zhiwei and @vinodkone's work recently. Bundle
> zookeeper package have already upgraded to 3.4.8 which could pass compile
> on ARM. The only change to make mesos pass compile on ARM is to patch
>  `pivot_root` in fs.cpp. @Tomek would you like to modify it according to my
> suggestions on your github and post it in review board
> https://reviews.apache.org/groups/mesos/ to further review? I think it is
> necessary if we want to make Mesos run on ARM perfectly.
>
> On Sat, Apr 23, 2016 at 9:42 AM, Sharma Podila <spod...@netflix.com>
> wrote:
>
>> Appreciate all the pointers so far. We'll certainly share what we end up
>> with in a few weeks.
>>
>>
>> On Fri, Apr 22, 2016 at 5:49 PM, tommy xiao <xia...@gmail.com> wrote:
>>
>>> the alternative way, use Docker on rpi to containerised the mesos master
>>> and slave, it also cool things.
>>>
>>> 2016-04-23 1:38 GMT+08:00 Dario Rexin <dario.re...@me.com>:
>>>
>>>> Hi Sharma,
>>>>
>>>> I played around with Mesos on RPi a while back and have been able to
>>>> compile and run it with 2 little patches.
>>>>
>>>> 1) Depending on the ZK version, it may be necessary to patch a function
>>>> that uses inline ASM to use the resp. compiler intrinsics (I don’t remember
>>>> where exactly in zk it was, but the compile error should tell you)
>>>>
>>>> 2) There is string formatting code somewhere that compiles, but is not
>>>> architecture independent, i.e. behaves different on 32 and 64 bit. IIRC the
>>>> fix was to change %lu to %llu or something close to that. The stack trace
>>>> when Mesos crashes should tell you. If you’re lucky enough to have an RPi3,
>>>> this may not be necessary.
>>>>
>>>> Also, if you compile on the RPi make sure to create a swap file of
>>>> >=512MB. The build process will use lots of memory. I have not been able to
>>>> compile on multiple cores, because the memory usage was just too high.
>>>>
>>>> I hope this helps.
>>>>
>>>> On Apr 22, 2016, at 10:23 AM, Tomek Janiszewski <jani...@gmail.com>
>>>> wrote:
>>>>
>>>> As @haosdent mentioned with Kevin we tried to run it on ARM. AFAIR
>>>> there was a problem only with master, agents runs smoothly (or pretend to).
>>>> To run it on RPi you need to compile it for ARM. Easy but long solution is
>>>> to compile it on rpi. Quick but a little bit harder  cross compile it on
>>>> "normal" machine and upload to device.
>>>>
>>>>
>>>> http://likemagicappears.com/projects/raspberry-pi-cluster/mesos-on-raspbian/
>>>>
>>>> pt., 22 kwi 2016, 19:02 użytkownik haosdent <haosd...@gmail.com>
>>>> napisał:
>>>>
>>>>> Tomek have a gsoc proposal to make Mesos build on ARM
>>>>> https://docs.google.com/document/d/1zbms2jQfExuIm6g-adqaXjFpPif6OsqJ84KAgMrOjHQ/edit
>>>>> I think you could take a look at this code in github
>>>>> https://github.com/lyda/mesos-on-arm
>>>>>
>>>>> On Sat, Apr 23, 2016 at 12:53 AM, Sharma Podila <spod...@netflix.com>
>>>>> wrote:
>>>>>
>>>>>> We are working on a hack to run Mesos agents on Raspberry Pi and are
>>>>>> wondering if anyone here has done that before. From the Google search
>>>>>> results we looked at so far, it seems like it has been compiled, but we
>>>>>> haven't seen an indication that anyone has run it and launched tasks on
>>>>>> them. And does it sound right that it might take 4 hours or so to 
>>>>>> compile?
>>>>>>
>>>>>> We are looking to run just the agents. The master will be on a
>>>>>> regular Ubuntu laptop or a server.
>>>>>>
>>>>>> Appreciate any pointers.
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Haosdent Huang
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Deshi Xiao
>>> Twitter: xds2000
>>> E-mail: xiaods(AT)gmail.com
>>>
>>
>>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Re: Running Mesos agent on ARM (Raspberry Pi)?

[Tomek Janiszewski]

As @haosdent mentioned with Kevin we tried to run it on ARM. AFAIR there
was a problem only with master, agents runs smoothly (or pretend to). To
run it on RPi you need to compile it for ARM. Easy but long solution is to
compile it on rpi. Quick but a little bit harder  cross compile it on
"normal" machine and upload to device.

http://likemagicappears.com/projects/raspberry-pi-cluster/mesos-on-raspbian/

pt., 22 kwi 2016, 19:02 użytkownik haosdent  napisał:

> Tomek have a gsoc proposal to make Mesos build on ARM
> https://docs.google.com/document/d/1zbms2jQfExuIm6g-adqaXjFpPif6OsqJ84KAgMrOjHQ/edit
> I think you could take a look at this code in github
> https://github.com/lyda/mesos-on-arm
>
> On Sat, Apr 23, 2016 at 12:53 AM, Sharma Podila 
> wrote:
>
>> We are working on a hack to run Mesos agents on Raspberry Pi and are
>> wondering if anyone here has done that before. From the Google search
>> results we looked at so far, it seems like it has been compiled, but we
>> haven't seen an indication that anyone has run it and launched tasks on
>> them. And does it sound right that it might take 4 hours or so to compile?
>>
>> We are looking to run just the agents. The master will be on a regular
>> Ubuntu laptop or a server.
>>
>> Appreciate any pointers.
>>
>>
>>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Re: Vote on #MesosCon proposals, deadline Friday March 25

[Tomek Janiszewski]

@David Do you have results?

pon., 21.03.2016 o 14:39 użytkownik David Greenberg 
napisał:

> No, sorry--we'll collect the votes on Friday.
>
> Thanks,
> David
>
> On Sun, Mar 20, 2016 at 9:01 PM Darren Haas  wrote:
>
>> Hi David,
>>
>> We could always start the ranking using shuf. :) Is it possible to show
>> the current votes during the ranking?
>>
>> Thanks,
>> Darren
>>
>>
>>
>>
>> Sent from my iPhone
>> On Mar 19, 2016, at 4:45 PM, David Greenberg 
>> wrote:
>>
>> Hi Jay,
>>
>> Thanks for your feedback! The reason we're asking for you to rank the
>> topics is that this will allow us to better understand everyone's relative
>> preferences--next, we'll use standard voting algorithms to determine the
>> schedule, to ensure most people get as many talks they want as possible. We
>> hope you enjoy the program we come up with :)
>>
>> Thanks,
>> David
>>
>> On Sat, Mar 19, 2016 at 12:39 AM Jay JN Guo 
>> wrote:
>>
>>> Hi,
>>>
>>> Thank you for this good work and I'm already looking forward to this
>>> MesosCon.
>>>
>>> Although one minor suggestion here, Accept/Reject on a scale of 10 is a
>>> bit intimidating. Personally, I only have three feeling toward a topic:
>>> will go/maybe/not interested, whereas quantifying these feeling into a
>>> scale of 10 for 154 topics is just too much. Maybe we could simplify the
>>> form in the future. We could take OpenStack summit voting form as an
>>> example.
>>>
>>> Cheers,
>>> /J
>>>
>>> - Original message -
>>> From: Kiersten Gaffney 
>>> To: d...@mesos.apache.org, user@mesos.apache.org
>>> Cc: David Greenberg , Dave Lester <
>>> d...@davelester.org>, Kiersten Gaffney 
>>> Subject: Vote on #MesosCon proposals, deadline Friday March 25
>>> Date: Sat, Mar 19, 2016 8:11 AM
>>>
>>>
>>> Please take a few minutes the next few days and review what members of
>>> the
>>> community have submitted!
>>>
>>> Voting forms close Friday, March 25, 2016, 11:55 PST
>>>
>>> A total of 154 proposals were submitted in time for #MesosCon review, up
>>> significantly from 63 submitted for last year’s conference. Similar to
>>> last
>>> year, the MesosCon program committee is opening these proposals up for
>>> community review/feedback to better-inform our decisions about what
>>> should
>>> be included in the program.
>>>
>>> In order to make it easier to review a subset of the proposals, we’ve
>>> segmented them based upon two loose themes: Developer and Users.
>>>
>>> Developers: http://bit.ly/1RpZPvj
>>>
>>> Talks on how frameworks can be used, developed, and integrate with Mesos.
>>>
>>> Users: http://bit.ly/1Mspaxp
>>>
>>> A combination of talks that are use cases (how company x uses Mesos), and
>>> operations-focused (how we deploy x, use Docker, etc).
>>>
>>> The forms above also include an opportunity to indicate which sessions
>>> you
>>> didn't see proposed but would like to attend.
>>>
>>> Thanks in advance for your participation!
>>>
>>> Kiersten, Dave, and David (Program Committee)
>>>
>>>

Re: Vote TODAY MesosCon voting closes today, Friday March 25

[Tomek Janiszewski]

Totally agree with Shuan and I think scale of 3 will be enough (-1,0,+1).
Another thing, presenting long list of proposals and expecting user go thru
all of that and click submit button at the end is far too optimistic.

sob., 26 mar 2016, 04:33 użytkownik Shuai Lin 
napisał:

> Not sure whether it's personal feeling or not, but in the voting page I
> see on a scale of 1 to 10, 1 for "accept" and 10 for "reject" is quite
> counter-intuitive.
>
> On Sat, Mar 26, 2016 at 1:32 AM, Kiersten Gaffney 
> wrote:
>
>> If you haven't already, please take a few minutes the next few days and
>> review what members of the community have submitted!
>>
>> Voting forms close TODAY, Friday, March 25, 2016, 11:55 PST
>>
>> A total of 154 proposals were submitted in time for #MesosCon review, up
>> significantly from 63 submitted for last year’s conference. Similar to last
>> year, the MesosCon program committee is opening these proposals up for
>> community review/feedback to better-inform our decisions about what should
>> be included in the program.
>>
>> In order to make it easier to review a subset of the proposals, we’ve
>> segmented them based upon two loose themes: Developer and Users.
>>
>> Developers: http://bit.ly/1RpZPvj
>>
>> Talks on how frameworks can be used, developed, and integrate with Mesos.
>>
>> Users: http://bit.ly/1Mspaxp
>>
>> A combination of talks that are use cases (how company x uses Mesos),
>> and operations-focused (how we deploy x, use Docker, etc).
>>
>> The forms above also include an opportunity to indicate which sessions
>> you didn't see proposed but would like to attend.
>>
>> Thanks in advance for your participation!
>>
>> Kiersten, Dave, and David (Program Committee)
>>
>
>

Warsaw Meetup on Mar 10th

[Tomek Janiszewski]

Hi

For European folks we have Warsaw (Poland)  Meetup. More info
http://meetu.ps/e/B9x9C/dGwDH/d

See you there
Tomek


Warsaw_MUG.ics
Description: Binary data

Re: Using Virtual Hosts

[Tomek Janiszewski]

Hi Alfredo
Have you seen https://github.com/mesosphere/marathon-lb or
https://github.com/martensson/nixy I'm not sure if they will work
straightforward with Chronos but you can pool Mesos for it's tasks (like
https://github.com/CiscoCloud/mesos-consul does).

pt., 12.02.2016 o 00:45 użytkownik Alfredo Carneiro <
alfr...@simbioseventures.com> napisał:

> But how can I assign a domain to a task using haproxy?
> On Feb 11, 2016 8:29 PM, "Shuai Lin"  wrote:
>
>> Since you already have haproxy running, why not use it as a reverse
>> proxy?
>>
>> On Fri, Feb 12, 2016 at 3:31 AM, Alfredo Carneiro <
>> alfr...@simbioseventures.com> wrote:
>>
>>> Hi guys,
>>>
>>> I have been searching for the past few weeks about Mesos and VHosts,
>>> saddly, I have not found anything useful.
>>>
>>> I have a mesos cluster running some webapps. So, I have assigned specifc
>>> ports to these apps, so I access this apps using
>>> *http://:*. How could I use Virtual Hosts to
>>> access these apps? *http://myapp.com *?
>>>
>>> 1x Mesos Master with HAProxy and Chronos
>>> 9x Mesos Slave with Docker
>>>
>>> Thanks,
>>>
>>> --
>>> Alfredo Miranda
>>>
>>
>>

Re: Monitoring

[Tomek Janiszewski]

Hi

In our setup we are using Diamond with default system collectors and one
custom collector (based on
https://github.com/python-diamond/Diamond/pull/106 but with some
improvements). Some other solutions were presented at MesosCon:
https://www.youtube.com/watch?v=yLkc17HFEb8
https://www.youtube.com/watch?v=zlgAT_xFNzU

Tomek

wt., 19.01.2016 o 21:04 użytkownik Michał Łowicki 
napisał:

> Hi,
>
> I've read Mesos Observability Metrics
>  which gives
> nice overview of cluster's health. What about other parameters like I/O
> usage (disk, network), number of processes etc. Maybe there are some tools
> or their configurations dedicated for Mesos? (we're mostly using Diamond
> and StatsD which reports to Graphite). How to launch such tools -
> separately from Mesos or launch as a part of long-running tasks?
>
> --
> BR,
> Michał Łowicki
>