Open Stack

There is a project, gantt, to split out the scheduler but it will be a while before it is capable of making cross project scheduling decisions.  I'll be happy if we just have the current Nova scheduler capabilities available in a separate Gantt scheduler by the Kilo release, more advanced capabilities will have to come later.

As suggested, using aggregates would be your best option for now.

--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786

-----Original Message-----
From: gustavo panizzo (gfa) [mailto:gfa at zumbi.com.ar] 
Sent: Tuesday, September 16, 2014 12:33 AM
To: Chris; 'Jay Pipes'; openstack at lists.openstack.org
Subject: Re: [Openstack] Scheduler try and error with compute nodes in different subnets/physnet's



On 09/16/2014 02:07 PM, Chris wrote:
> Hello Jay,
> As far as I understand each compute node sends the current available 
> resources to the management node.

yes, but nova does not know the matching between the subnet and the physical port, neutron knows that.

as Jay previously told you, the only thing you can do now is to use host aggregates.

i think there is a project to split the scheduler from nova to make it a service, it could take the information from different services (nova, neutron, cinder) to make the decision


> This could also include the physnet, so the scheduler ignore the not 
> matching compute nodes. Or the compute nodes sends the physnet at the 
> first registration in the management node.
> But to be honest I not have the deep insights to make a proper 
> suggestion here.
>
> -----Original Message-----
> From: Jay Pipes [mailto:jaypipes at gmail.com]
> Sent: Tuesday, September 16, 2014 11:54
> To: openstack at lists.openstack.org
> Subject: Re: [Openstack] Scheduler try and error with compute nodes in 
> different subnets/physnet's
>
> On 09/15/2014 11:26 PM, Chris wrote:
>> Hello,
>>
>> We have a OpenStack setup with a large number of compute nodes spread 
>> in different subnets which are represented as different physnet's in
> OpenStack.
>>
>> When we start an instance we see that the scheduler choose a compute 
>> node and tries to spawn the instance, then it sees its not in the 
>> right physnet and choose a different compute node.
>
> How would the scheduler know which compute node is "in the right physnet"?
> In other words, when an instance is launched, how does the scheduler 
> know what is the "correct physnet" for that type of instance?
>
>> In our case this takes around 4 - 10 attempts. All this attempts 
>> counts for the "scheduler_max_attempts" which default value is 3. We 
>> increase this value to prevent errors, but it's still very 
>> inefficient especially in a large environment.
>>
>> Is there a way that the scheduler knows the physnet/subnet position 
>> of the compute nodes before the instance tries to spawn?
>
>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>

--
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack at lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack