<div dir="ltr">Hi all,<div><br></div><div>Maybe my description is not clear enough.</div><div>As is known to everyone, service provider provides ability for plugins to schedule a different vendor. It is just a factor of scheduling. We should integrate this into a United Schedule Module(USM) which provides scheduling service for every plugins. This scheduling service can be based on capability, resource, vendor, user-specific requirement and so on.</div><div>So how to get those information from back-ends? Statically configuring or dynamically reporting? And those info are changing should be taken into consideration. It's important to note that we have reported something in current agent report implementation.</div><div>My suggestion is that agents (and controllers in phase 2) report their capability, vendor, and other info to the USM in core. Every plugin invokes the USM to schedule not dose it by their selves. We can even wrap scheduling into agent-calling method(aka service driver), plugins can be standardized and do not care vendors, agent or controller and other things.</div><div><br></div><div>BR,</div><div>Germy</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 20, 2014 at 2:59 PM, Germy Lure <span dir="ltr"><<a href="mailto:germy.lure@gmail.com" target="_blank">germy.lure@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><font color="#cc0000">Hi Mathieu,</font><div><font color="#cc0000"><br></font></div><div><font color="#cc0000">Thanks for your response.</font></div><div><font color="#cc0000">I'm so sorry to reply you util today.(I was on a vacation)</font></div><div><font color="#cc0000">I have some comments inline.</font></div><div><font color="#cc0000"><br></font></div><div><font color="#cc0000">BR,</font></div><div><font color="#cc0000">Germy</font></div><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, Oct 8, 2014 at 7:34 PM, Mathieu Rohon <span dir="ltr"><<a href="mailto:mathieu.rohon@gmail.com" target="_blank">mathieu.rohon@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi germy,<br><br></div>thanks for this interesting proposal.<br></div>To go further, It would be interesting to insert in your framework the capacity to load service plugin dynamically, not only service providers.<br></div></div></div></blockquote></span><div><font color="#cc0000">Thanks for your suggestion. I think this has been included in the evolution part.</font></div><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div></div>It as been discussed here [1][2]f or GBP needs, but it's something interesting for other service plugin which want to be hosted in a independent (stackforge) project.<br></div></div></blockquote></span><div><font color="#cc0000">It is different. My proposal targets agent and controller not plugin.</font></div><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div>There is a line in the etherpad for kilo design summit about that [3]. I hope this will be discussed.<br></div></blockquote></span><div>Yes, I also hope.</div><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br>[1]<a href="https://review.openstack.org/#/c/116996/" target="_blank">https://review.openstack.org/#/c/116996/</a><br>[2]<a href="https://review.openstack.org/#/c/123620/" target="_blank">https://review.openstack.org/#/c/123620/</a><br>[3]<a href="https://etherpad.openstack.org/p/kilo-neutron-summit-topics" target="_blank">https://etherpad.openstack.org/p/kilo-neutron-summit-topics</a><br><br></div><div>Mathieu<br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Tue, Oct 7, 2014 at 3:51 PM, Germy Lure <span dir="ltr"><<a href="mailto:germy.lure@gmail.com" target="_blank">germy.lure@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">Hi all,<div><br></div><div>I have an idea about service provider framework. Anyone interested in this topic can give me some suggestions.</div><div><br><div><div class="gmail_extra">My idea is that providers report their services capability dynamically not configured in neutron.conf. See details by the link below.</div><div class="gmail_extra"><a href="https://docs.google.com/presentation/d/1_uNF0JEDyoFor8xj-MaaacPL334hiWJWB7NzfRrcVJg/edit?usp=sharing" target="_blank">https://docs.google.com/presentation/d/1_uNF0JEDyoFor8xj-MaaacPL334hiWJWB7NzfRrcVJg/edit?usp=sharing</a><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Everyone can comment this doc.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Here are the main pages.</div><div class="gmail_extra"><span><p dir="ltr" style="line-height:1;margin-top:0pt;margin-bottom:0pt"><img src="cid:ii_i0zb2c874_148eade7c6d0024f" height="263" width="474"></p><p dir="ltr" style="line-height:1;margin-top:0pt;margin-bottom:0pt"><br></p><p dir="ltr" style="line-height:1;margin-top:0pt;margin-bottom:0pt"><img src="cid:ii_i0zb49rq8_148eadfde7ba908f" height="267" width="474"><br></p><p dir="ltr" style="line-height:1;margin-top:0pt;margin-bottom:0pt"><br></p><p dir="ltr" style="line-height:1;margin-top:0pt;margin-bottom:0pt"><img src="cid:ii_i0zb558n9_148eae0756de7c0a" height="264" width="474"><br></p><p dir="ltr" style="line-height:1;margin-top:0pt;margin-bottom:0pt"><br></p><p dir="ltr" style="line-height:1;margin-top:0pt;margin-bottom:0pt"><img src="cid:ii_i0zb5t2q10_148eae0f029d18f8" height="260" width="474"><br><span style="line-height:normal">BR,</span></p></span></div><div class="gmail_extra">Germy</div></div></div></div>
<br></div></div>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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></div></div><br></div></div>
</blockquote></div><br></div>