Re: Looking for a shepherd for MESOS-4965

Zhitao, would you mind adding an item to the agenda of Containerization WG? https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit#heading=h.99ld98fhk6ar On Mon, Mar 5, 2018 at 12:59 PM, Zhitao Li wrote: > Thanks Jie. > > I'll try to start

[GitHub] mesos pull request #269: fix name of --executor_environment_variables

GitHub user benjaminp opened a pull request: https://github.com/apache/mesos/pull/269 fix name of --executor_environment_variables Needs underscores not dashes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/benjaminp/mesos

Re: Looking for a shepherd for MESOS-4965

Zhitao, sure. Let's chat about that during this week's WG meeting! - Jie On Mon, Mar 5, 2018 at 12:59 PM, Zhitao Li wrote: > Thanks Jie. > > I'll try to start with some write up on this. Can we discuss this in this > week's container WG since it's pretty high priority to

Re: Looking for a shepherd for MESOS-4965

Thanks Jie. I'll try to start with some write up on this. Can we discuss this in this week's container WG since it's pretty high priority to our org (some recent accounting shows that it's potentially a lot of saving on hardware). On Mon, Mar 5, 2018 at 11:09 AM, Jie Yu

Re: Looking for a shepherd for MESOS-4965

Zhitao, I can provide some feedback because it most likely overlap with the Resource Provider/CSI work. - Jie On Fri, Mar 2, 2018 at 9:08 PM, Zhitao Li wrote: > Hi, > > As our workload using persistent volume increases, the support for resizing > volumes

[GitHub] mesos pull request #265: Update presentations.md

Github user greggomann commented on a diff in the pull request: https://github.com/apache/mesos/pull/265#discussion_r172287822 --- Diff: docs/presentations.md --- @@ -133,6 +133,10 @@ Presented Summer 2010 at [Yahoo](http://yahoo.com) # Apache Mesos - Training _(Listed in

API Working Group - First Meeting Tomorrow

Hello all, We'll be having our first API working group meeting tomorrow, March 6 at 11am PST. This working group is a great opportunity for us to work toward greater consistency and usability of our API, as well as raise issues with the current interface and plan future directions. You can find