<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Le 30/05/2014 10:06, jcsf a écrit :<br>
</div>
<blockquote cite="mid:02b301cf7bde$1ce06d60$56a14820$@gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Carl,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></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?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">John</span></p>
</div>
</blockquote>
<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>
<blockquote cite="mid:02b301cf7bde$1ce06d60$56a14820$@gmail.com"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
name="_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></a></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 class="moz-txt-link-freetext" href="mailto:carl@ecbaldwin.net">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 class="moz-txt-link-abbreviated" href="mailto:jcsf31459@gmail.com">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 ?<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Keshava,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></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?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></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.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></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.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Carl<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></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:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D">Hi,</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D">Motivation behind this
requirement is “ to achieve VM prefix aggregation
using routing protocol ( BGP/OSPF)”.</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D">So that prefix advertised from
cloud to upstream will be aggregated.</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D">I do not have idea how the
current scheduler is implemented. </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D">But schedule to maintain some
kind of the ‘Network to Node mapping to VM” ..</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D">It will be great help us from
routing side if this is available in the
infrastructure.</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D">I am available for
review/technical discussion/meeting. </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D">Thanks & regards,</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D">Keshava.A</span><o:p></o:p></p>
</div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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 ?<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white"><span
style="color:#1F497D">Hi keshava,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white"><span
style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;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><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white"><span
style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white"><span
style="color:#1F497D">There are a number of
uses cases for this. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white"><span
style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white"><span
style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white"><span
style="color:#1F497D">John. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white"><span
style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:white"><span
style="color:#1F497D">Sent from my
smartphone.</span><o:p></o:p></p>
</div>
<table class="MsoNormalTable"
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"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
</div>
</div>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Hi,<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I
have one of the basic question about the Nova
Scheduler in the following below scenario.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Whenever
a new VM to be hosted is there any consideration
of network attributes ? <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;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.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;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.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-indent:.5in"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">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 ) ? <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">This
is required to achieve prefix/route aggregation
and to avoid network broadcast (incase if they
are scattered across different TOR/Switch) ? <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><img
id="_x0000_i1025"
src="cid:part6.03010909.08070602@redhat.com"
border="0" height="727" width="628"><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Thanks
& regards,<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Keshava.A<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>