<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 14:44, CARVER, PAUL a
écrit :<br>
</div>
<blockquote
cite="mid:A81F249089B6C7479786834457908C600AD29FBC@MISOUT7MSGUSR9N.ITServices.sbc.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
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.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{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:10.0pt;font-family:"Tahoma","sans-serif"">Mathieu
Rohon wrote:<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>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">></span>I'm
also very interested in scheduling VMs with Network
requirement. This seems to be in the scope of NFV
workgroup
<span style="color:#1F497D">></span>[1].<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="color:#1F497D">></span>For instance, I think
that scheduling should take into account bandwith/QoS
requirement for a VM, or specific Nic
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">This
falls in my area of interest as well. We’re working on
making network quality of service guarantees by means of
a combination of DSCP marking with a reservation
database and separate hardware queues in physical
network switches in order to ensure that the
reservations granted don’t exceed the wire speed of the
switches. Right now the only option if the total of
requested reservations would exceed the wire speed of
the switches is to deny reservations on the basis of
“first come, first served” and “last come, doesn’t get
served”, in other words simply issuing a failure
response at reservation time to any tenants who attempt
to make reservations after a particular switch port is
maxed out (from a reservation perspective, not
necessarily maxed out from an actual utilization
perspective at any given moment.)</span></p>
</div>
</div>
</div>
</blockquote>
<br>
Hi Paul,<br>
<br>
I don't exactly know your needs, neither your current state of work
regarding the implementation of a reservation database, but please
note that there is a Stackforge project aiming to provide this for
OpenStack natively :<br>
<br>
<a class="moz-txt-link-freetext" href="http://wiki.openstack.org/wiki/Blazar">http://wiki.openstack.org/wiki/Blazar</a> (formerly Climate).<br>
<br>
<br>
During last Juno summit, some discussions in Nova were related to
having a reservation system in place, and the agreement was to take
a look at Climate/Blazar to see if it's a good fit.<br>
<br>
I think it would be valuable for both you and Climate folks (whose
I'm in as core reviewer) to see if we can join efforts to address
your requirements with Blazar so you wouldn't have to do all the
things.<br>
<br>
There is a weekly meeting today at 3pm UTC in #openstack-meeting for
Blazar team. If you have time, just jump in and address your
questions here, that would be a good starting point.<br>
<br>
<br>
<br>
<blockquote
cite="mid:A81F249089B6C7479786834457908C600AD29FBC@MISOUT7MSGUSR9N.ITServices.sbc.com"
type="cite">
<div class="WordSection1">
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">However,
with the element of chance in VM scheduling to compute
node, it’s possible that a tenant could get a deny
response from the reservation server because their VM
landed on a particularly reservation heavy rack. If
their VM happened to land on a compute node in a
different rack then there might well be plenty of excess
bandwidth on that rack’s uplink. But our current
implementation has no way to tell Nova or the tenant
that a reservation that was denied could have been
granted if the VM were relocated to a less network
overloaded rack.<o:p></o:p></span></p>
</div>
</div>
<div>
</div>
</div>
</blockquote>
<br>
IMHO, this strategy requires both a reservation system (in my
opinion, Blazar), a resource placement system (Gantt) and possibly
some AMQP notifications which would go thru the queue.<br>
That's something I also have in my scope, we can discuss that
whenever you want.<br>
<br>
-Sylvain<br>
<br>
<br>
<blockquote
cite="mid:A81F249089B6C7479786834457908C600AD29FBC@MISOUT7MSGUSR9N.ITServices.sbc.com"
type="cite">
<div class="WordSection1">
<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>