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) ? [cid:image003.png at 01CF79AE.740B1EF0] Thanks & regards, Keshava.A -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140527/ec80e10e/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.emz Type: application/octet-stream Size: 16132 bytes Desc: image001.emz URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140527/ec80e10e/attachment-0002.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: oledata.mso Type: application/octet-stream Size: 14412 bytes Desc: oledata.mso URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140527/ec80e10e/attachment-0003.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 30014 bytes Desc: image003.png URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140527/ec80e10e/attachment-0001.png>
