Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On 06/12/2017 02:17 PM, Edward Leafe wrote: On Jun 12, 2017, at 10:20 AM, Jay Pipes > wrote: The RP uuid is part of the provider: the compute node's uuid, and (after https://review.openstack.org/#/c/469147/ merges) the PCI device's uuid. So in

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Jun 12, 2017, at 10:20 AM, Jay Pipes wrote: >> The RP uuid is part of the provider: the compute node's uuid, and (after >> https://review.openstack.org/#/c/469147/ merges) the PCI device's uuid. So >> in the code that passes the PCI device information to the scheduler,

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On 06/09/2017 06:31 PM, Ed Leafe wrote: On Jun 9, 2017, at 4:35 PM, Jay Pipes wrote: We can declare that allocating for shared disk is fairly deterministic if we assume that any given compute node is only associated with one shared disk provider. a) we can't assume that

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Fri, 9 Jun 2017, Dan Smith wrote: In other words, I would expect to be able to explain the purpose of the scheduler as "applies nova-specific logic to the generic resources that placement says are _valid_, with the goal of determining which one is _best_". This sounds great as an

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Fri, 9 Jun 2017, Jay Pipes wrote: Sorry, been in a three-hour meeting. Comments inline... Thanks for getting to this, it's very helpful to me. * Part of the reason for having nested resource providers is because it can allow affinity/anti-affinity below the compute node (e.g.,

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

>> b) a compute node could very well have both local disk and shared >> disk. how would the placement API know which one to pick? This is a >> sorting/weighing decision and thus is something the scheduler is >> responsible for. > I remember having this discussion, and we concluded that a >

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Jun 9, 2017, at 4:35 PM, Jay Pipes wrote: >> We can declare that allocating for shared disk is fairly deterministic >> if we assume that any given compute node is only associated with one >> shared disk provider. > > a) we can't assume that > b) a compute node could very

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

Sorry, been in a three-hour meeting. Comments inline... On 06/06/2017 10:56 AM, Chris Dent wrote: On Mon, 5 Jun 2017, Ed Leafe wrote: One proposal is to essentially use the same logic in placement that was used to include that host in those matching the requirements. In other words, when it

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

>> My current feeling is that we got ourselves into our existing mess >> of ugly, convoluted code when we tried to add these complex >> relationships into the resource tracker and the scheduler. We set >> out to create the placement engine to bring some sanity back to how >> we think about things

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On 06/05/2017 05:22 PM, Ed Leafe wrote: Another proposal involved a change to how placement responds to the scheduler. Instead of just returning the UUIDs of the compute nodes that satisfy the required resources, it would include a whole bunch of additional information in a structured response.

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

Sorry for the top-post, but it seems that nobody has responded to this, and there are a lot of important questions that need answers. So I’m simply re-posting this so that we don’t get too ahead of ourselves, by planning implementations before we fully understand the problem and the

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Jun 7, 2017, at 1:44 PM, Mooney, Sean K > wrote: > [Mooney, Sean K] neutron will need to use nested resource providers to track > Network backend specific consumable resources in the future also. One example > is > is hardware

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Jun 7, 2017, at 1:44 PM, Mooney, Sean K > wrote: > [Mooney, Sean K] neutron will need to use nested resource providers to track > Network backend specific consumable resources in the future also. One example > is > is hardware

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Wednesday, June 7, 2017 6:47 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [nova][scheduler][placement] Allocating > Complex Resources > > On 06/07/2017 01:0

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On 06/07/2017 01:00 PM, Edward Leafe wrote: On Jun 6, 2017, at 9:56 AM, Chris Dent > wrote: For clarity and completeness in the discussion some questions for which we have explicit answers would be useful. Some of these may appear ignorant

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Jun 6, 2017, at 9:56 AM, Chris Dent wrote: > > For clarity and completeness in the discussion some questions for > which we have explicit answers would be useful. Some of these may > appear ignorant or obtuse and are mostly things we've been over > before. The goal is

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Mon, 5 Jun 2017, Ed Leafe wrote: One proposal is to essentially use the same logic in placement that was used to include that host in those matching the requirements. In other words, when it tries to allocate the amount of disk, it would determine that that host is in a shared storage

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

Le 06/06/2017 15:03, Edward Leafe a écrit : > On Jun 6, 2017, at 4:14 AM, Sylvain Bauza > wrote: >> >> The Plan A option you mention hides the complexity of the >> shared/non-shared logic but to the price that it would make scheduling >> decisions

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Jun 6, 2017, at 4:14 AM, Sylvain Bauza wrote: > > The Plan A option you mention hides the complexity of the > shared/non-shared logic but to the price that it would make scheduling > decisions on those criteries impossible unless you put > filtering/weighting logic into

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 05/06/2017 23:22, Ed Leafe a écrit : > We had a very lively discussion this morning during the Scheduler > subteam meeting, which was continued in a Google hangout. The > subject was how to handle claiming resources when the Resource > Provider