In addition to a pool of IPs, we've also discussed other cluster-wide or
globally managed resources, like NAS/SAN bandwidth, site licenses, etc.
We'll be filing a JIRA on that soon, and we'd love to have your input.
As for allocator modules, the core functionality landed in MESOS-2160
FYI, I just tagged Mesos 0.22.1-rc6
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=shortlog;h=refs/tags/0.22.1-rc6,
but I'll give it a day to bake before starting the official vote.
You can also find the latest 0.22.1 java bindings in the maven repo
This is something we're interested in exploring as well. Can we ensure the
design thinking get circulated to the community early on? I agree there
will be many different requirements and it would be helpful to understand
those from the onset.
Ian
On Tue, Apr 28, 2015 at 5:48 PM, Christos
Hello,
We made some final changes on the doc, so I'm updating this thread to point
out that all changes are reflected on a small prototype of the API that you
can find here https://github.com/jimenez/mesos-APIproto.
Please feel free to comment on the new changes on the design doc.
Thanks,
Isabel
I would like to propose that regarding the header include order we follow
the Google Styleguide completely. We currently have an undocumented
exception in that we do not include direct headers first in the
corresponding implementation files (i.e. abc.hpp - abc.cpp).
The reasons, and examples for
I would like to take this opportunity to move the doc from Twitter domain so
that I dont have to manually grant access to each new viewer. I'll post the new
doc link tomorrow.
@vinodkone
On Apr 29, 2015, at 8:54 AM, Isabel Jimenez contact.isabeljime...@gmail.com
wrote:
Hello,
We
Hi Joe,
I think it's a great idea and would love to contribute. Please keep us
posted on progress.
On Apr 28, 2015 5:20 PM, Joe Stein joe.st...@stealth.ly wrote:
Hi Mesos community, there is a lot of work in progress around virtual
routers and custom allocator(s) to enable for every task to
