lto:vinodk...@apache.org <mailto:vinodk...@apache.org>>
<mailto:vinodk...@apache.org
<mailto:vinodk...@apache.org> <mailto:vinodk...@apache.org
<mailto:vinodk...@apache.org>>>
<mailto:vinodk...@apache.org
<mailto:vin
;
>> --
>>
>> Aaron Carey
>> Production Engineer - Cloud Pipeline
>> Industrial Light & Magic
>> London
>> 020 3751 9150
&g
oris Van Remoortere; vinodk...@apache.org
<mailto:vinodk...@apache.org>
<mailto:vinodk...@apache.org <mailto:vinodk...@apache.org>>
<mailto:vinodk...@apache.org
<mailto:vinodk...@apache.org> <mailto:vinodk...@apache.org
https://issues.apache.org/jira/browse/MESOS-3059
>>
>> --
>>
>> Aaron Carey
>> Production Engineer - Cloud Pipeline
>> Industrial Light & Magic
>> London
>> 020
@apache.org
<mailto:vinodk...@apache.org>
<mailto:vinodk...@apache.org <mailto:vinodk...@apache.org>>
Subject: Re: Rack awareness support for Mesos
Hi everyone
Let me summarize the discussion about Rack awareness in the
ser@mesos.apache.org>;
d...@mesos.apache.org <mailto:d...@mesos.apache.org>
Cc: Joris Van Remoortere; vinodk...@apache.org
<mailto:vinodk...@apache.org>
Subject: Re: Rack awareness support for Mesos
Hi everyone
Let me summarize the discussion about Rack
gt;> ________________
>> From: Du, Fan [fan...@intel.com <mailto:fan...@intel.com>]
>> Sent: 14 June 2016 07:24
>> To: user@mesos.apache.org <mailto:user@mesos.apache.org>;
>> d...@mesos.apache.org <mailto:d...@mesos.apac
user@mesos.apache.org <mailto:user@mesos.apache.org>;
d...@mesos.apache.org <mailto:d...@mesos.apache.org>
Cc: Joris Van Remoortere; vinodk...@apache.org
<mailto:vinodk...@apache.org>
Subject: Re: Rack awareness support for Mesos
Hi everyone
Let me summarize
uction Engineer - Cloud Pipeline
> Industrial Light & Magic
> London
> 020 3751 9150
>
>
> From: Du, Fan [fan...@intel.com]
> Sent: 14 June 2016 07:24
> To: user@mesos.apache.org; d...@mesos.apache.org
> Cc: Joris Van Remoortere;
7:24
To: user@mesos.apache.org; d...@mesos.apache.org
Cc: Joris Van Remoortere; vinodk...@apache.org
Subject: Re: Rack awareness support for Mesos
Hi everyone
Let me summarize the discussion about Rack awareness in the community so
far. First thanks for all the comments, advices or challenges! :)
Hi everyone
Let me summarize the discussion about Rack awareness in the community so
far. First thanks for all the comments, advices or challenges! :)
#1. Stick with attributes for rack awareness
For compatibility with existing framework, I tend to be ok with using
attributes to convey the r
On 2016/6/8 0:58, james wrote:
Do I have access to the jira system by default joining this list,
or do I have to request permission somewhere? (sorry jira is new to me
so recommendations on jira, per mesos, in a document, would be keen.)
You need a JIRA account, sign up one here:
https://iss
On Tuesday, June 7, 2016, Du, Fan wrote:
>
>
> On 2016/6/6 23:48, Jörg Schad wrote:
>
>> Hi,
>> thanks for your idea and design doc!
>> Just a few thoughts:
>> a) The scheduling part would be implemented in a framework scheduler and
>> not the Mesos Core, or?
>>
>
> I'm not sure which level of sc
+dev.
@Fan, I responded on the JIRA with some next steps.
Thanks for bringing this up!
—
*Joris Van Remoortere*
Mesosphere
On Tue, Jun 7, 2016 at 12:58 PM, james wrote:
> On 06/07/2016 09:57 AM, Du, Fan wrote:
>
>>
>>
>> On 2016/6/6 21:27, james wrote:
>>
>>> Hello,
>>>
>>>
>>> @Stephen::I gue
On 06/07/2016 09:57 AM, Du, Fan wrote:
On 2016/6/6 21:27, james wrote:
Hello,
@Stephen::I guess Stephen is bringing up the 'security' aspect of who
get's access to the information, particularly cluster/cloud devops,
customers or interlopers?
ACLs should play in this part to address sec
: Du, Fan [fan...@intel.com]
Sent: 07 June 2016 16:16
To: Jörg Schad; user@mesos.apache.org
Subject: Re: Rack awareness support for Mesos
On 2016/6/6 23:48, Jörg Schad wrote:
> Hi,
> thanks for your idea and design doc!
> Just a few thoughts:
> a) The scheduling part would be implemente
On 2016/6/6 23:48, Jörg Schad wrote:
Hi,
thanks for your idea and design doc!
Just a few thoughts:
a) The scheduling part would be implemented in a framework scheduler and
not the Mesos Core, or?
I'm not sure which level of scheduling part do you indicate,
For the "Future" section of proposal
On 2016/6/6 21:27, james wrote:
Hello,
@Stephen::I guess Stephen is bringing up the 'security' aspect of who
get's access to the information, particularly cluster/cloud devops,
customers or interlopers?
ACLs should play in this part to address security concern.
@Fan:: As a consultant
There are a lot of things in Mesos which require a-priori communication
between an agent and a framework in order to properly set resource usage
expectations (example: what does 1 cpu mean?). I'm not seeing how having
customizations in core mesos per "way of looking at resources" is scalable
and fu
Hi,
thanks for your idea and design doc!
Just a few thoughts:
a) The scheduling part would be implemented in a framework scheduler and
not the Mesos Core, or?
b) As mentioned by James, this needs to be very flexible (and not
necessarily based on network structure), afaik people are using labels on
Hello,
@Stephen::I guess Stephen is bringing up the 'security' aspect of who
get's access to the information, particularly cluster/cloud devops,
customers or interlopers?
@Fan:: As a consultant, most of my customers either have or are
planning hybrid installations, where some codes ru
Hi,
This looks potentially interesting. How does it work in a public cloud
deployment scenario? I assume you would just have to disable this
feature, or not enable it?
Cheers,
On 06/06/16 10:17, Du, Fan wrote:
> Hi, Mesos folks
>
> I’ve been thinking about Mesos rack awareness support for a
22 matches
Mail list logo
