Re: [VOTE] Move Apache Mesos to Attic

[Gastón Kleiman]

+1

I had a great time working with you all and with the community! Hope our
paths cross again in the future!

On Mon, Apr 5, 2021 at 10:58 AM Vinod Kone  wrote:

> Hi folks,
>
> Based on the recent conversations
> 
> on our mailing list, it seems to me that the majority consensus among the
> existing PMC is to move the project to the attic
>  and let the interested community members
> collaborate on a fork in Github.
>
> I would like to call a vote to dissolve the PMC and move the project to
> the attic.
>
> Please reply to this thread with your vote. Only binding votes from
> PMC/committers count towards the final tally but everyone in the community
> is encouraged to vote. See process here
> .
>
> Thanks,
>

Re: [VOTE] Move Apache Mesos to Attic

[Gastón Kleiman]

+1

I had a great time working with you all and with the community! Hope our
paths cross again in the future!

On Mon, Apr 5, 2021 at 10:58 AM Vinod Kone  wrote:

> Hi folks,
>
> Based on the recent conversations
> 
> on our mailing list, it seems to me that the majority consensus among the
> existing PMC is to move the project to the attic
>  and let the interested community members
> collaborate on a fork in Github.
>
> I would like to call a vote to dissolve the PMC and move the project to
> the attic.
>
> Please reply to this thread with your vote. Only binding votes from
> PMC/committers count towards the final tally but everyone in the community
> is encouraged to vote. See process here
> .
>
> Thanks,
>

[RESULT][VOTE] Release Apache Mesos 1.7.2 (rc1)

[Gastón Kleiman]

Hi all,

The vote for Mesos 1.7.2 (rc1) has passed with the following votes.

+1 (Binding)
--
*** Vinod Kone
*** Greg Mann
*** Meng Zhu
*** Gilbert Song

There were no 0 or -1 votes.

Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/1.7.2

It is recommended to use a mirror to download the release:
http://www.apache.org/dyn/closer.cgi

The CHANGELOG for the release is available at:
https://gitbox.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.7.2

The mesos-1.7.2.jar has been released to:
https://repository.apache.org

The website (http://mesos.apache.org) will be updated shortly to reflect
this release.

Thanks,
Gastón & Chun-Hung

Re: [VOTE] Release Apache Mesos 1.4.3 (rc2)

[Gastón Kleiman]

+1

Ran it through Mesosphere's internal CI. Only 7 test failures were
observed, all known flakes.

On Fri, Feb 15, 2019 at 11:49 AM Vinod Kone  wrote:

> +1 (binding)
>
> Tested on ASF CI. Red builds are known flaky tests or unrelated infra
> issues.
>
>
> *Revision*: 1fee9b5365bf2424e4768dc1d5209c6c78dfece6
>
>- refs/tags/1.4.3-rc2
>
> Configuration Matrix gcc clang
> centos:7 --verbose --disable-libtool-wrappers
> --disable-parallel-test-execution --enable-libevent --enable-ssl autotools
> [image: Failed]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/64/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--disable-libtool-wrappers%20--disable-parallel-test-execution%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/
> >
> [image: Not run]
> cmake
> [image: Failed]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/64/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--verbose%20--disable-libtool-wrappers%20--disable-parallel-test-execution%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/
> >
> [image: Not run]
> --verbose --disable-libtool-wrappers --disable-parallel-test-execution
> autotools
> [image: Failed]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/64/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--disable-libtool-wrappers%20--disable-parallel-test-execution,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/
> >
> [image: Not run]
> cmake
> [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/64/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--verbose%20--disable-libtool-wrappers%20--disable-parallel-test-execution,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/
> >
> [image: Not run]
> ubuntu:16.04 --verbose --disable-libtool-wrappers
> --disable-parallel-test-execution --enable-libevent --enable-ssl autotools
> [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/64/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--disable-libtool-wrappers%20--disable-parallel-test-execution%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A16.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/
> >
> [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/64/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose%20--disable-libtool-wrappers%20--disable-parallel-test-execution%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A16.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/
> >
> cmake
> [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/64/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--verbose%20--disable-libtool-wrappers%20--disable-parallel-test-execution%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A16.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/
> >
> [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/64/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=--verbose%20--disable-libtool-wrappers%20--disable-parallel-test-execution%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A16.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/
> >
> --verbose --disable-libtool-wrappers --disable-parallel-test-execution
> autotools
> [image: Failed]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/64/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--disable-libtool-wrappers%20--disable-parallel-test-execution,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A16.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/
> >
> [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/64/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose%20--disable-libtool-wrappers%20--disable-parallel-test-execution,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A16.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/
> >
> cmake
> [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/64/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--verbose%20--disable-libtool-wrappers%20--disable-parallel-test-execution,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A16.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/
> >
> [image: Failed]
> <
> 

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

[Gastón Kleiman]

+1 (binding) — ran the build through Mesosphere's internal CI and only two
known flaky tests failed.

On Tue, Feb 19, 2019 at 11:56 AM Greg Mann  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.6.2.
>
>
> 1.6.2 includes a number of bug fixes since 1.6.1; the CHANGELOG for the
> release is available at:
>
> https://gitbox.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.6.2-rc1
>
> 
>
> The candidate for Mesos 1.6.2 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.6.2-rc1/mesos-1.6.2.tar.gz
>
> The tag to be voted on is 1.6.2-rc1:
> https://gitbox.apache.org/repos/asf?p=mesos.git;a=commit;h=1.6.2-rc1
>
> The SHA512 checksum of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/1.6.2-rc1/mesos-1.6.2.tar.gz.sha512
>
> The signature of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/1.6.2-rc1/mesos-1.6.2.tar.gz.asc
>
> The PGP key used to sign the release is here:
> https://dist.apache.org/repos/dist/release/mesos/KEYS
>
> The JAR is in a staging repository here:
> https://repository.apache.org/content/repositories/orgapachemesos-1246
>
> Please vote on releasing this package as Apache Mesos 1.6.2!
>
> The vote is open until Fri Feb 22 11:54 PST 2019, and passes if a majority
> of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 1.6.2
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Greg
>

[VOTE] Release Apache Mesos 1.7.2 (rc1)

[Gastón Kleiman]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 1.7.2.


1.7.2 includes a number of bug fixes since 1.7.1; the CHANGELOG for the
release is available at:
https://gitbox.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.7.2-rc1



The candidate for Mesos 1.7.2 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/1.7.2-rc1/mesos-1.7.2.tar.gz

The tag to be voted on is 1.7.2-rc1:
https://gitbox.apache.org/repos/asf?p=mesos.git;a=commit;h=1.7.2-rc1

The SHA512 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.7.2-rc1/mesos-1.7.2.tar.gz.sha512

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.7.2-rc1/mesos-1.7.2.tar.gz.asc

The PGP key used to sign the release is here:
https://dist.apache.org/repos/dist/release/mesos/KEYS

The JAR is in a staging repository here:
https://repository.apache.org/content/repositories/orgapachemesos-1249

Please vote on releasing this package as Apache Mesos 1.7.2!

The vote is open until Fri Feb 22 15:00:00 PST 2019, and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 1.7.2
[ ] -1 Do not release this package because ...

Thanks,

Gastón

Re: Welcome Benno Evers as committer and PMC member!

[Gastón Kleiman]

Very well deserved — welcome and congratulations, Benno!



On Wed, Jan 30, 2019 at 3:21 PM Alex R  wrote:

> Folks,
>
> Please welcome Benno Evers as an Apache committer and PMC member of the
> Apache Mesos!
>
> Benno has been active in the project for more than a year now and has made
> significant contributions, including:
>   * Agent reconfiguration, MESOS-1739
>   * Memory profiling, MESOS-7944
>   * "/state" performance improvements, MESOS-8345
>
> I have been working closely with Benno, paired up on, and shepherded some
> of his work. Benno has very strong technical knowledge in several areas and
> he is willing to share it with others and help his peers.
>
> Benno, thanks for all your contributions so far and looking forward to
> continuing to work with you on the project!
>
> Alex.
>

Re: Join us at MesosCon 2018 next week!

[Gastón Kleiman]

You can pick up your ticket at 30% off here <https://t.co/1Tfb4a6gSO> (source
tweet <https://twitter.com/mesosphere/status/1057692455456464897>).

On Thu, Nov 1, 2018 at 10:33 AM Vaibhav Khanduja 
wrote:

> Thanks for the email.
>
> Are there any promotional code available for enterprises?
>
> On Wed, Oct 31, 2018 at 5:06 PM Gastón Kleiman 
> wrote:
>
>> MesosCon 2018 is taking place next week! Join us and celebrate the 5th
>> anniversary of MesosCon November 5th-7th, in the The Village (969 Market
>> St, San Francisco).
>>
>> MesosCon North America is an annual conference organized by the Apache
>> Mesos community, bringing together users and developers to share and learn
>> about the Apache Mesos project, containers, DevOps, and automation.
>>
>> What to expect
>>
>> MesosCon will include tracks focused on case studies and architecture of
>> modern, containerized applications, fast data tools like Spark, Cassandra,
>> and TensorFlow, and about Mesos itself. Attendees can expect engaging
>> keynotes, technical breakout sessions, and collaborative town hall
>> sessions
>> to include Mesos and the broader ecosystem. Attendees can expect to:
>>
>>
>>-
>>
>>Learn how to design and build their own custom frameworks
>>-
>>
>>Discover how easy it is to build, deploy, and scale your applications
>>-
>>
>>Dive deep into Mesos internals, storage, security, and networking
>>-
>>
>>Network with the community and share best practices and lessons learned
>>
>>
>> Check out the schedule and register at http://mesoscon2018.org.
>>
>> Cheers,
>>
>> The MesosCon 2018 organization team
>>
> --
> You received this message because you are subscribed to the Google Groups
> "marathon-framework" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to marathon-framework+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

Join us at MesosCon 2018 next week!

[Gastón Kleiman]

MesosCon 2018 is taking place next week! Join us and celebrate the 5th
anniversary of MesosCon November 5th-7th, in the The Village (969 Market
St, San Francisco).

MesosCon North America is an annual conference organized by the Apache
Mesos community, bringing together users and developers to share and learn
about the Apache Mesos project, containers, DevOps, and automation.

What to expect

MesosCon will include tracks focused on case studies and architecture of
modern, containerized applications, fast data tools like Spark, Cassandra,
and TensorFlow, and about Mesos itself. Attendees can expect engaging
keynotes, technical breakout sessions, and collaborative town hall sessions
to include Mesos and the broader ecosystem. Attendees can expect to:


   -

   Learn how to design and build their own custom frameworks
   -

   Discover how easy it is to build, deploy, and scale your applications
   -

   Dive deep into Mesos internals, storage, security, and networking
   -

   Network with the community and share best practices and lessons learned


Check out the schedule and register at http://mesoscon2018.org.

Cheers,

The MesosCon 2018 organization team

[VOTE] Release Apache Mesos 1.7.0 (rc3)

[Gastón Kleiman]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 1.7.0.


1.7.0 includes the following:

* Performance Improvements:
  * Master `/state` endpoint: ~130% throughput improvement through RapidJSON
  * Allocator: Improved allocator cycle significantly
  * Agent `/containers` endpoint: Fixed a performance issue
  * Agent container launch / destroy throughput is significantly improved
* Containerization:
  * **Experimental** Supported docker image tarball fetching from HDFS
  * Added new `cgroups/all` and `linux/devices` isolators
  * Added metrics for `network/cni` isolator and docker pull latency
* Windows:
  * Added support to libprocess for the Windows Thread Pool API
* Multi-Framework Workloads:
  * **Experimental** Added per-framework metrics to the master
  * A new weighted random sorter was added as an alternative to the DRF
sorter

The CHANGELOG for the release is available at:
https://gitbox.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.7.0-rc3


The candidate for Mesos 1.7.0 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/1.7.0-rc3/mesos-1.7.0.tar.gz

The tag to be voted on is 1.7.0-rc3:
https://gitbox.apache.org/repos/asf?p=mesos.git;a=commit;h=1.7.0-rc3

The SHA512 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.7.0-rc3/mesos-1.7.0.tar.gz.sha512

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.7.0-rc3/mesos-1.7.0.tar.gz.asc

The PGP key used to sign the release is here:
https://dist.apache.org/repos/dist/release/mesos/KEYS

The JAR is in a staging repository here:
https://repository.apache.org/content/repositories/orgapachemesos-1234

Please vote on releasing this package as Apache Mesos 1.7.0!

The vote is open until Fri Sep 14 11:06:30 PDT 2018 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 1.7.0
[ ] -1 Do not release this package because ...

Thanks,

Chun-Hung & Gastón

MesosCon 2018 CFP deadline extended

[Gastón Kleiman]

We are excited and want to thank you for the number of high quality
submissions that we have received so far this year!

In order to allow for more submissions, we have extended the CFP deadline
for MesosCon 2018 until Sept 4th 11:59 PM PDT. If you have not yet had a
chance to submit a proposal, you can still access the submission form here
.

Submit a talk for MesosCon and join us at MesosCon 2018!
https://mesoscon2018.org

-Gastón

MesosCon 2018 Call for Proposals

[Gastón Kleiman]

Greetings Friends and Community Members,

This year MesosCon will be held in New York between November 5th-7th,
bringing together users and developers to share and learn about the project
and its growing ecosystem.

The MesosCon Call for Proposals deadline is *Aug 27th*. The Apache Mesos
community would love to hear how you're using Mesos, Apache Aurora, Titus,
PaaSTA, Marathon, DC/OS, or how you have built software around these
projects. There are many ways to participate (e.g. 40 minute talks,
lightning talks, leading or participating in a panel, tutorials, or
sponsorship). You can find out more at the MesosCon CFP survey
.

Below are some ideas on what the community might like to hear:

   - User stories about how adopting Mesos has helped your organization
   (preferably with metrics)
   - How you operate your Mesos cluster
   - Advanced presentations about Mesos features and internals
   - What is new in the ecosystem? Have you created a new framework? What
   is new in your favorite framework?
   - What applications/services you run on your Mesos clusters
   - How you run machine learning and analytics workloads on Mesos
   - What challenges you've faced using Mesos
   - What advice you have for other users

Finally, MesosCon is a community run conference and your support is needed.
Sponsoring this event will provide a great opportunity for your
organization to further engage with the Mesos community. Email
spon...@mesoscon2018.org to learn more.

Best,

-Gastón

Re: Operations Working Group - First Meeting

[Gastón Kleiman]

Hi Abel,

I would love to learn more from people operating Mesos clusters of any
size. We can discuss what is working great, what is on the roadmap, and
what could be improved.

Some of us have been working on adding new per-framework metrics and extra
logging to the Mesos master - I think that an operator would find them
valuable to monitor/debug/troubleshoot a Mesos cluster, so I could also
talk a bit about that.

The agenda (
https://docs.google.com/document/d/1XjJfoksz70vbTvvT6FQ1t_J0SD1XIoipmYSvEHJfXt8/edit
) is still open and editable. I want to encourage everyone to add there the
topics that interest you!

Looking forward to meeting you all over Zoom next week,

-Gastón

On Tue, Jul 17, 2018 at 2:55 AM Abel Souza  wrote:

> Thank you for setting this up Gaston,
>
> Would you mind giving us a brief of what you have in mind for discussion?
>
> Thank you,
>
> Abel
>
> On 07/17/2018 10:52 AM, Matt Jarvis wrote:
>
> That's great news Gaston ! Let me know if you need any help from the
> Community team.
>
> Matt
>
> On Tue, 17 Jul 2018, 05:04 Gastón Kleiman,  wrote:
>
>> Hi all,
>>
>> Thank you for responding to my previous emails - I think that we have
>> quorum for a new working group!
>>
>> Many of you who have expressed interest seem to be in Europe, so I tried
>> schedule the first meeting at a time that I hope will be friendly for
>> people in both GMT+1 and GMT-8:
>>
>> *Date:* Wednesday July 25th from 9:00-10:00 AM PDT
>> *Agenda:*
>> https://docs.google.com/document/d/1XjJfoksz70vbTvvT6FQ1t_J0SD1XIoipmYSvEHJfXt8/
>> *Zoom URL:* https://zoom.us/j/310132146
>> <https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F310132146=D=1532231796594000=AFQjCNES74X29V0xlXjWGttfAVW0knbQlA>
>>
>> You can also find the event in the Mesos Community Calendar.
>>
>> Feel free to add more topics to the agenda.
>>
>> Looking forward to meeting you all next week,
>>
>> -Gastón
>>
>
>

Re: [VOTE] Release Apache Mesos 1.6.1 (rc2)

[Gastón Kleiman]

+1 (binding)

Tested on our internal CI. All green!
Tested on CentOS 7 and the following tests failed:

[  FAILED  ] DockerContainerizerTest.ROOT_DOCKER_Launch_Executor
[  FAILED  ] CgroupsIsolatorTest.ROOT_CGROUPS_CFS_EnableCfs
[  FAILED  ] CgroupsAnyHierarchyWithCpuMemoryTest.ROOT_CGROUPS_Listen
[  FAILED  ]
NvidiaGpuTest.ROOT_INTERNET_CURL_CGROUPS_NVIDIA_GPU_NvidiaDockerImage
[  FAILED  ]
bool/UserContainerLoggerTest.ROOT_LOGROTATE_RotateWithSwitchUserTrueOrFalse/0,
where GetParam() = true

They are all known to be flaky.

On Wed, Jul 11, 2018 at 6:15 PM Greg Mann  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.6.1.
>
>
> 1.6.1 includes the following:
>
> 
> *Announce major features here*
> *Announce major bug fixes here*
>
> The CHANGELOG for the release is available at:
>
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.6.1-rc2
>
> 
>
> The candidate for Mesos 1.6.1 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.6.1-rc2/mesos-1.6.1.tar.gz
>
> The tag to be voted on is 1.6.1-rc2:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.6.1-rc2
>
> The SHA512 checksum of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/1.6.1-rc2/mesos-1.6.1.tar.gz.sha512
>
> The signature of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/1.6.1-rc2/mesos-1.6.1.tar.gz.asc
>
> The PGP key used to sign the release is here:
> https://dist.apache.org/repos/dist/release/mesos/KEYS
>
> The JAR is in a staging repository here:
> https://repository.apache.org/content/repositories/orgapachemesos-1230
>
> Please vote on releasing this package as Apache Mesos 1.6.1!
>
> The vote is open until Mon Jul 16 18:15:00 PDT 2018 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 1.6.1
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Greg
>

Re: [VOTE] Move the project repos to gitbox

[Gastón Kleiman]

On Tue, Jul 17, 2018 at 7:59 AM Vinod Kone  wrote:

> Hi,
>
> As discussed in another thread and in the committers sync, there seem to be
> heavy interest in moving our project repos ("mesos", "mesos-site") from the
> "git-wip" git server to the new "gitbox" server to better avail GitHub
> integrations.
>
> Please vote +1, 0, -1 regarding the move to gitbox. The vote will close in
> 3 business days.
>

+1

Re: 1.7 release manager?

[Gastón Kleiman]

I haven't been waiting for this, but I'd like to volunteer too. I've never
been the release manager before, so I could help with some of the
pre-release JIRA wrangling and drafting the announcements.

-Gastón

On Tue, Jul 17, 2018 at 2:26 PM Vinod Kone  wrote:

> +dev
>
> -- Vinod
>
>
> On Tue, Jul 17, 2018 at 4:20 PM Chun-Hung Hsiao 
> wrote:
>
> > I could volunteer unless someone has been waiting for this :)
> >
> > On Tue, Jul 17, 2018 at 2:09 PM Greg Mann  wrote:
> >
> > > Hey folks!
> > > The question just came up here in the office: who is managing the 1.7.0
> > > release? 1.6.0 came out on May 11, so according to our quarterly
> release
> > > policy, we should aim for 1.7 to come out some time around mid-August.
> > >
> > > AFAIK, nobody has volunteered yet? I thought I'd start a thread to see
> if
> > > anybody is interested - any volunteers?
> > >
> > > Cheers,
> > > Greg
> > >
> >
>

Operations Working Group - First Meeting

[Gastón Kleiman]

Hi all,

Thank you for responding to my previous emails - I think that we have
quorum for a new working group!

Many of you who have expressed interest seem to be in Europe, so I tried
schedule the first meeting at a time that I hope will be friendly for
people in both GMT+1 and GMT-8:

*Date:* Wednesday July 25th from 9:00-10:00 AM PDT
*Agenda:*
https://docs.google.com/document/d/1XjJfoksz70vbTvvT6FQ1t_J0SD1XIoipmYSvEHJfXt8/
*Zoom URL:* https://zoom.us/j/310132146


You can also find the event in the Mesos Community Calendar.

Feel free to add more topics to the agenda.

Looking forward to meeting you all next week,

-Gastón

Re: Getting write access to our GitHub repo

[Gastón Kleiman]

On Wed, Jun 20, 2018 at 7:59 PM Vinod Kone  wrote:

> Hi folks,
>
> Looks like ASF now supports  giving write
> access to committers for their GitHub mirrors, which means we can merge PRs
> directly on GitHub!
>

+1. Not only does it allow to merge PRs directly on GitHub, but it also
allows committers to close stale PRs!

-Gastón

Scheduler library API change: method to consume Request/Response API calls

[Gastón Kleiman]

Hello everyone,


As you all probably know by now, Greg and I are working on enabling operation
feedback  for frameworks.

I implemented a new ReconcileOperations scheduler API call
, which will allow frameworks to get
the latest operation status sent to the framework, and to find out if the
agent (and external resource provider in the future) performing an
operation is unreachable, marked gone, etc.

This is the first scheduler API call that follows the “Request/Response”
pattern, i.e., the master will synchronously respond with a
mesos::v1::scheduler::Response protobuf message instead of via events. This
allows a scheduler to unambiguously associate status updates with a
particular reconciliation call, which is not possible with the Call/Event
pattern.

Our C++ Scheduler API client implements a void send()

method that doesn’t return the response from the master. I’m adding a new
method that will make it possible for users of the library to get that
response.

This method can be implemented in many ways, so I’d like to get your
opinion.

Note: this method will initially be used only by tests, but we might want
to use it if we update our Java bindings to support the “Request/Response”
pattern.

Option #1

process::Future> call(const Call& callMessage)

Where APIResult is a new protobuf message in the mesos.v1.scheduler package
with the following definition:

message APIResult {

 message Status {

   required uint32 status = 1; // HTTP status code

   optional string error = 2; // Body of the HTTP response

 }

 required Status status = 1;

 // The deserialized `v1.scheduler.Response` message.

 //

 // Note: this field is optional, because the master's response to most API

 // calls has a `202 Accepted` status code and an empty body.

 optional Response response = 2;

}

Advantages

   -

   It is possible to know whether the server answered with 200 or with 202.
   -

   It is easy to know if the server’s response included a
   mesos.v1.scheduler.Response


Option #2

process::Future> call(const Call& callMessage)

Where APIResult is a new protobuf message in the mesos.v1.scheduler package
with the following definition:

message APIResult {

 message Error {

   required uint32 status = 1; // HTTP status code

   optional string message = 2; // Body of the HTTP response

 }

 optional Error error = 1;

 optional Response response = 2; // mesos.v1.scheduler.Response

}

Note: if the server responds with “202 Accepted” and an empty body, then
both fields will be empty

Please take a look and let me know what you think!

Thanks,

-Gastón

API Change: New operation states

[Gastón Kleiman]

Hello everyone,

Greg and I are working on enabling offer operation feedback for frameworks
[1]. I am adding a new `ReconcileOperations` scheduler API call, which will
allow frameworks to get the latest operation status sent to the framework,
and to find out if the agent (and external resource provider in the future)
performing an operation is unreachable, marked gone, etc.

I recently proposed the introduction of new operation states in a review
request [2]. They are similar to the task states that were added when
adding support for partition-aware frameworks.

If you are interested in using operation feedback in the future, please
take a look and let me know what you think.

-Gastón

[1] https://issues.apache.org/jira/browse/MESOS-8054
[2] https://reviews.apache.org/r/66462/

Re: Welcome Chun-Hung Hsiao as Mesos Committer and PMC Member

[Gastón Kleiman]

Congrats Chun! Very well deserved!

Re: API working group

[Gastón Kleiman]

On Tue, Jan 30, 2018 at 10:42 AM, Vinod Kone  wrote:

> [...]
> 1) Would you be interested in participating in the API WG?
>

I'd be interested!

-Gastón

Offer Operation Feedback

[Gastón Kleiman]

Hello all!

We've been working on a design for adding support for sending offer
operation status updates to schedulers. You can find the design doc here

.

TL;DR: Mesos currently provides schedulers with feedback when a LAUNCH
operation succeeds or fails via task status updates. It does not, however,
provide explicit feedback for other offer operations such as RESERVE,
UNRESERVE, CREATE, and DESTROY. The plan is to provide feedback for these
operations in a similar way.

Comments on the design doc would be greatly appreciated!

Cheers,

-Gastón

Re: Slides from the previous community meeting (health checks)

[Gastón Kleiman]

The ASF mail servers seem to strip attachments - they deck is available
here: https://docs.google.com/presentation/d/1AUdNIyZ4vAu8vRuFRC7l-
Y9tB3fOXBMiYbICXpGjOXQ

-Gastón

On Fri, Jun 2, 2017 at 1:42 PM, Gastón Kleiman <gas...@mesosphere.io> wrote:

> Hi all,
>
> Please find attached the deck about health checks that I presented at the
> last Mesos Community Meeting.
>
> Cheers,
>
> Gastón
>

Slides from the previous community meeting (health checks)

[Gastón Kleiman]

Hi all,

Please find attached the deck about health checks that I presented at the
last Mesos Community Meeting.

Cheers,

Gastón

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

[Gastón Kleiman]

On Tue, May 30, 2017 at 3:43 PM, Neil Conway  wrote:

> On Tue, May 30, 2017 at 2:36 PM, Vinod Kone  wrote:
> > Ran on ASF CI.
> >
> > Found following issues.
> >
> > Failed test: CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled
> >  Release/36/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=centos:7,label_exp=(docker%7C%7CHadoop)
> &&(!ubuntu-us1)&&(!ubuntu-eu2)/console>
>
> Attached is the test log for this failure. From a quick look, seems as
> though the agent starts to launch the task, including forking the
> child process, but no subsequent task status updates or error messages
> are observed. Gaston, have you seen this before?
>
> I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.
>

Nope, I haven't seen this before.

It looks like the executor wasn't launched or something went wrong at a
very early stage of the executor's launch.

This is what the logs from a successful run look like:

I0530 20:19:52.679759 11282 launcher.cpp:140] Forked child with pid '11304'
>> for container '703bded9-43de-4950-986f-0eaec7bbe664'
>
> I0530 20:19:52.692080 11268 fetcher.cpp:324] Starting to fetch URIs for
>> container: 703bded9-43de-4950-986f-0eaec7bbe664, directory:
>> /tmp/CommandExecutorCheckTest_CommandCheckDeliveredAndReconciled_fqE44y/slaves/7c74b451-3e64-4c95-8570-ad3b5b60962b-S0/frameworks/7c74b451-3e64-4c95-8570-ad3b5b60962b-/executors/55b387b7-c1f1-47d5-9f19-2d676cd4ef2e/runs/703bded9-43de-4950-986f-0eaec7bbe664
>
> I0530 20:19:53.517201 11268 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-
>
> I0530 20:19:53.517283 11268 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:53.517318 11268 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:53.517367 11268 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 654478ns
>
> I0530 20:19:54.518506 11277 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-
>
> I0530 20:19:54.518584 11277 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:54.518616 11277 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:54.518662 11277 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 568919ns
>
> I0530 20:19:55.520282 11276 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-
>
> I0530 20:19:55.520364 11276 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:55.520409 11276 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:55.520463 11276 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 621097ns
>
> I0530 20:19:56.521884 11271 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-
>
> I0530 20:19:56.521966 11271 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:56.522001 11271 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:56.522047 11271 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 597601ns
>
> I0530 20:19:57.523320 11267 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-
>
> I0530 20:19:57.523398 11267 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:57.523432 11267 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:57.523478 11267 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 573802ns
>
> I0530 20:19:57.641808 11358 exec.cpp:162] Version: 1.4.0
>
> I0530 20:19:57.648437 11268 slave.cpp:3809] Got registration for executor
>> '55b387b7-c1f1-47d5-9f19-2d676cd4ef2e' of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b- from executor(1)@
>> 192.99.40.208:43797
>
> I0530 20:19:57.650589 11279 slave.cpp:2526] Sending queued task
>> '55b387b7-c1f1-47d5-9f19-2d676cd4ef2e' to executor
>> '55b387b7-c1f1-47d5-9f19-2d676cd4ef2e' of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b- at executor(1)@
>> 192.99.40.208:43797
>
> I0530 20:19:57.650804 11356 exec.cpp:237] Executor registered on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0
>
> 

Re: Welcome Neil Conway as Mesos Committer and PMC member!

[Gastón Kleiman]

Congratulations!!! =)

On Mon, Jan 23, 2017 at 1:46 AM, Neil Conway  wrote:

> Thanks for the kind words, everyone! It's been a pleasure to be a part
> of the Mesos community, and I'm looking forward to continuing to
> contribute.
>
> Neil
>
> On Sun, Jan 22, 2017 at 2:16 PM, Benjamin Mahler 
> wrote:
> > Congrats and welcome!
> >
> > On Fri, Jan 20, 2017 at 11:03 PM, Vinod Kone 
> wrote:
> >
> >> Hi folks,
> >>
> >> Please welcome Neil Conway as the newest committer and PMC member of the
> >> Apache Mesos project.
> >>
> >> Neil has been an active contributor to Mesos for more than a year now.
> As
> >> part of his work, he has contributed some major features (Partition
> aware
> >> frameworks, floating point operations for resources). Neil also took the
> >> initiative to improve the documentation of our project and shepherded
> >> several improvements over time. Doing that even without being a
> committer,
> >> shows that he takes ownership of the project seriously.
> >>
> >> Here is his more formal checklist for your perusal.
> >>
> >> https://docs.google.com/document/d/137MYwxEw9QCZRH09CXfn1544
> >> p1LuMuoj9LxS-sk2_F4/edit
> >>
> >> Thanks,
> >> Vinod
> >>
>

Re: Welcome Haosdent Huang as Mesos Committer and PMC member!

[Gastón Kleiman]

Congratulations! Very well deserved =).

On Tue, Dec 20, 2016 at 11:17 AM, Aaron Carey  wrote:

> Congratulations! Very well deserved! Always so helpful :)
>
> Aaron Carey
> Production Engineer - Cloud Pipeline
> Industrial Light & Magic
> London
> 020 3751 9150
>
>
> On 20 December 2016 at 01:24, Jie Yu  wrote:
>
>> Congrats! Well deserved!!
>>
>> Always wondering why you have so much time!
>>
>> - Jie
>>
>> On Mon, Dec 19, 2016 at 5:19 PM, Jay Guo 
>> wrote:
>>
>>> Congratulations Haosdent!!!
>>>
>>> /J
>>>
>>> On Mon, Dec 19, 2016 at 4:40 PM, Chengwei Yang
>>>  wrote:
>>> > Congratulations! Well deserved.
>>> >
>>> > Haosdent helps me a lot!
>>> >
>>> > On Fri, Dec 16, 2016 at 01:59:19PM -0500, Vinod Kone wrote:
>>> >> Hi folks,
>>> >>
>>> >> Please join me in formally welcoming Haosdent Huang as Mesos
>>> Committer and
>>> >> PMC member.
>>> >>
>>> >> Haosdent has been an active contributor to the project for more than
>>> a year
>>> >> now. He has contributed a number of patches and features to the Mesos
>>> code
>>> >> base, most notably the unified cgroups isolator and health check
>>> >> improvements. The most impressive thing about him is that he always
>>> >> volunteers to help out people in the community, be it on slack/IRC or
>>> >> mailing lists. The fact that he does all this even though working on
>>> Mesos
>>> >> is not part of his day job is even more impressive.
>>> >>
>>> >> Here is his more formal checklist
>>> >> >> ZGLXG6CF9VP2IY_UU5_0/edit?ts=57e0029d>
>>> >> for your perusal.
>>> >>
>>> >> Thanks,
>>> >> Vinod
>>> >>
>>> >> P.S: Sorry for the delay in sending the welcome email.
>>> >
>>> > --
>>> > Thanks,
>>> > Chengwei
>>>
>>
>>
>

Re: Command healthcheck failed but status KILLED

[Gastón Kleiman]

On Mon, Dec 12, 2016 at 12:47 PM, Tomek Janiszewski 
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: [VOTE] Release Apache Mesos 1.1.0 (rc1)

[Gastón Kleiman]

+1 (non-binding), "make check' and also Marathon's integration tests pass
on OS X.

-Gastón

On Tue, Oct 18, 2016 at 10:01 PM, Till Toenshoff  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.1.0.
>
>
> 1.1.0 includes the following:
> 
> 
>   * [MESOS-2449] - **Experimental** support for launching a group of tasks
> via a new `LAUNCH_GROUP` Offer operation. Mesos will guarantee that
> either
> all tasks or none of the tasks in the group are delivered to the
> executor.
> Executors receive the task group via a new `LAUNCH_GROUP` event.
>
>   * [MESOS-2533] - **Experimental** support for HTTP and HTTPS health
> checks.
> Executors may now use the updated `HealthCheck` protobuf to implement
> HTTP(S) health checks. Both default executors (command and docker)
> leverage
> `curl` binary for sending HTTP(S) requests and connect to `127.0.0.1`,
> hence a task must listen on all interfaces. On Linux, For BRIDGE and
> USER
> modes, docker executor enters the task's network namespace.
>
>   * [MESOS-3421] - **Experimental** Support sharing of resources across
> containers. Currently persistent volumes are the only resources
> allowed to
> be shared.
>
>   * [MESOS-3567] - **Experimental** support for TCP health checks.
> Executors
> may now use the updated `HealthCheck` protobuf to implement TCP health
> checks. Both default executors (command and docker) connect to
> `127.0.0.1`,
> hence a task must listen on all interfaces. On Linux, For BRIDGE and
> USER
> modes, docker executor enters the task's network namespace.
>
>   * [MESOS-4324] - Allow access to persistent volumes as read-only or
> read-write
> by tasks. Mesos doesn't allow persistent volumes to be created as
> read-only
> but in 1.1 it starts allow tasks to use the volumes as read-only. This
> is
> mainly motivated by shared persistent volumes but applies to regular
> persistent volumes as well.
>
>   * [MESOS-5275] - **Experimental** support for linux capabilities.
> Frameworks
> or operators now have fine-grained control over the capabilities that a
> container may have. This allows a container to run as root, but not
> have all
> the privileges associated with the root user (e.g., CAP_SYS_ADMIN).
>
>   * [MESOS-5344] -- **Experimental** support for partition-aware Mesos
> frameworks. In previous Mesos releases, when an agent is partitioned
> from
> the master and then reregisters with the cluster, all tasks running on
> the
> agent are terminated and the agent is shutdown. In Mesos 1.1,
> partitioned
> agents will no longer be shutdown when they reregister with the
> master. By
> default, tasks running on such agents will still be killed (for
> backward
> compatibility); however, frameworks can opt-in to the new
> PARTITION_AWARE
> capability. If they do this, their tasks will not be killed when a
> partition
> is healed. This allows frameworks to define their own policies for how
> to
> handle partitioned tasks. Enabling the PARTITION_AWARE capability also
> introduces a new set of task states: TASK_UNREACHABLE, TASK_DROPPED,
> TASK_GONE, TASK_GONE_BY_OPERATOR, and TASK_UNKNOWN. These new states
> are
> intended to eventually replace the TASK_LOST state.
>
>   * [MESOS-6077] - **Experimental** A new default executor is introduced
> which
> frameworks can use to launch task groups as nested containers. All the
> nested containers share resources likes cpu, memory, network and
> volumes.
>
>   * [MESOS-6014] - **Experimental** A new port-mapper CNI plugin, the
> `mesos-cni-port-mapper` has been introduced. For Mesos containers,
> with the
> CNI port-mapper plugin, users can now expose container ports through
> host
> ports using DNAT. This is especially useful when Mesos containers are
> attached to isolated CNI networks such as private bridge networks, and
> the
> services running in the container needs to be exposed outside these
> isolated networks.
>
>
> The CHANGELOG for the release is available at:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_
> plain;f=CHANGELOG;hb=1.1.0-rc1
> 
> 
>
> The candidate for Mesos 1.1.0 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.1.0-rc1/mesos-1.1.0.tar.gz
>
> The tag to be voted on is 1.1.0-rc1:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.1.0-rc1
>
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.1.0-rc1/
> mesos-1.1.0.tar.gz.md5
>
> The signature of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.1.0-rc1/
> mesos-1.1.0.tar.gz.asc
>
> The PGP key used to sign the release is here:
> 

Re: On creating actor instances in Mesos

[Gastón Kleiman]

Hi,

As you can see in MESOS-5917, I made sure that all the processes I could
find specify a distinguishable IDs.

After talking to Alex R and Ben M, I enforced the following naming schema:

For processes created by Mesos:

   - Every process must specify a distinguishable process ID.

   - The process ID must contain only lowercase characters and use a dash
as word separator, e.g., `zookeeper-leader-contender`.

   - A common pattern is to prefix the ID with the name of the component,
e.g., `log-recover`, `logrotate-logger`.

For processes created by libprocess:

   - The ID of a process internal to libprocess (one with not associated
route/endpoint) must be enclosed in double underscores, and use underscores
instead of dashes as word separator, e.g., `__authentication_router__`.

   - The Mesos process ID naming schema applies to libprocess exposed to
libprocess users, via a route/associated to an endpoint, e.g., use `help`
instead of `__help__`.

>From now on, please make sure you adhere to this naming scheme when
defining new processes!

Thanks,

-Gastón


On Sat, Jul 23, 2016 at 12:04 AM, Timothy Chen  wrote:

> +1
>
> Previously when I was adding tracing to Mesos this was one of the most
> missing piece of metadata to easily detect sender and receiver
> information.
>
> Tim
>
> On Fri, Jul 22, 2016 at 11:07 PM, Alex Rukletsov 
> wrote:
> > Folks,
> >
> > I've noticed recently that some actors do not specify a distinguishable
> > actor ID. As a result, it may be hard to match output to a specific
> actor,
> > for example an excerpt from "__processes__" endpoint:
> >
> > [{"events":[],"id":"(10)"},{"events":[],"id":"(11)"},{"
> events":[],"id":"(1279859)"},{"events":[],"id":"(15)"},
> > ... ]
> >
> > Every time you create an actor, i.e., a `ProcessBase` instance, you most
> > probably want to give it a meaningful id. Consider `StatusUpdateManager`.
> > Currently, the code does not specify the ID:
> >
> > StatusUpdateManagerProcess::StatusUpdateManagerProcess(const Flags&
> _flags)
> >   : flags(_flags), paused(false) {}
> >
> > Instead, a preferred way of calling the `StatusUpdateManagerProcess`
> c-tor
> > would be:
> >
> > StatusUpdateManagerProcess::StatusUpdateManagerProcess(const Flags&
> _flags)
> >   : ProcessBase(process::ID::generate("status-update-manager")),
> > flags(_flags),
> > paused(false) {}
> >
> > Best,
> > Alex
>