It is easier if you enable it through the network. Stop following the easiest.
> On May 27, 2024, at 03:46, Marc wrote:
>
> Hi,
>
> I was wondering if anyone knows how I could get this sortlist entry added to
> an /etc/resolv.conf?
>
> sortlist 192.168.x.0/255.255.255.0
>
> Could it be that
+1 HPC support, but this requires NUMA support and cgroup features, besides
easier to write modules for new scheduling techniques (beyond DRF).
/Abel
> On 1 Mar 2021, at 09:43, Damien GERARD wrote:
>
> On 2021-03-01 04:14 PM, Klaus Ma wrote:
>> Mesos is really a great project!
>> In addition
starting to have more flexible scheduling strategies
brought-in to Mesos. The idea brought in the previous email
(https://github.com/criteo/mesos-command-modules/) is also good, though task
management would be sent outside Mesos control, which may not be a good thing
in some cases I would guess.
Hi,
Does anyone know if pinning capabilities will ever be available to Mesos?
Someone registered an issue at Jira
(https://issues.apache.org/jira/browse/MESOS-5342), started an
implementation (https://github.com/ct-clmsn/mesos-cpusets), but
apparently it never went through mainline. I success
* Just a misconception in my first sentence I'd like to fix:
By default, Mesos never creates an offer with resources coming from two
different physical nodes (hosts).
The rest I keep. Sorry for that.
Hopefully it is clearer now,
/Abel
On 7/8/19 9:02 PM, Abel Souza wrote:
By default
By default Mesos never offers resources from two different physical
nodes. In order to do so, one has to create his/her own scheduler
enabling the management of (perhaps many) different Mesos offers so to
satisfy higher level framework constraints.
People usually suggest using Marathon to over
Interesting.
I've been working on a paper doing exactly that, but in a different
context. I can share a draft version of it if you like.
Best,
/Abel
On 11/29/18 20:58, Iwanowski, Maciej wrote:
Hello,
My team at Intel has recently opensourced a Mesos-related project: Orchestration-aware
Wo
t; Looking forward to meeting you all over Zoom next week,
>
> -Gastón
>
>> On Tue, Jul 17, 2018 at 2:55 AM Abel Souza wrote:
>> Thank you for setting this up Gaston,
>>
>> Would you mind giving us a brief of what you have in mind for discussion?
>>
>> T
Thank you for setting this up Gaston,
Would you mind giving us a brief of what you have in mind for discussion?
Thank you,
Abel
On 07/17/2018 10:52 AM, Matt Jarvis wrote:
That's great news Gaston ! Let me know if you need any help from the
Community team.
Matt
On Tue, 17 Jul 2018, 05:04 G
I’d be interested.
> On Jul 9, 2018, at 11:49 PM, Gastón Kleiman wrote:
>
> Hi all,
>
> I'm considering creating an "Operations Working Group".
>
> It could focus on making Mesos clusters easier to manage, deploy, and operate.
>
> Some possible topics that could be discussed in the working gr
on
multiple nodes: think about fault tolerance, where one needs replicas in case
of failures in the datacenter.
Best,
/Abel Souza
> On Jun 21, 2018, at 2:44 AM, Qian Zhang wrote:
>
> > It is possible to use multiple offers from a single agent node to launch a
> > task, but
Anyone that could suggest me anything? Is it a problem that could be
fixed by writing a custom framework?
/Abel
On 06/13/2018 06:05 AM, Abel Souza wrote:
Did you mean through ‘mesos-execute’ command or is it a Mesos general
behavior?
Best,
/Abel Souza
On Jun 13, 2018, at 02:04, Qian
Did you mean through ‘mesos-execute’ command or is it a Mesos general behavior?
Best,
/Abel Souza
> On Jun 13, 2018, at 02:04, Qian Zhang wrote:
>
> It is possible to use multiple offers from a single agent node to launch a
> task, but I do not think you can use multiple
if there is a way to enable the mesos-execute to
handle situations where multiple nodes are needed to satisfy a resource
request. If so, what would be needed?
Thank you,
/Abel Souza
14 matches
Mail list logo
