<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 04/15/2014 06:03 AM, Jiangying
      (Jenny) wrote:<br>
    </div>
    <blockquote
cite="mid:4A62CE9483C76D4C81CAFA0F0A4CBD3B4C5B60E5@SZXEMA504-MBX.china.huawei.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:宋体;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:宋体;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:"\@宋体";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:宋体;}
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;}
span.EmailStyle17
        {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:612.0pt 792.0pt;
        margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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.5pt;font-family:"Calibri","sans-serif";color:#1F497D"
            lang="EN-US">Sorry, I’m not quite clear about it yet.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D"
            lang="EN-US">I’m trying to find a way that heat controls the
            flow but not the nova scheduler.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D"
            lang="EN-US"><o:p> </o:p></span></p>
      </div>
    </blockquote>
    Heat doesn't control flow.  Heat expects a scheduler is built into
    whatever service it is consuming for resource management, if the
    resource is constrained for some reason (such as limited memory,
    disk, cpu resources available for consumption).  This is why
    something like a storage system (cinder) has a scheduler, and Heat
    does not.<br>
    <br>
    It makes zero sense to add scheduling to Heat - since the projects
    that Heat consumes are in much better position to make decisions
    about which resources get scheduled when and where.<br>
    <br>
    Regards<br>
    -steve<br>
    <br>
    <blockquote
cite="mid:4A62CE9483C76D4C81CAFA0F0A4CBD3B4C5B60E5@SZXEMA504-MBX.china.huawei.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><b><span style="font-size:10.0pt">发件人<span
                lang="EN-US">:</span></span></b><span
            style="font-size:10.0pt" lang="EN-US"> Henrique Truta
            [<a class="moz-txt-link-freetext" href="mailto:henriquecostatruta@gmail.com">mailto:henriquecostatruta@gmail.com</a>]
            <br>
          </span><b><span style="font-size:10.0pt">发送时间<span
                lang="EN-US">:</span></span></b><span
            style="font-size:10.0pt" lang="EN-US"> 2014</span><span
            style="font-size:10.0pt">年<span lang="EN-US">4</span>月<span
              lang="EN-US">14</span>日<span lang="EN-US"> 21:39<br>
            </span><b>收件人<span lang="EN-US">:</span></b><span
              lang="EN-US"> OpenStack Development Mailing List (not for
              usage questions)<br>
            </span><b>主题<span lang="EN-US">:</span></b><span
              lang="EN-US"> Re: [openstack-dev] [heat][nova]dynamic
              scheduling<o:p></o:p></span></span></p>
        <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
        <div>
          <div>
            <div>
              <div>
                <p class="MsoNormal" style="margin-bottom:12.0pt"><span
                    lang="EN-US">Hello!<o:p></o:p></span></p>
              </div>
              <p class="MsoNormal" style="margin-bottom:12.0pt"><span
                  lang="EN-US">I'm currently investigating both of these
                  features you have mentioned, specifically on the
                  NEAT[1] and GANTT[2] projects, as you might see on the
                  last week discussion.
                  <o:p></o:p></span></p>
            </div>
            <p class="MsoNormal" style="margin-bottom:12.0pt"><span
                lang="EN-US">Do you have any further ideas about how and
                why this would work with Heat?<o:p></o:p></span></p>
          </div>
          <div>
            <p class="MsoNormal" style="margin-bottom:12.0pt"><span
                lang="EN-US">Thanks,<o:p></o:p></span></p>
          </div>
          <div>
            <p class="MsoNormal"><span lang="EN-US">Henrique<o:p></o:p></span></p>
          </div>
          <div>
            <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
          </div>
          <p class="MsoNormal"><span lang="EN-US">[1] <a
                moz-do-not-send="true" href="http://openstack-neat.org/">
                http://openstack-neat.org/</a><br>
              [2] <a moz-do-not-send="true"
                href="https://github.com/openstack/gantt">https://github.com/openstack/gantt</a><o:p></o:p></span></p>
          <div>
            <p class="MsoNormal" style="margin-bottom:12.0pt"><span
                lang="EN-US"><o:p> </o:p></span></p>
            <div>
              <p class="MsoNormal"><span lang="EN-US">2014-04-13 22:53
                  GMT-03:00 Jiangying (Jenny) <<a
                    moz-do-not-send="true"
                    href="mailto:jenny.jiangying@huawei.com"
                    target="_blank">jenny.jiangying@huawei.com</a>>:<o:p></o:p></span></p>
              <div>
                <div>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                      style="font-family:"Courier New""
                      lang="EN-US">Hi,
                    </span><span lang="EN-US"><o:p></o:p></span></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                      style="font-family:"Courier New""
                      lang="EN-US">there has been a heated discussion
                      about dynamic scheduling last week.(<a
                        moz-do-not-send="true"
href="http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg21644.html"
                        target="_blank">http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg21644.html</a>)</span><span
                      lang="EN-US"><o:p></o:p></span></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                      style="font-family:"Courier New""
                      lang="EN-US">I am also interested in this topic.
                      We believe that dynamic scheduling consists of two
                      parts: balancing computing capacity and optimizing
                      power consumption.</span><span lang="EN-US"><o:p></o:p></span></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                      style="font-family:"Courier New""
                      lang="EN-US">For balancing computing capacity, the
                      ceilometer periodically monitors distribution and
                      usage of CPU and memory resources for hosts and
                      virtual machines. Based on the information, the
                      scheduler calculates the current system standard
                      deviation metric and determines the system
                      imbalance by comparing it to the target. To
                      resolve the imbalance, the scheduler gives the
                      suitable virtual machine migration suggestions to
                      nova. In this way, the dynamic scheduling achieves
                      higher consolidation ratios and deliver optimized
                      performance for the virtual machines.</span><span
                      lang="EN-US"><o:p></o:p></span></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                      style="font-family:"Courier New""
                      lang="EN-US">For optimizing power consumption, we
                      attempt to keep the resource utilization of each
                      host within a specified target range. The
                      scheduler evaluates if the goal can be reached by
                      balancing the system workloads. If the resource
                      utilization of a host remains below the target,
                      the scheduler calls nova to power off some hosts.
                      Conversely the scheduler powers on hosts to absorb
                      the additional workloads. Thus optimizing power
                      consumption offers an optimum mix of resource
                      availability and power savings.</span><span
                      lang="EN-US"><o:p></o:p></span></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                      style="font-family:"Courier New""
                      lang="EN-US">As Chen CH Ji said, “nova is a cloud
                      solution that aim to control virtual / real
                      machine lifecycle management the dynamic
                      scheduling mechanism is something like
                      optimization of the cloud resource”. We
                      think implementing the dynamic scheduling with
                      heat may be a good attempt.</span><span
                      lang="EN-US"><o:p></o:p></span></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                      style="font-family:"Courier New""
                      lang="EN-US">Do you have any comments?</span><span
                      lang="EN-US"><o:p></o:p></span></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                      style="font-family:"Courier New""
                      lang="EN-US">Thanks,</span><span lang="EN-US"><o:p></o:p></span></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                      style="font-family:"Courier New""
                      lang="EN-US">Jenny</span><span lang="EN-US"><o:p></o:p></span></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                      lang="EN-US"> <o:p></o:p></span></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""
                      lang="EN-US"> </span><span lang="EN-US"><o:p></o:p></span></p>
                </div>
              </div>
              <p class="MsoNormal" style="margin-bottom:12.0pt"><span
                  lang="EN-US"><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><o:p></o:p></span></p>
            </div>
            <div>
              <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
            </div>
          </div>
        </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>