<br><br><div class="gmail_quote">On Tue, Dec 18, 2012 at 4:51 PM, gong yong sheng <span dir="ltr"><<a href="mailto:gongysh@linux.vnet.ibm.com" target="_blank">gongysh@linux.vnet.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div>Eugene:<br>
      The BP name is a little  confusing. It is not all about scheduler.
      But it needs us to have a scheduler.<br>
      The BP spec in <a rel="nofollow" href="https://docs.google.com/presentation/d/1eiBx6roRyk-mUfgBfJZUtEjEGbgTB5Gf4r7varAyDpg/edit" style="background-image:url();color:rgb(0,51,170);text-decoration:none;padding:0px 0px 6px 18px;line-height:18px;background-repeat:no-repeat no-repeat" target="_blank">Read the full
        specification</a> is old. But I cannot change the URL. the new
      Spec is '
      
      <a rel="nofollow" href="https://docs.google.com/document/d/1TJlW0_tMpeENA_ia38fvRu7ioKRt9fsWXBjivwd1mMw/edit" style="text-indent:0px;letter-spacing:normal;max-width:60em;font-variant:normal;text-align:left;font-style:normal;font-weight:normal;line-height:18px;color:rgb(0,51,170);text-transform:none;font-size:12px;white-space:normal;text-decoration:none;font-family:sans-serif;word-spacing:0px" target="_blank">https:/<u></u>/docs.google.<u></u>com/document/<u></u>d/1TJlW0_<u></u>tMpeENA_<u></u>ia38fvRu7ioKRt9<u></u>fsWXBjivwd1mMw/<u></u>edit</a>'<br>

</div></div></blockquote><div><br></div><div>Yong, you should be able to rename the blueprint URL using the "edit details" link: <a href="https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler/+edit">https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler/+edit</a></div>

<div><br></div><div>dan</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><div>
      <br>
      I have a patch for this BP:
      
      <a href="https://review.openstack.org/#/c/18216/" target="_blank">https://review.openstack.org/#/c/18216/</a><br>
      <br>
      please see the schedule_xxxx methods in this file:<br>
       
      
      <a href="https://review.openstack.org/#/c/18216/3/quantum/db/multipleagents_db.py" target="_blank">https://review.openstack.org/#/c/18216/3/quantum/db/multipleagents_db.py</a><br>
      <br>
      I composed a draft admin guide (attached) for the BP, please have
      a look at: Appendix A. Demos Setup ->Scale and HA of agents.<br>
      <br>
      I read your  <a href="http://wiki.openstack.org/Quantum/LBaaS/Architecture/Scheduler" target="_blank">http://wiki.openstack.org/Quantum/LBaaS/Architecture/Scheduler</a> 
      and have this:<br>
      1. Quantum scheduler can be multischeduler, just like one in
      nova-scheduler although it schedules only VM to compute hosts now.<br>
      2. With multischeduler, we can have sub schedulers. for example
      sub scheduler for allocating networks to DHCP agents<br>
      sub scheduler for allocating quantum routers to l3 agents,  and
      subscheduler for allocating 'pool' to devices<br>
      So here it is: <br>
      class multischeduler(object):<br>
      scheduler['network'] = import_class(conf.network_scheduler)<br>
      scheduler['router'] = import_class(conf.router_scheduler)<br>
      scheduler['pool'] = import_class(conf.pool_scheduler)<br>
      <br>
      3. Then the sequence diagram is calling scheduler['pool'].<br>
      My BP is calling other two.<br>
      <br>
      Thanks<br>
      Yong Sheng Gong<div><div class="h5"><br>
      <br>
      On 12/18/2012 10:25 PM, Eugene Nikanorov wrote:<br>
    </div></div></div>
    <blockquote type="cite"><div><div class="h5">Hi Yong Sheng,
      <div><br>
      </div>
      <div>I see you've started working on <a href="https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler" target="_blank">https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler</a></div>
      <div>
        <br>
      </div>
      <div>We also thought on designing/implementing scheduler for load
        balancer service.</div>
      <div>Although we're working on it within LBaaS effort, we're
        designing scheduler to be a framework where service-specific
        scheduling algorithms may easily be plugged.</div>
      <div><br>
      </div>
      <div>Could you briefly go over <a href="http://wiki.openstack.org/Quantum/LBaaS/Architecture/Scheduler" target="_blank">http://wiki.openstack.org/Quantum/LBaaS/Architecture/Scheduler</a> and
        share your thoughts?</div>
      <div>
        I think it would be better to have one scheduling component in
        quantum rather than a set of shedulers for each kind of service.</div>
      <div><br>
      </div>
      <div>Also I have a question regarding quantum scheduler
        architecture proposal (both options1 and 2) in blueprint spec:</div>
      <div>why does it need to be a separate process?</div>
      <div><br>
      </div>
      <div>Thanks,</div>
      <div>Eugene.</div>
      <br>
      <fieldset></fieldset>
      <br>
      </div></div><pre>_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a>
<a 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>
    </blockquote>
    <br>
  </div>

<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a 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><br clear="all"><div><br></div>-- <br>~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>Dan Wendlandt <div>Nicira, Inc: <a href="http://www.nicira.com" target="_blank">www.nicira.com</a><br><div>twitter: danwendlandt<br>

~~~~~~~~~~~~~~~~~~~~~~~~~~~<br></div></div>