Re: Welcome Zhitao Li as Mesos Committer and PMC Member

spares no effort to improve the project quality and to propose >> > ideas. Thank you Zhitao for all contributions! >> > >> > Here is his committer candidate checklist for your perusal: >> > https://docs.google.com/document/d/1HGz7iBdo1Q9z9c8fNRgNNLnj0XQ_ >> > PhDhjXLAfOx139s/ >> > >> > Congrats Zhitao! >> > >> > Cheers, >> > Gilbert >> > >> > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

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

Very well deserved Chun !! On Sun, Mar 11, 2018 at 4:32 PM Qian Zhang wrote: > Congratulations Chun! > > > Regards, > Qian Zhang > > On Sun, Mar 11, 2018 at 2:08 PM, Sam wrote: > >> Congrats Chun >> >> >> Regards, >> Sam Chen | APJ Country Director |

Re: API working group

018 at 8:21 PM, Chun-Hung Hsiao < > > >>> chhs...@mesosphere.io> > > >>> > wrote: > > >>> > > > >>> > > I'm in. Especially, I'd like to continue the work of adapting > gRPC > > >>> into > > >>> > > libprocess, > > >>> > > so we could have a gRPC-based API! > > >>> > > > > >>> > > > >>> > > > >>> > > > >>> > -- > > >>> > Judith Malnick > > >>> > Community Manager > > >>> > 310-709-1517 <(310)%20709-1517> > > >>> > > > >>> > > >> > > >> > > >> > > >> -- > > >> Judith Malnick > > >> Community Manager > > >> 310-709-1517 <(310)%20709-1517> > > >> > > > > > > > > > > > > -- > > > Judith Malnick > > > Community Manager > > > 310-709-1517 <(310)%20709-1517> > > > > > > > > > > > -- > > Judith Malnick > > Community Manager > > 310-709-1517 > > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Surfacing additional issues on agent host to schedulers

tion of any failure in HAProxy and will boiled up as a Mesos healthcheck failure?? > > On Wed, Feb 21, 2018 at 9:45 AM, Avinash Sridharan <avin...@mesosphere.io> > wrote: > > > On Tue, Feb 20, 2018 at 3:54 PM, James Peach <jor...@gmail.com> wrote: > >

Re: Surfacing additional issues on agent host to schedulers

tecture/nodes/#condition > > The condition can automatically taint the node, which could cause pods to > automatically be evicted (ie. if they can't tolerate that specific taint). > > J -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Sharing master detector to modules

gt; implementation requires it to create two different instances of > `MasterDetector`, one for master/agent itself, and one for your module. > That probably means number of watchers on zookeeper would be doubled? Would > that create unnecessary load? > > > > On Tue, Jan 16, 20

Re: Sharing master detector to modules

ance in slave to the module. > > Any comment on this idea? > > Thanks. > > -- > Cheers, > > Zhitao Li > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Chained CNI plugin support

quot;: "host-local", > "subnet": "10.10.10.0/24", > "routes": [ > { "dst": "0.0.0.0/0" } > ] > } > }, > { > "name": "mytuning", > "type": "tuning", > "sysctl": { > "net.core.somaxconn": "500" > } > }, > { >"type": "chain0", >"Chain0_Flag": true, >"Chain0_Arg": "Arg0" > } > ] > } > > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: State of IPV6 and Mesos

ing effort. > > Regards, > Tim Hansen > Senior Software Engineer > Waltham, MA | Verizon Labs > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Welcome James Peach as a new committer and PMC memeber!

Congrats James !! Very well deserved. On Wed, Sep 6, 2017 at 5:47 PM Benjamin Mahler wrote: > Thanks for all that you've done so far for the project James! > > On Wed, Sep 6, 2017 at 2:08 PM, Yan Xu wrote: > >> Hi Mesos devs and users, >> >> Please welcome

Re: Welcome Greg Mann as a new committer and PMC member!

the scheduler and > > executor APIs. > > > > Here is his more formal checklist for your perusal. > > > > https://docs.google.com/document/d/1S6U5OFVrl7ySmpJsfD4fJ3_ > R8JYRRc5spV0yKrpsGBw/edit > > > > Thanks, > > Vinod > > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Proposal new workflow to engage more developer to involved in mesos project

e learn curve is here, > not > > >> trivial. > > >> > > >> So proposal: > > >> > > >> quote from tim chen's chat in the chat group: > > >> > > >> "I think the current spark flow, where issues are in jira and code is > > >> happening in github is a good compromise" > > >> > > >> if you like it proposal, please +1 > > >> > > >> > > >> -- > > >> Deshi Xiao > > >> Twitter: xds2000 > > >> E-mail: xiaods(AT)gmail.com > > > > > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Welcome Gilbert Song as a new committer and PMC member!

y > regarding > >>> > their > >>> > > patches, questions and etc. He also played an important role > >>> organizing > >>> > > MesosCon Asia last year and this year! > >>> > > > >>> > > His formal committer checklist can be found here: > >>> > > https://docs.google.com/document/d/1iSiqmtdX_0CU-YgpViA6r6PU_ > >>> > aMCVuxuNUZ458FR7Qw/edit?usp=sharing > >>> > > > >>> > > Welcome, Gilbert! > >>> > > > >>> > > - Jie > >>> > > >>> > >> > >> > > > > > > -- > > Cheers, > > > > Zhitao Li > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: CNI: Mesos containers need to access Mesos agent

os container networks don't need to be > generally open to the Mesos host networks. > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245 <(323)%20702-5245>

Re: Mesos CNI Result spec

uot;nameservers": [ > "10.10.10.1" > ] > } > } > > And here's the modified JSON that is working: > > { > "cniVersion": "0.3.0", > "interfaces": [ > { > "name": "eth0", > "mac": "36:c0:43:08:97:f7", > "sandbox": "" > } > ], > "ip4": { > "ip": "10.10.10.170/24", > "gateway": "10.10.10.1", > "interface": 0 > }, > "dns": { > "nameservers": [ > "10.10.10.1" > ] > } > } > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Welcome Kevin Klues as a Mesos Committer and PMC member!

eDKIxTYyboK_ > > uiOJ4Uwr6ruKTlFM/edit > > > > Thanks! > > Ben > > > > [1] http://mesos.apache.org/documentation/latest/gpu-support/ > > [2] > > https://docs.google.com/document/d/1nAVr0sSSpbDLrgUlAEB5hKzCl482N > > SVk8V0D56sFMzU > > [3] > > https://docs.google.com/document/d/1r6Iv4Efu8v8IBrcUTjgYkvZ32WVsc > > gYqrD07OyIglsA/ > > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

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

Mesos 1.0.3! > > > The vote is open until Mon Jan 23rd 17:00:00 PST 2017 and passes if a > majority of at least 3 +1 PMC votes are cast. > > > [ ] +1 Release this package as Apache Mesos 1.0.3 > > [ ] -1 Do not release this package because ... > > > Thanks, > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

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

al 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/137MYwxEw9QCZRH09CXfn1544p1LuM > uoj9LxS-sk2_F4/edit > >>> > >>> Thanks, > >>> Vinod > >>> > >>> > > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Welcome Guangya Liu as Mesos Committer and PMC member!

pport for docker containerizer, Mesos Tiers/Optimistic Offer design, >> scarce resources discussion, and many others. >> >> His formal checklist is here: >> https://docs.google.com/document/d/1tot79kyJCTTgJHBhzStFKrVkDK4pX >> qfl-LHCLOovNtI/edit?usp=sharing >> <https://docs.google.com/document/d/1tot79kyJCTTgJHBhzStFKrVkDK4pXqfl-LHCLOovNtI/edit?usp=sharing> >> >> Thanks, >> - Jie >> > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

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

IY_UU5_0/edit?ts=57e0029d> > for your perusal. > > Thanks, > Vinod > > P.S: Sorry for the delay in sending the welcome email. > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Adding a reload end-point to `network/cni` isolator

t can fail framework's request and remove > that CNI network from its cache. So it is kind of lazy delete in cache. > > > Thanks, > Qian Zhang > > On Thu, Dec 8, 2016 at 8:12 AM, Avinash Sridharan <avin...@mesosphere.io> > wrote: > > > On Wed, Dec 7, 2016

Re: Adding a reload end-point to `network/cni` isolator

t-tabpanel#comment-15652501 > > You are correct. We don't store the config in-memory just the `name`. So we will be reading the config every time we launch a new container. So looks like "delete" is the only operation that will need an agent restart. > > On Wed, Dec 7,

Re: Adding a reload end-point to `network/cni` isolator

of CNI networks. The two operations above will still need an agent restart. On Wed, Dec 7, 2016 at 3:40 PM, Avinash Sridharan <avin...@mesosphere.io> wrote: > > > On Wed, Dec 7, 2016 at 3:31 PM, Avinash Sridharan <avin...@mesosphere.io> > wrote: > >> >> &g

Re: Adding a reload end-point to `network/cni` isolator

On Wed, Dec 7, 2016 at 3:31 PM, Avinash Sridharan <avin...@mesosphere.io> wrote: > > > On Wed, Dec 7, 2016 at 3:17 PM, Daniel Osborne <d...@tigera.io> wrote: > >> Chiming in since I raised an identical issue a few weeks back: >> https://issues.apache.org/jira/

Re: Adding a reload end-point to `network/cni` isolator

continuously launches containers on a non-existent network (due to operator error or malicious intent). This would result in quite a few unnecessary reads. However, if the reload endpoint is not a possibility than this would be the route we have to take. -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Adding a reload end-point to `network/cni` isolator

ministic. The behavior would be much cleaner if we can make it deterministic. > > Best, > -Dan > > On Wed, Dec 7, 2016 at 3:01 PM, Avinash Sridharan <avin...@mesosphere.io> > wrote: > > > @adam @vinod Starting to work on > > https://issues.apache.org/jira/brow

Adding a reload end-point to `network/cni` isolator

with an empty HTTP response. Wanted to run this by you guys to understand the implications on authn/authz and if this is the right place (the `network/cni` isolator) to host this endponit? -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: On increasing visibility into experimental features.

es declared > > > stable, and add new experimental features. > > > > > > With this change users will have a complete overview of experimental > > > functionality per release, without searching the CHANGELOG for when and > > > whether a certain feature became production-ready. > > > > > > What do you think? > > > > > > AlexR. > > > > > > > > > > > -- > > Cheers, > > > > Zhitao Li > > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Design Document for IPv6 support

s-ipv6.pdf > > For those who remember my previous mails, this proposal is actually much > more streamlined in comparison, looking to provide minimal core IPv6 > connectivity which can be expanded in the future if desired. > > I'm looking forward to receive any comments, thoughts, questions, etc. > > Best regards, > Benno > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Unified cgroups isolator

rtantly, the new cgroups isolator supports cgroups v2! > > - Jie > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Fail to get CNI with unified containerizer, job remains stuck on staging

Oliver, you can't have the agent running on 127.0.0.1. The agent needs to be running in a routeabl IP address (choose an IP from one of the interfaces). Reason being that if agent is on local host the executor running in its own network namespace will try to make a connection in its own network

Re: error when using dockerinfo user network

hanks > > > > Olivier > > > > -- > > Olivier Sallou > > IRISA / University of Rennes 1 > > Campus de Beaulieu, 35000 RENNES - FRANCE > > Tel: 02.99.84.71.95 > > > > gpg key id: 4096R/326D8438 (keyring.debian.org) > > Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 > > > > > > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

A port mapping plugin for CNI

/1ZwXZ_utpxmy9vccYiL0q86efgpWpjmmKLQ0S4Mmz9N4/edit?usp=sharing Would be great if the community can share their feedback on the proposed port mapping CNI plugin. Thanks, -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: cni / public port questions

, Jul 29, 2016 at 12:44 AM, Olivier Sallou <olivier.sal...@irisa.fr> > wrote: > > > > > > > - Mail original - > > > De: "Jie Yu" <yujie@gmail.com> > > > À: "dev" <dev@mesos.apache.org> > > > Cc: &

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

ocess: > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > SIGTERM for the graceful kill and SIGKILL for the forcible > >>>>>>> kill. For > >>>>>>> >> > docker > >>>>>>> >> > > >>>>>>> >> > executor-less tasks the grace period is passed to 'docker > >>>>>>> stop > >>>>>>> >> --time'. > >>>>>>> >> > This > >>>>>>> >> > > >>>>>>> >> > feature supersedes the '--docker_stop_timeout', which is > now > >>>>>>> >> > deprecated. > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > * [MESOS-4908] - The task kill policy defined within > >>>>>>> 'TaskInfo' can > >>>>>>> >> now > >>>>>>> >> > be > >>>>>>> >> > > >>>>>>> >> > overridden when the scheduler kills the task. This can be > >>>>>>> used by > >>>>>>> >> > schedulers > >>>>>>> >> > > >>>>>>> >> > to forcefully kill a task which is already being killed, > >>>>>>> e.g. if > >>>>>>> >> > something > >>>>>>> >> > > >>>>>>> >> > went wrong during a graceful kill and a forcible kill is > >>>>>>> desired. > >>>>>>> >> Note > >>>>>>> >> > that > >>>>>>> >> > > >>>>>>> >> > it is the executor's responsibility to honor the > >>>>>>> >> > 'Event.kill.kill_policy' > >>>>>>> >> > > >>>>>>> >> > field and override the task's kill policy and kill policy > >>>>>>> from a > >>>>>>> >> > previous > >>>>>>> >> > > >>>>>>> >> > kill task request. To use this feature, schedulers and > >>>>>>> executors > >>>>>>> >> must > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > support HTTP API; use the '--http_command_executor' agent > >>>>>>> flag to > >>>>>>> >> > ensure > >>>>>>> >> > > >>>>>>> >> > the agent launches the HTTP API based command executor. > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > * [MESOS-4949] - The executor shutdown grace period can now > be > >>>>>>> >> configured > >>>>>>> >> > in > >>>>>>> >> > > >>>>>>> >> > `ExecutorInfo`, which overrides the agent flag. When > >>>>>>> shutting down > >>>>>>> >> an > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > executor the agent will wait in a best-effort manner for > >>>>>>> the grace > >>>>>>> >> > period > >>>>>>> >> > > >>>>>>> >> > specified here before forcibly destroying the container. > The > >>>>>>> >> executor > >>>>>>> >> > must > >>>>>>> >> > > >>>>>>> >> > not assume that it will always be allotted the full grace > >>>>>>> period, as > >>>>>>> >> > the > >>>>>>> >> > > >>>>>>> >> > agent may decide to allot a shorter period and failures / > >>>>>>> forcible > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > terminations may occur. Together with kill policies this > >>>>>>> gives > >>>>>>> >> > frameworks > >>>>>>> >> > > >>>>>>> >> > flexibility around how to clean up tasks and executors. > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > * [MESOS-3094] - **Experimental** support for launching > mesos > >>>>>>> tasks on > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > Windows. Note that there are no isolation guarantees > >>>>>>> provided yet. > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > * [MESOS-4090] - The `mesos.native` python module has been > >>>>>>> split into > >>>>>>> >> > two, > >>>>>>> >> > > >>>>>>> >> > `mesos.executor` and `mesos.scheduler`. This change also > >>>>>>> removes > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > un-necessary 3rd party dependencies from `mesos.executor` > >>>>>>> and > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > `mesos.scheduler`. `mesos.native` still exists, combining > >>>>>>> both > >>>>>>> >> modules > >>>>>>> >> > for > >>>>>>> >> > > >>>>>>> >> > backwards compatibility with existing code. > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > * [MESOS-1478] - Phase I of the Slave to Agent rename is > >>>>>>> complete. To > >>>>>>> >> > support > >>>>>>> >> > > >>>>>>> >> > the rename, new duplicate flags (e.g., > >>>>>>> --agent_reregister_timeout), > >>>>>>> >> new > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > binaries (e.g., mesos-agent) and WebUI sandbox links have > >>>>>>> been > >>>>>>> >> added. > >>>>>>> >> > All > >>>>>>> >> > > >>>>>>> >> > the logging output has been updated to use the term > 'agent' > >>>>>>> now. > >>>>>>> >> Flags, > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > binaries and scripts with 'slave' keyword have been > >>>>>>> deprecated (see > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > "Deprecations section below"). > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > * [MESOS-4312] - **Experimental** support for building and > >>>>>>> running > >>>>>>> >> mesos > >>>>>>> >> > on > >>>>>>> >> > > >>>>>>> >> > IBM PowerPC platform. > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > * [MESOS-4189] - Weights for resource roles can now be > >>>>>>> configured > >>>>>>> >> > dynamically > >>>>>>> >> > > >>>>>>> >> > via the new '/weights' endpoint on the master. > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > * [MESOS-4424] - Support for using Nvidia GPUs as a resource > >>>>>>> in the > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > Mesos "unified" containerizer. This support includes > running > >>>>>>> >> containers > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > with and without filesystem isolation (i.e. running both > >>>>>>> imageless > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > containers as well as containers using a docker image). > >>>>>>> Frameworks > >>>>>>> >> must > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > opt-in to receiving GPU resources via the GPU_RESOURCES > >>>>>>> framework > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > capability (see the scarce resource problem in > MESOS-5377). > >>>>>>> We > >>>>>>> >> support > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > 'nvidia-docker'-style docker containers by injecting a > >>>>>>> volume that > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > contains the Nvidia libraries / binaries when the docker > >>>>>>> image has > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > the 'com.nvidia.volumes.needed' label. Support for the > >>>>>>> docker > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > containerizer will come in a future release. > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > * [MESOS-5724] - SSL certificate validation allows for > >>>>>>> additional IP > >>>>>>> >> > address > >>>>>>> >> > > >>>>>>> >> > subject alternative name extension verification. > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > 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.0.0-rc2 > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > >>>>>>> > > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > The candidate for Mesos 1.0.0 release is available at: > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > >>>>>>> > https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc2/mesos-1.0.0.tar.gz > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > The tag to be voted on is 1.0.0-rc2: > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > >>>>>>> > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.0.0-rc2 > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > The MD5 checksum of the tarball can be found at: > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > >>>>>>> > https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc2/mesos-1.0.0.tar.gz.md5 > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > The signature of the tarball can be found at: > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > >>>>>>> > https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc2/mesos-1.0.0.tar.gz.asc > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > The PGP key used to sign the release is here: > >>>>>>> >> > > >>>>>>> >> > https://dist.apache.org/repos/dist/release/mesos/KEYS > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > The JAR is up in Maven in a staging repository here: > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> > https://repository.apache.org/content/repositories/orgapachemesos-1149 > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > Please vote on releasing this package as Apache Mesos 1.0.0! > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > The vote is open until Tue Jul 12 15:00:00 PDT 2016 and passes > >>>>>>> if a > >>>>>>> >> > majority of at least 3 +1 PMC votes are cast. > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > [ ] +1 Release this package as Apache Mesos 1.0.0 > >>>>>>> >> > > >>>>>>> >> > [ ] -1 Do not release this package because ... > >>>>>>> >> > > >>>>>>> >> > > >>>>>>> >> > Thanks, > >>>>>>> >> > > >>>>>>> >> > Vinod > >>>>>>> >> > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>> > -- > >>>>>>> > Cheers, > >>>>>>> > > >>>>>>> > Zhitao Li > >>>>>>> > > >>>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Cheers, > >>>>>> > >>>>>> Zhitao Li > >>>>>> > >>>>> > >>>>> > >>>> > >>> > >>> > >>> -- > >>> Best Regards, > >>> Haosdent Huang > >>> > >> > >> > >> > >> -- > >> Deshi Xiao > >> Twitter: xds2000 > >> E-mail: xiaods(AT)gmail.com > >> > > > > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: [Replicated Log] Enable Mesos to use etcd for replicated_log

ome help on better understanding replicated_log internals. > #3 Is there a plan to use replicated_log to do master contend/detect > instead of ZK? If yes, what's the status? > > Your help and suggestions are highly appreciated!! > > Thanks, > /Jay > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Slack as the canonical chat channel

> >> - > > > > >> > > > > >> Community metrics (e.g., affiliations) > > > > >> - > > > > >> > > > > >> AI [Mpark] : Blog post around Mesocon NA community talk > > > > >> - > > > > >> > > > > >> AI [Artem] : Email dev@ and personally to solicit > affiliations > > > for > > > > >> contributor metrics > > > > >> > > > > >> > > > > >> > > > > >> - > > > > >> > > > > >> Communication Channel > > > > >> - > > > > >> > > > > >> Slack, HipChat, IRC? > > > > >> - > > > > >> > > > > >> AI [Vinod] : Email dev@ and user@ about using Slack as > > canonical > > > > >> communication channel > > > > >> > > > > >> > > > > >>> On Wed, Jun 15, 2016 at 6:46 PM, Greg Mann <g...@mesosphere.io> > > > wrote: > > > > >>> > > > > >>> Also note: tomorrow's community sync will be hosted at Mesosphere > > HQ, > > > 88 > > > > >>> Stevenson St., San Francisco, CA. Community members are welcome > to > > > attend > > > > >>> in person! > > > > >>> > > > > >>> As usual, Google Hangout and Youtube links for the meeting will > be > > > posted > > > > >>> in the Google doc just before the meeting begins. > > > > >>> > > > > >>> Cheers, > > > > >>> Greg > > > > >>> > > > > >>>> On Wed, Jun 15, 2016 at 3:01 PM, Michael Park <mp...@apache.org > > > > > wrote: > > > > >>>> > > > > >>>> -- Forwarded message -- > > > > >>>> From: "Google Calendar" <calendar-notificat...@google.com> > > > > >>>> Date: Jun 15, 2016 6:00 PM > > > > >>>> Subject: Notification: Community Meeting @ Thu Jun 16, 2016 3pm > - > > > 4pm > > > > >>>> (Apache Mesos) > > > > >>>> To: "Michael Park" <mcyp...@gmail.com> > > > > >>>> Cc: > > > > >>>> > > > > >>>> more details » > > > > >>>> < > > > > >> https://www.google.com/calendar/event? > > > > > > > > > > > > > action=VIEW=dmF2a2xrZG1mNGhsb25qYXJzb2ZnOGxrMWNfMjAxNjA2MTZUMjIwMDAwWiAyaGVjdm5kYzBtbmFxbGlyMzRjcW5mdnRha0Bn > > > > > > > >>>> Community Meeting > > > > >>>> > > > > >>>> *When* > > > > >>>> Thu Jun 16, 2016 3pm – 4pm Pacific Time > > > > >>>> > > > > >>>> *Calendar* > > > > >>>> Apache Mesos > > > > >>>> > > > > >>>> *Who* > > > > >>>> • > > > > >>>> Michael Park - creator > > > > >>>> • > > > > >>>> dev@mesos.apache.org > > > > >>>> *Attachments* > > > > >>>> Mesos Developer Community Sync > > > > >>>> < > > > > >> https://docs.google.com/document/d/ > > > > 153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit?usp=drive_web > > > > >>>> > > > > >>>> Invitation from Google Calendar < > https://www.google.com/calendar/ > > > > > > > >>>> > > > > >>>> You are receiving this email at the account mcyp...@gmail.com > > > because > > > > >> you > > > > >>>> set a notification for this event on the calendar Apache Mesos. > > > > >>>> > > > > >>>> You can change your notifications for specific events in the > event > > > > >> details > > > > >>>> page in https://www.google.com/calendar/. > > > > >>>> > > > > >>>> Forwarding this invitation could allow any recipient to modify > > your > > > RSVP > > > > >>>> response. Learn More > > > > >>>> <https://support.google.com/calendar/answer/37135#forwarding>. > > > > > > > > > > > > > > > > > > > > -- > > > > > Best Regards, > > > > > Haosdent Huang > > > > > > > > > > > > > > > -- > > ~Vinit > > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Welcome Anand and Joseph as new committers!

Modules. He has also been a valuable contributor and reviewer to >> our testing infrastructure and the Windows work. His formal committer >> checklist is here >> <https://docs.google.com/document/d/1o7qLQJQ7TZCaf49gSNc6SSl29qAFagYH2STDfhHDDPw/edit?usp=sharing> >> .

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

> What do you think? > > - Jie > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Mesos Calico CNI

rne/net-modules/tree/cni > > I’d be happy to assist you in getting it working on your repo. Let me > know if you need any assistance. > > We haven't published much information on this as of yet, since Mesos CNI > support is only just rolling out now. > > -Dan > > On

Re: Mesos Calico CNI

repository on Github > >> >> > >> >> https://github.com/ContainerSolutions/mesos-calico-cni-sandbox > >> >> > >> >> In this repo I build the Mesos master branch and > >> >> https://github.com/projectcalico/calico-cni, create a local cluster > >> >> and deploy an application. I don't see anything in the logs about > cni, > >> >> except that it loads the cni isolator. > >> >> > >> >> Is there some user documentation for this feature? If not I am happy > >> >> to write documentation once I figure out how this feature works. > >> >> > >> >> Cheers, > >> >> > >> >> Frank > >> > > >> > > >> > > >> > > >> > -- > >> > Best Regards, > >> > Haosdent Huang > >> > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: [Proposal] Remove the default value for agent work_dir

n acceptable change because '/tmp/mesos' is not a > > suitable location for the agent work directory except for short-term > local > > testing, and any production scenario that is currently using this > location > > should be altered immediately. > > > > +1 from me too. Defaulting to /tmp just helps people shoot themselves in > > the foot. > > > > J > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: [DISCUSS] Fetching Docker Images Requiring User Credentials.

ot;, > >> >> "type" : "", > >> >> "credential" : > >> >> { > >> >> // Custom based on type... > >> >> }, > >> >>

Re: [DISCUSS] Fetching Docker Images Requiring User Credentials.

On Tue, Mar 15, 2016 at 11:43 AM, Vinod Kone <vinodk...@apache.org> wrote: > moved core@ to *bcc* > > On Tue, Mar 15, 2016 at 11:18 AM, Avinash Sridharan <avin...@mesosphere.io > > wrote: > >> Why not follow option 2, but instead of passing the agent credential

Re: [DISCUSS] Fetching Docker Images Requiring User Credentials.

er pull, we set the > $HOME env for the subprocess to point to the sandbox so that the docker > client can pick up that .dockercfg when pulling images. > > Any comment/advice will be absolutely welcome! > > Thanks, > Gilbert/Jie > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

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

-4ddc-8741-74bd7e71f91c ro init=/bin/systemd console=hvc0 console=ttyS0 cgroup_enable=memory I think the test filters should have caught the absence of the cgroup memory subsystem. If I can't find a JIRA for this, will go ahead and file one. On Fri, Mar 4, 2016 at 6:52 PM, Avinash Sridharan

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

wice. >> > >> > On Fri, Mar 4, 2016 at 1:25 PM, Vinod Kone <vinodk...@apache.org> >> wrote: >> > >> >> On Thu, Mar 3, 2016 at 5:43 PM, Vinod Kone <vinodk...@apache.org> >> wrote: >> >> >> >> > Tue Mar 10 17:00:00 PST 2016 >> >> >> >> >> >> Sorry. This should be Mar 8th not 10th. >> >> >> > >> > >> > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

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

/Linux On Fri, Mar 4, 2016 at 6:49 PM, Avinash Sridharan <avin...@mesosphere.io> wrote: > I am seeing the following crash when I run mesos build of 0.28.0-rc1 `sudo > bin/mesos-tests.sh` : > [ RUN ] MemIsolatorTest/1.MemUsage > F0305 02:43:01.791003 32494 isolator_tests.c

Re: Need CHANGELOG updates

net_cls isolator update under review: https://reviews.apache.org/r/44350/ On Thu, Mar 3, 2016 at 11:11 AM, Avinash Sridharan <avin...@mesosphere.io> wrote: > Hi Vinod, > Will file a ticket and update the change log for the net_cls isolator. > > -Avinash > > On Thu, Mar 3

Re: Performance isolation working group meeting on Friday 10am PST

> 4) Discussion on actuating isolation for resources that are accounted > / > > not > > >> accounted by Mesos > > >> For now, this will be the hangout: > > >> https://plus.google.com/hangouts/_/qni.dk/nik and we will follow up > > with > > >> any changes > > >> > > >> -- > > >> Niklas > > > > > > > > > > > > -- > > > ~Kevin > > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: Enable compiler optimization by default?

uences of not enabling compiler > > optimizations can be pretty severe: 5x in a benchmark I just ran, and > > we've seen between 2x and 30x (!) performance differences for some > > real-world workloads. > > > > Neil > > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Re: .gitignore-template

te to `support/gitignore` and have > `bootstrap` > > symlink it to `.gitignore`. > > > > Please let me know if you're opposed to this change. > > > > Thanks! > > > > MPark. > > > > -- > ~Kevin > -- Avinash Sridharan, Mesosphere +1 (323) 702 5245

Question on adding commit hook to enforce leading whitespace in comments

community. So the questions that we would like to ask are: a) Should we enforce the "single space between // and comment” rule explicitly using a git commit hook ? b) Whether we want single space or double space for trailing comments, or maybe leave it open-ended ?? Thanks, Avinash -- Av