@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
1) Cherry pick scheduler code from Nova, which already has a working
(not for usage questions)
openstack-dev@lists.openstack.orgmailto: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
Reply-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
Subject: Re: [openstack-dev] [Magnum
Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto: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
, February 7, 2015 at 10:09 AM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
mailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Magnum] Scheduling for Magnum
1) Cherry pick scheduler code from Nova, which already
@lists.openstack.orgmailto: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 created, the k8s has its
To: OpenStack Development Mailing List (not for usage questions)
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
)
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
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) std...@cisco.com
wrote:
On 2/9/15, 3:02 AM, Thierry Carrez thie
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 Scheduler to
On 2/9/15, 3:02 AM, Thierry Carrez thie...@openstack.org 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
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, February 9, 2015 at 10:38 AM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Magnum] Scheduling for Magnum
I think Sylvain
On Mon, Feb 9, 2015 at 6:00 AM, Steven Dake (stdake) std...@cisco.com
wrote:
On 2/9/15, 3:02 AM, Thierry Carrez thie...@openstack.org wrote:
Adrian Otto wrote:
[...]
We have multiple options for solving this challenge. Here are a few:
1) Cherry pick scheduler code from Nova, which
(not for usage questions)
openstack-dev@lists.openstack.orgmailto: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)
std...@cisco.commailto:std...@cisco.com wrote:
On 2/9/15, 3:02 AM, Thierry Carrez
(not for usage questions)
openstack-dev@lists.openstack.orgmailto: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
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.
: 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
1) Cherry pick scheduler code from Nova, which already has a working a
filter scheduler design
)
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 e...@windisch.us
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev
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] Scheduling for Magnum
From: Eric
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.
Magnum
20 matches
Mail list logo
