<div dir="ltr"><div>Thanks Sylvain, we did not work out the API requirement till now but I think the requirement should be similar with nova: we need select_destination to select the best target host based on filters and weights.<br><br>There are also some discussions here <a href="https://blueprints.launchpad.net/magnum/+spec/magnum-scheduler-for-docker">https://blueprints.launchpad.net/magnum/+spec/magnum-scheduler-for-docker</a><br><br></div>Thanks!<br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-02-09 16:22 GMT+08:00 Sylvain Bauza <span dir="ltr"><<a href="mailto:sbauza@redhat.com" target="_blank">sbauza@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi Magnum team,<br>
<br>
<br>
<div>Le 07/02/2015 19:24, Steven Dake
(stdake) a écrit :<br>
</div><span class="">
<blockquote type="cite">
<div><br>
</div>
<div><br>
</div>
<span>
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span>Eric Windisch
<<a href="mailto:eric@windisch.us" target="_blank">eric@windisch.us</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack
Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Saturday,
February 7, 2015 at 10:09 AM<br>
<span style="font-weight:bold">To: </span>"OpenStack
Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re:
[openstack-dev] [Magnum] Scheduling for Magnum<br>
</div>
<div><br>
</div>
<blockquote style="BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0 0 5">
<div>
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
1) Cherry pick scheduler code from Nova, which
already has a working a filter scheduler design.<br>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</span></blockquote>
<br></span>
The Gantt team explored that option by the Icehouse cycle and it
failed with a lot of problems. I won't list all of those, but I'll
just explain that we discovered how the Scheduler and the Nova
compute manager were tighly coupled, which was meaning that a
repository fork was really difficult to do without reducing the tech
debt.<br>
<br>
That said, our concerns were far different from the Magnum team : it
was about having feature parity and replacing the current Nova
scheduler, while your team is just saying that they want to have
something about containers.<span class=""><br>
<br>
<br>
<blockquote type="cite"><span>
<blockquote style="BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0 0 5">
<div>
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2) Integrate swarmd to leverage its scheduler[2].</blockquote>
<div><br>
</div>
<div>I see #2 as not an alternative but possibly an
"also". Swarm uses the Docker API, although
they're only about 75% compatible at the moment.
Ideally, the Docker backend would work with both
single docker hosts and clusters of Docker
machines powered by Swarm. It would be nice,
however, if scheduler hints could be passed from
Magnum to Swarm.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Eric Windisch </div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>Adrian & Eric,</div>
<div><br>
</div>
<div>I would prefer to keep things simple and just integrate
directly with swarm and leave out any cherry-picking from Nova.
It would be better to integrate scheduling hints into Swarm, but
I’m sure the swarm upstream is busy with requests and this may
be difficult to achieve.</div>
<div><br>
</div>
</blockquote>
<br></span>
I don't want to give my opinion about which option you should take
as I don't really know your needs. If I understand correctly, this
is about having a scheduler providing affinity rules for containers.
Do you have a document explaining which interfaces you're looking
for, which kind of APIs you're wanting or what's missing with the
current Nova scheduler ?<br>
<br>
MHO is that the technology shouldn't drive your decision : whatever
the backend is (swarmd or an inherited nova scheduler), your
interfaces should be the same. <br>
<br>
-Sylvain<br>
<br>
<br>
<blockquote type="cite">
<div>
</div>
<div>Regards</div>
<div>-steve</div>
<div><br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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 Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Thanks,<br><br></div>Jay Lau (Guangya Liu)<br></div></div></div></div>
</div>