Re: [openstack-dev] [nova] [placement] aggregates associated with multiple resource providers

2016-05-31 Thread Chris Dent
On Tue, 31 May 2016, Jay Pipes wrote: So this seem rather fragile and pretty user-hostile. We're creating an opportunity for people to easily replace their existing bad tracking of disk usage with a different style of bad tracking of disk usage. I'm not clear why the new way of tracking disk

Re: [openstack-dev] [nova] [placement] aggregates associated with multiple resource providers

2016-05-31 Thread Jay Pipes
On 05/31/2016 01:06 PM, Chris Dent wrote: On Tue, 31 May 2016, Jay Pipes wrote: Kinda. What the compute node needs is an InventoryList object containing all inventory records for all resource classes both local to it as well as associated to it via any aggregate-resource-pool mapping. Okay,

Re: [openstack-dev] [nova] [placement] aggregates associated with multiple resource providers

2016-05-31 Thread Chris Dent
On Tue, 31 May 2016, Jay Pipes wrote: Kinda. What the compute node needs is an InventoryList object containing all inventory records for all resource classes both local to it as well as associated to it via any aggregate-resource-pool mapping. Okay, that mostly makes sense. A bit different

Re: [openstack-dev] [nova] [placement] aggregates associated with multiple resource providers

2016-05-31 Thread Jay Pipes
On 05/29/2016 06:19 PM, Chris Dent wrote: This gets a bit complex (to me) but: The idea for step 4 is that the resource tracker will be modified such that: * if the compute node being claimed by an instance is a member of some aggregates * and one of those aggregates is associated with a

Re: [openstack-dev] [nova] [placement] aggregates associated with multiple resource providers

2016-05-31 Thread Jay Pipes
On 05/30/2016 11:22 PM, Cheng, Yingxin wrote: Hi, cdent: This problem arises because the RT(resource tracker) only knows to consume the DISK resource in its host, but it still doesn’t know exactly which resource provider to place the consumption. That is to say, the RT still needs to *find* the

Re: [openstack-dev] [nova] [placement] aggregates associated with multiple resource providers

2016-05-30 Thread Cheng, Yingxin
Hi, cdent: This problem arises because the RT(resource tracker) only knows to consume the DISK resource in its host, but it still doesn’t know exactly which resource provider to place the consumption. That is to say, the RT still needs to *find* the correct resource provider in the step 4. The

[openstack-dev] [nova] [placement] aggregates associated with multiple resource providers

2016-05-29 Thread Chris Dent
I'm currently doing some thinking on step 4 ("Modify resource tracker to pull information on aggregates the compute node is associated with and the resource pools available for those aggregatesa.") of the work items for the generic resource pools spec[1] and I've run into a brain teaser that I