Re: [openstack-dev] [neutron][L3] VM Scheduling v/s Network as input any consideration ?

[jcsf31459]

Yes, agree on the use case.   I suggest we introduce a series of callbacks and up calls to the scheduler so that we don't bloat the ‎scheduler with information outside of its domain.      Callbacks and up calls can be used to call external systems that keep detailed topology information.    We can also work on the latter together if you wish.   We have a topology system already.   I've been waiting for someone to work with this on.   John Sent from my BlackBerry 10 smartphone. From: A, Keshava Sent: Thursday, May 29, 2014 7:13 AM To: jcsf31...@gmail.com Cc: Armando M.; OpenStack Development Mailing List (not for usage questions); Carl Baldwin; Kyle Mestery Subject: RE: [openstack-dev] [neutron][L3] VM Scheduling v/s Network as input any consideration ? Hi, Motivation behind this  requirement is “ to achieve VM prefix aggregation  using routing protocol ( BGP/OSPF)”. So that prefix advertised from cloud to upstream will be aggregated.   I do not have idea how the current scheduler is implemented. But schedule to  maintain some kind of the ‘Network to Node mapping to VM” .. Based on that mapping to if any new VM  getting hosted to give prefix in those Nodes based one input preference.   It will be great help us from routing side if this is available in the infrastructure. I am available for review/technical discussion/meeting.     Thanks & regards, Keshava.A   From: jcsf31...@gmail.com [mailto:jcsf31...@gmail.com] Sent: Thursday, May 29, 2014 9:14 AM To: openstack-dev@lists.openstack.org; Carl Baldwin; Kyle Mestery; OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron][L3] VM Scheduling v/s Network as input any consideration ?   Hi keshava,   This is an area that I am interested in.   I'd be happy to collaborate with you on a blueprint.    This would require enhancements to the scheduler as you suggested.      There are a number of uses cases for this.       ‎John.    Sent from my  smartphone. From: A, Keshava‎ Sent: Tuesday, May 27, 2014 10:58 AM To: Carl Baldwin; Kyle Mestery; OpenStack Development Mailing List (not for usage questions) Reply To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron][L3] VM Scheduling v/s Network as input any consideration ?   Hi, I have one of the basic question about the Nova Scheduler in the following below scenario. Whenever a new VM to be hosted is there any consideration of network attributes ? Example let us say all the VMs with 10.1.x is under TOR-1, and 20.1.xy are under TOR-2. A new CN nodes is inserted under TOR-2 and at same time a new  tenant VM needs to be  hosted for 10.1.xa network.   Then is it possible to mandate the new VM(10.1.xa)   to hosted under TOR-1 instead of it got scheduled under TOR-2 ( where there CN-23 is completely free from resource perspective ) ? This is required to achieve prefix/route aggregation and to avoid network broadcast (incase if they are scattered across different TOR/Switch) ?         Thanks & regards, Keshava.A

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev