<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">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 class="sprite external-link" rel="nofollow"
href="https://docs.google.com/presentation/d/1eiBx6roRyk-mUfgBfJZUtEjEGbgTB5Gf4r7varAyDpg/edit"
style="background-image:
url(https://blueprints.launchpad.net/+icing/rev16378/inline-sprites-1.png);
color: rgb(0, 51, 170); text-decoration: none; padding: 0px 0px
6px 18px; line-height: 18px; background-position: 0px -2622px;
background-repeat: no-repeat no-repeat; ">Read the full
specification</a> is old. But I cannot change the URL. the new
Spec is '
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a rel="nofollow"
href="https://docs.google.com/document/d/1TJlW0_tMpeENA_ia38fvRu7ioKRt9fsWXBjivwd1mMw/edit"
style="max-width: 60em; color: rgb(0, 51, 170); text-decoration:
none; font-family: sans-serif; font-size: 12px; font-style:
normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: 18px; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); ">https:/<wbr
style="max-width: 60em; ">/docs.google.<wbr style="max-width:
60em; ">com/document/<wbr style="max-width: 60em; ">d/1TJlW0_<wbr
style="max-width: 60em; ">tMpeENA_<wbr style="max-width: 60em;
">ia38fvRu7ioKRt9<wbr style="max-width: 60em; ">fsWXBjivwd1mMw/<wbr
style="max-width: 60em; ">edit</a>'<br>
<br>
I have a patch for this BP:
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://review.openstack.org/#/c/18216/">https://review.openstack.org/#/c/18216/</a><br>
<br>
please see the schedule_xxxx methods in this file:<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="https://review.openstack.org/#/c/18216/3/quantum/db/multipleagents_db.py">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 moz-do-not-send="true"
href="http://wiki.openstack.org/Quantum/LBaaS/Architecture/Scheduler">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<br>
<br>
On 12/18/2012 10:25 PM, Eugene Nikanorov wrote:<br>
</div>
<blockquote
cite="mid:CAJfiwOS0EvhEG4dTqmUBSaBowaCTwmEUjJCtcwFzBv+oKEMj0Q@mail.gmail.com"
type="cite">Hi Yong Sheng,
<div><br>
</div>
<div>I see you've started working on <a moz-do-not-send="true"
href="https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler">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 moz-do-not-send="true"
href="http://wiki.openstack.org/Quantum/LBaaS/Architecture/Scheduler">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 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>