Magnum Team,
In our initial spec, we addressed the subject of resource scheduling. Our plan
was to begin with a naive scheduler that places resources on a specified Node
and can sequentially fill Nodes if one is not specified.
Magnum supports multiple conductor backends[1], one of which is our
On Sat, 2015-02-07 at 00:44 +, Adrian Otto wrote:
> Magnum Team,
>
> In our initial spec, we addressed the subject of resource scheduling. Our
> plan was to begin with a naive scheduler that places resources on a specified
> Node and can sequentially fill Nodes if one is not specified.
>
>
>
>
> 1) Cherry pick scheduler code from Nova, which already has a working a
> filter scheduler design.
> 2) Integrate swarmd to leverage its scheduler[2].
I see #2 as not an alternative but possibly an "also". Swarm uses the
Docker API, although they're only about 75% compatible at the moment.
I
ons)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Magnum] Scheduling for Magnum
1) Cherry pick scheduler code from Nova, which already has a working a filter
scheduler design.
2) Integrate swarmd to leverage its scheduler[2].
I see #2 as not an alternat
at 10:09 AM
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Subject: Re: [openstack-dev] [Magnum] Scheduling for Magnum
>
>>
>> 1) Cherry pick scheduler code from Nova, which already has a working a
>> filter scheduler design.
>>
feedback suggesting
our contributions are out of scope.
Adrian
Original message
From: "Steven Dake (stdake)"
Date:02/07/2015 10:27 AM (GMT-08:00)
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [Magnum] Schedulin
m: "Steven Dake (stdake)"
> Date:02/07/2015 10:27 AM (GMT-08:00)
> To: "OpenStack Development Mailing List (not for usage questions)"
> Subject: Re: [openstack-dev] [Magnum] Scheduling for Magnum
>
>
>
> From: Eric Windisch
> Reply-To
t 10:09 AM
To: "OpenStack Development Mailing List (not for usage questions)"
<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Magnum] Scheduling for Magnum
1) Cherry pick scheduler code from Nova, which already has a
working a filter
<
> openstack-dev@lists.openstack.org>
> Date: Saturday, February 7, 2015 at 10:09 AM
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [Magnum] Scheduling for Magnum
>
Adrian Otto wrote:
> [...]
> We have multiple options for solving this challenge. Here are a few:
>
> 1) Cherry pick scheduler code from Nova, which already has a working a filter
> scheduler design.
> 2) Integrate swarmd to leverage its scheduler[2].
> 3) Wait for the Gantt, when Nova Schedule
On 2/9/15, 3:02 AM, "Thierry Carrez" wrote:
>Adrian Otto wrote:
>> [...]
>> We have multiple options for solving this challenge. Here are a few:
>>
>> 1) Cherry pick scheduler code from Nova, which already has a working a
>>filter scheduler design.
>> 2) Integrate swarmd to leverage its schedu
)
Subject: Re: [openstack-dev] [Magnum] Scheduling for Magnum
Thanks Sylvain, we did not work out the API requirement till now but I think
the requirement should be similar with nova: we need select_destination to
select the best target host based on filters and weights.
There are also some
st (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Magnum] Scheduling for Magnum
I think Sylvain is getting at an important point. Magnum is trying to be as
agnostic as possible when it comes to selecting a backend. Because of that, I
think th
gt;
Date: Monday, February 9, 2015 at 10:38 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Magnum] Scheduling for Magnum
I think Sylvain is getting at an important point. Magnum is trying to
On Mon, Feb 9, 2015 at 6:00 AM, Steven Dake (stdake)
wrote:
>
>
> On 2/9/15, 3:02 AM, "Thierry Carrez" wrote:
>
> >Adrian Otto wrote:
> >> [...]
> >> We have multiple options for solving this challenge. Here are a few:
> >>
> >> 1) Cherry pick scheduler code from Nova, which already has a workin
ons)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Magnum] Scheduling for Magnum
On Mon, Feb 9, 2015 at 6:00 AM, Steven Dake (stdake)
mailto:std...@cisco.com>> wrote:
On 2/9/15, 3:02 AM, "Thierry Carrez"
mailto:thie...@openstack.org>&
, 2015 at 6:41 PM
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [Magnum] Scheduling for Magnum
>
>
>
> On Mon, Feb 9, 2015 at 6:00 AM, Steven Dake (stdake)
> wrote:
>
&
ons)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Magnum] Scheduling for Magnum
Steve,
So you mean we should focus on docker and k8s scheduler? I was a bit confused,
why do we need to care k8s? As the k8s cluster was created by heat and once the
k8s was crea
ly-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: Monday, February 9, 2015 at 11:31 PM
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
penStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, February 9, 2015 at 11:31 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [op
OpenStack Development Mailing List (not for usage questions)"
>>
>> Date: Monday, February 9, 2015 at 11:31 PM
>> To: "OpenStack Development Mailing List (not for usage questions)" <
>> openstack-dev@lists.openstack.org>
>> Subject: Re: [openstack-dev
21 matches
Mail list logo
