Re: Mapped diagnostics context - Adding internal Mesos IDs as context to the logs

It's adding *an* extension to the header of the log. In this case after the file name. In the comment above the code you can see that it's: > often used to append the port we're listening on to the logfile That means we can tag our own IDs in there such as Agent ID, Executor ID, Master ID, etc.

Re: LXC Container Support

Also just as an aside, being able to run system containers and not precanned Docker applications would seem to certainly be a missing feature that Mesos could benefit from, as it would allow sysadmins to spin up vanilla Ubuntu, Centos, Debian etc images without doing something funky like using the

Re: Notification: Community Meeting @ Thu Oct 6, 2016 3pm - 4pm PST (Apache Mesos)

Did it cancel? On Oct 6, 2016 6:09 AM, "Michael Park" wrote: > >

[GitHub] mesos pull request #170: typo

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/170 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] mesos pull request #170: typo

GitHub user The-smooth-operator opened a pull request: https://github.com/apache/mesos/pull/170 typo Corrected small typo. You can merge this pull request into a Git repository by running: $ git pull https://github.com/The-smooth-operator/mesos typo Alternatively you can