<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Le 30/05/2014 11:11, Mathieu Rohon a
écrit :<br>
</div>
<blockquote
cite="mid:CAAfiWQqQmtC1p-NcZ3Bbo8v4DG1oMzhck9jGor-Eu5afvURdRg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>I'm also very interested in scheduling VMs with Network
requirement. This seems to be in the scope of NFV workgroup
[1].<br>
</div>
For instance, I think that scheduling should take into account
bandwith/QoS requirement for a VM, or specific Nic requirement
for a VM (availability of a SRIOV Vif on compute nodes).<br>
<br>
</div>
To do this, it seems that Neutron should report its available
capacity (Vif availability, bandwith availability) for each
compute node, and Gantt should take this reporting into account
for scheduling.<br>
<div>
<div>
<br>
[1]<a moz-do-not-send="true"
href="https://etherpad.openstack.org/p/juno-nfv-bof">https://etherpad.openstack.org/p/juno-nfv-bof</a><br>
<br>
</div>
</div>
</div>
<div class="gmail_extra"><br>
</div>
</blockquote>
<br>
I don't have a clear picture yet on all the stakeholders, but the
goal of Gantt is to deal with heterogenous resources like Nova
compute nodes or others.<br>
At the moment, the idea is to paint a clear line in between Nova and
the scheduler, so we are defining an interface
(update_resource_stats) that anyone could call.<br>
In other words, mid-term it would not be mandatory to report the
stats to compute nodes for updating Gantt resources, Neutron could
directly update the resources thanks to Gantt API.<br>
<br>
-Sylvain<br>
<br>
<blockquote
cite="mid:CAAfiWQqQmtC1p-NcZ3Bbo8v4DG1oMzhck9jGor-Eu5afvURdRg@mail.gmail.com"
type="cite">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, May 30, 2014 at 10:47 AM, jcsf
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jcsf31459@gmail.com" target="_blank">jcsf31459@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Sylvain,</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thank
you for the background – I will educate myself on
this work.</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks,</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">John</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
name="1464c53e7d036c54__MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></a></p>
<div>
<div style="border:none;border-top:solid #b5c4df
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
Sylvain Bauza [mailto:<a moz-do-not-send="true"
href="mailto:sbauza@redhat.com"
target="_blank">sbauza@redhat.com</a>] <br>
<b>Sent:</b> Friday, May 30, 2014 11:31 AM</span></p>
<div class=""><br>
<b>To:</b> OpenStack Development Mailing List (not
for usage questions)<br>
</div>
<b>Cc:</b> jcsf; 'Carl Baldwin'; 'A, Keshava'
<div>
<div class="h5">
<br>
<b>Subject:</b> Re: [openstack-dev]
[neutron][L3] VM Scheduling v/s Network as input
any consideration ?</div>
</div>
</div>
</div>
<div>
<div class="h5">
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">
Le 30/05/2014 10:06, jcsf a écrit :</p>
</div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Carl,</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">A
new routing protocol is certainly of great
interest. Are you working with IETF or can
you share more here?</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">WRT:Nova
Schedule - There still are requirements for
the Schedule to taking into consideration
network as a resource. My focus is to figure
out how to add network capabilities to the
Scheduler’s algorithm while still maintaining
clean separation of concerns between Nova and
Neutron. We wouldn’t want to get back into
the nova-network situation. </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">John</span></p>
</blockquote>
<p class="MsoNormal"><br>
As it was previously mentioned, there are already
different kinds of grouping for VMs in Nova that
probably don't require to add new network-specific
features :<br>
- aggregates and user-facing AZs allow to define
a common set of capabilities for physical hosts
upon which you can boot VMs<br>
- ServerGroups with Affinity/Anti-Affinity
filters allow you to enforce a certain level of
network proximity for VMs<br>
<br>
<br>
Once that said, there is also another effort of
forking the Nova Scheduler code into a separate
project so that cross-projects scheduling could
happen (and consequently Neutron could use it).
This project is planned to be delivered by K
release, and will be called Gantt.<br>
<br>
<br>
So, could you please mention which features do you
need for Nova, so we could discuss that here
before issuing a spec ?<br>
<br>
-Sylvain<br>
<br>
<br>
<br>
<br>
<br>
</p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
Carl Baldwin [<a moz-do-not-send="true"
href="mailto:carl@ecbaldwin.net"
target="_blank">mailto:carl@ecbaldwin.net</a>]
<br>
<b>Sent:</b> Friday, May 30, 2014 12:05 AM<br>
<b>To:</b> A, Keshava<br>
<b>Cc:</b> <a moz-do-not-send="true"
href="mailto:jcsf31459@gmail.com"
target="_blank">jcsf31459@gmail.com</a>;
Armando M.; OpenStack Development Mailing List
(not for usage questions); Kyle Mestery<br>
<b>Subject:</b> Re: [openstack-dev]
[neutron][L3] VM Scheduling v/s Network as input
any consideration ?</span></p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Keshava,</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">How much of a problem is
routing prefix fragmentation for you?
Fragmentation causes routing table bloat and
may reduce the performance of the routing
table. It also increases the amount of
information traded by the routing protocol.
Which aspect(s) is (are) affecting you? Can
you quantify this effect?</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">A major motivation for my
interest in employing a dynamic routing
protocol within a datacenter is to enable IP
mobility so that I don't need to worry about
doing things like scheduling instances based
on their IP addresses. Also, I believe that
it can make floating ips more "floaty" so that
they can cross network boundaries without
having to statically configure routers.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">To get this mobility, it
seems inevitable to accept the fragmentation
in the routing prefixes. This level of
fragmentation would be contained to a
well-defined scope, like within a datacenter.
Is it your opinion that trading off
fragmentation for mobility a bad trade-off?
Maybe it depends on the capabilities of the
TOR switches and routers that you have. Maybe
others can chime in here.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Carl</p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> </p>
<div>
<p class="MsoNormal">On Wed, May 28, 2014 at
10:11 PM, A, Keshava <<a
moz-do-not-send="true"
href="mailto:keshava.a@hp.com"
target="_blank">keshava.a@hp.com</a>>
wrote:</p>
<div>
<div>
<p class="MsoNormal"><span
style="color:#1f497d">Hi,</span></p>
<p class="MsoNormal"><span
style="color:#1f497d">Motivation behind
this requirement is “ to achieve VM
prefix aggregation using routing
protocol ( BGP/OSPF)”.</span></p>
<p class="MsoNormal"><span
style="color:#1f497d">So that prefix
advertised from cloud to upstream will
be aggregated.</span></p>
<p class="MsoNormal"><span
style="color:#1f497d"> </span></p>
<p class="MsoNormal">
<span style="color:#1f497d">I do not have
idea how the current scheduler is
implemented. </span></p>
<p class="MsoNormal"><span
style="color:#1f497d">But schedule to
maintain some kind of the ‘Network to
Node mapping to VM” ..</span></p>
<p class="MsoNormal"><span
style="color:#1f497d">Based on that
mapping to if any new VM getting hosted
to give prefix in those Nodes based one
input preference.</span></p>
<p class="MsoNormal"><span
style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="color:#1f497d">It will be great
help us from routing side if this is
available in the infrastructure.</span></p>
<p class="MsoNormal"><span
style="color:#1f497d">I am available for
review/technical discussion/meeting. </span></p>
<p class="MsoNormal"><span
style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span
style="color:#1f497d"> </span></p>
<div>
<p class="MsoNormal"><span
style="color:#1f497d">Thanks &
regards,</span></p>
<p class="MsoNormal"><span
style="color:#1f497d">Keshava.A</span></p>
</div>
<p class="MsoNormal"><span
style="color:#1f497d"> </span></p>
<div>
<div style="border:none;border-top:solid
#e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> <a
moz-do-not-send="true"
href="mailto:jcsf31459@gmail.com"
target="_blank">jcsf31459@gmail.com</a>
[mailto:<a moz-do-not-send="true"
href="mailto:jcsf31459@gmail.com"
target="_blank">jcsf31459@gmail.com</a>]
<br>
<b>Sent:</b> Thursday, May 29, 2014
9:14 AM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>;
Carl Baldwin; Kyle Mestery; OpenStack
Development Mailing List (not for
usage questions)<br>
<b>Subject:</b> Re: [openstack-dev]
[neutron][L3] VM Scheduling v/s
Network as input any consideration ?</p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"
style="background:white"><span
style="color:#1f497d">Hi keshava,</span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white">
<span style="color:#1f497d"> </span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="color:#1f497d">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. </span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="color:#1f497d"> </span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="color:#1f497d">There are a
number of uses cases for this. </span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="color:#1f497d"> </span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="color:#1f497d"> </span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="color:#1f497d">John. </span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="color:#1f497d"> </span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="color:#1f497d">Sent from my
smartphone.</span></p>
</div>
<table
style="width:100.0%;background:white;border-spacing:0px"
border="0" cellpadding="0"
cellspacing="3" width="100%">
<tbody>
<tr>
<td style="padding:.75pt .75pt
.75pt
.75pt;font-size:initial;text-align:initial">
<div
style="border:none;border-top:solid
#b5c4df 1.0pt;padding:3.0pt
0in 0in 0in">
<div>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:
</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">A,
Keshava</span></p>
</div>
<div>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Sent:
</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Tuesday,
May 27, 2014 10:58 AM</span></p>
</div>
<div>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">To:
</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Carl
Baldwin; Kyle Mestery;
OpenStack Development
Mailing List (not for
usage questions)</span></p>
</div>
<div>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Reply
To: </span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">OpenStack
Development Mailing List
(not for usage
questions)</span></p>
</div>
<div>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Subject:
</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">[openstack-dev]
[neutron][L3] VM
Scheduling v/s Network
as input any
consideration ?</span></p>
</div>
</div>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Hi,</p>
<p class="MsoNormal">I have one of the
basic question about the Nova
Scheduler in the following below
scenario.</p>
<p class="MsoNormal">Whenever a new VM
to be hosted is there any
consideration of network attributes
? </p>
<p class="MsoNormal"
style="text-indent:.5in">Example let
us say all the VMs with 10.1.x is
under TOR-1, and 20.1.xy are under
TOR-2.</p>
<p class="MsoNormal"
style="text-indent:.5in">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.</p>
<p class="MsoNormal"
style="text-indent:.5in">
</p>
<p class="MsoNormal">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 ) ? </p>
<p class="MsoNormal">This is required
to achieve prefix/route aggregation
and to avoid network broadcast
(incase if they are scattered across
different TOR/Switch) ? </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><img
src="cid:part11.01000209.01070703@redhat.com"
border="0" height="727"
width="628"></p>
<p class="MsoNormal">
</p>
<p class="MsoNormal">Thanks &
regards,</p>
<p class="MsoNormal">Keshava.A</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"
style="margin-bottom:12.0pt"> </p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal"><br>
<br>
<br>
</p>
<pre>_______________________________________________</pre>
<pre>OpenStack-dev mailing list</pre>
<pre><a moz-do-not-send="true" href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a></pre>
<pre><a moz-do-not-send="true" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></pre>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>