Re: Initial Design Document Apache Mesos Federation (JIRA 3548)

Hi , In the proposed the design the PE(Policy Engine) will recommend a new DC the framework can connect to at the time of bursting. It is upto the framework to perform contraction or suppress itself from the ' public cloud ' and use offers from its own datacenter. Yes the second part is true,

Re: Initial Design Document Apache Mesos Federation (JIRA 3548)

if you “burst” into another datacenter because of unavailable “local” resources do you contract when resources are free? If your purpose of bursting is the use case of an on-prem site bursting into a public provider it would seem logical the contraction would be desired to free that public

Re: Initial Design Document Apache Mesos Federation (JIRA 3548)

Hi All, Only 9 have responded so far to the survey. Your response is really important to understand communities preference. Thanks in Advance, Dhilip On Mon, Aug 1, 2016 at 4:37 PM, DhilipKumar Sankaranarayanan < s.dhilipku...@gmail.com> wrote: > Hi All, > > Sorry for the long gap. We had an

Re: Initial Design Document Apache Mesos Federation (JIRA 3548)

Hi All, Sorry for the long gap. We had an interesting discussion last week at Mesosphere HQ again on this topic before the Mesos SF Meetup. The discussion revolved around several areas and suggestions on the proposed design. One of the main item that popped up was the approach through which we

Re: Initial Design Document Apache Mesos Federation (JIRA 3548)

Hi All, I got a chance to bring this up during yesterdays Community Sync. It was great discussing with you all. As a general feedback the role of policy engine in the design needs to be clearer, i will update the Document with more information on PE very soon. We are yet to get more insight on

Re: Initial Design Document Apache Mesos Federation (JIRA 3548)

On Thu, Jul 14, 2016 at 2:40 AM, DhilipKumar Sankaranarayanan < s.dhilipku...@gmail.com> wrote: > HI Alex, > > Thanks for taking a look. We have simplified the design since the > conference. The Allocation and Anonymous modules where only helping us to > control the offers sent to the

Re: Initial Design Document Apache Mesos Federation (JIRA 3548)

No sir there wouldn't be a problem, but all of Mesos is currently C++. It just seems like a somewhat odd dependency, but I can't blame you for wanting to reuse the code already being used. I was just curious is all. Keep up the good work :) On Thursday, July 14, 2016, DhilipKumar Sankaranarayanan

Re: Initial Design Document Apache Mesos Federation (JIRA 3548)

can't wait to have a try . 2016-07-14 14:49 GMT+08:00 DhilipKumar Sankaranarayanan < s.dhilipku...@gmail.com>: > Hi Jeff, > > Thanks for takign a loook. The current design does not enforce Consul, > but im not sure using golang has conflict with Apache Eco-system. Im very > new to ASF but cant

Re: Initial Design Document Apache Mesos Federation (JIRA 3548)

Hi Jeff, Thanks for takign a loook. The current design does not enforce Consul, but im not sure using golang has conflict with Apache Eco-system. Im very new to ASF but cant i not incubate a project written in golang under ASF? I would love to hear more from others too. Regards, Dhilip On

Re: Initial Design Document Apache Mesos Federation (JIRA 3548)

HI Alex, Thanks for taking a look. We have simplified the design since the conference. The Allocation and Anonymous modules where only helping us to control the offers sent to the frameworks. Now we think that Roles and Quota in Moses elegantly solve this problem and we could take advantage of

Re: Initial Design Document Apache Mesos Federation (JIRA 3548)

Would this mean introducing golang and as a result, consul, into mesos proper? Seems like a bit of an odd dependency when everything currently uses existing ASF projects. On Wed, Jul 13, 2016 at 5:11 PM, DhilipKumar Sankaranarayanan < s.dhilipku...@gmail.com> wrote: > Hi All, > > Please find the

Re: Initial Design Document Apache Mesos Federation (JIRA 3548)

This is very cool work, i had a chat w/ another company thinking about doing the exact same thing. I think the proposal is missing several details that make it hard to evaluate on paper (also saw your presentation). 1) Failure semantics, seem to be the same from the proposed design. As a

Initial Design Document Apache Mesos Federation (JIRA 3548)

Hi All, Please find the initial version of the Design Document for Federating Mesos Clusters. https://docs.google.com/document/d/1U4IY_ObAXUPhtTa-0Rw_5zQxHDRnJFe5uFNOQ0VUcLg/edit?usp=sharing We at