Re: Proposing change to the allocatable check in the allocator

I would suggest we also consider the possibility of adding per framework control on `min_allocatable_resources`. If we want to consider supporting per-framework setting, we should probably model this as a protobuf, rather than a free form JSON. The same protobuf can be reused for both master

[Design Doc] External Resource Provider and CSI

Folks, As a natural extension to prior work [1, 2] to improve storage support in Mesos, I'm working on the general design of external resource providers, and the specific design for external storage support through CSI [3]. The goal is to enable Mesos to manage cluster-wide resources such as EBS

Proposing change to the allocatable check in the allocator

Hi: The allocatable check in the allocator (shown below) was originally introduced to help alleviate the situation where a framework receives some resources, but no cpu/memory, thus cannot

Re: Follow up on instructions on CMake and VSCode support

> On Jun 11, 2018, at 1:24 PM, Andrew Schwartzmeyer > wrote: > > Ah, so with VS Code it's _mostly_ automatic; I don't actually use VS > Code much myself, though Akash does. > > I have a review up here https://reviews.apache.org/r/67308/ that goes > over setting up and using Cquery (which is

Re: Follow up on instructions on CMake and VSCode support

Ah, so with VS Code it's _mostly_ automatic; I don't actually use VS Code much myself, though Akash does. I have a review up here https://reviews.apache.org/r/67308/ that goes over setting up and using Cquery (which is _also_ used by VS Code, but in the background) with Emacs, and was hoping to

Follow up on instructions on CMake and VSCode support

Hi Andrew, I remembered that you gave an pretty exciting talk about setting up CMake and VSCode to parse Mesos code base. I'm quite curious on setting that up myself. Can you share any instructions/notes about that? Thanks! -- Cheers, Zhitao Li

[GitHub] mesos pull request #296: Add xiao wei.

Github user sharego commented on a diff in the pull request: https://github.com/apache/mesos/pull/296#discussion_r194521400 --- Diff: docs/contributors.yaml --- @@ -825,3 +825,11 @@ - xingz...@cn.ibm.com jira_user: dongdong reviewboard_user: dongdong +

[GitHub] mesos pull request #296: Add xiao wei.

Github user jieyu commented on a diff in the pull request: https://github.com/apache/mesos/pull/296#discussion_r194518563 --- Diff: docs/contributors.yaml --- @@ -825,3 +825,11 @@ - xingz...@cn.ibm.com jira_user: dongdong reviewboard_user: dongdong +

[GitHub] mesos pull request #296: Add xiao wei.

GitHub user sharego opened a pull request: https://github.com/apache/mesos/pull/296 Add xiao wei. Add xiao wei You can merge this pull request into a Git repository by running: $ git pull https://github.com/sharego/mesos xiaowei Alternatively you can review and apply these