<div dir="ltr"><div><div><div><div><div>Thanks Jay Pipes and Boris for the comments.<br><br></div>@Jay Pipes, agree, I can name it as AvailabilityZoneAggregateFilter.<br><br></div>@Boris,<br><br>For your first question, we may want to get some answer from @Robert Collins.<br>
For second question, perhaps you can refer to <a href="https://blueprints.launchpad.net/nova/+spec/forklift-scheduler-breakout">https://blueprints.launchpad.net/nova/+spec/forklift-scheduler-breakout</a> , from this bp specification, <b>Gantt's goal is </b><span class=""><b>is to deprecate nova-scheduler in I and remove in J</b>, so perhaps your bp can be implemented on Gantt? <br>
</span></div><span class="">For third question, the goal of Gantt is for a </span>common scheduler for OpenStack, you can refer to
<a href="https://blueprints.launchpad.net/nova/+spec/forklift-scheduler-breakout">https://blueprints.launchpad.net/nova/+spec/forklift-scheduler-breakout</a> for more detail.<br><br></div>Thanks,<br><br></div>Jay<br>
<div><div><div><div class=""><div class=""><span name="Collins, Robert (Converged Cloud)" class=""><br></span>
</div></div><div><div></div></div></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014/1/6 Boris Pavlovic <span dir="ltr"><<a href="mailto:bpavlovic@mirantis.com" target="_blank">bpavlovic@mirantis.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi Jay, </div><div><br></div><div>I have 3 points:</div><div><br></div><div>First of all:</div><div>
<a href="https://github.com/openstack/gantt/" target="_blank">https://github.com/openstack/gantt/</a><br></div><div>Why this project has all history of Nova? It seems very odd way to create new project aka clone Nova remove all from Nova..</div>
<div><br></div><div>Second:</div><div>This blueprint <a href="https://blueprints.launchpad.net/nova/+spec/no-db-scheduler" target="_blank">https://blueprints.launchpad.net/nova/+spec/no-db-scheduler</a> should be implement before switching to separated scheduler aaS.<br>
</div>
<div>The main reason is that: scheduler business logic is deeply connected with host states that are deeply connected with db models, that makes a really hard (or impossible we already tried) process of making common scheduler. </div>
<div><br></div><div>Third: </div><div>Why this project, that is actually just Nova copy paste is under "openstack"?</div><div><br></div><div><br></div><div>Best regards,</div><div>Boris Pavlovic</div><div><div>
<br>
</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Sun, Jan 5, 2014 at 6:13 PM, Jay Lau <span dir="ltr"><<a href="mailto:jay.lau.513@gmail.com" target="_blank">jay.lau.513@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 class="h5"><div dir="ltr"><div><div><div><div><div><div>Greetings,<br><br></div>Here come a question related to AvailabilityZoneFilter.<br>
<br>A new project Gantt which is a common scheduler for OpenStack is now under incubation, and now most of the code are get from nova scheduler.<br>
<br></div>I'm planning to make Gantt use common scheduler from oslo, and I think that this is the right direction and it is better do this at this stage for Gantt to make sure it has a good code base. But AvailabilityZoneFilter has different logic in oslo and Gantt.<br>
<br></div>In oslo, AvailabilityZoneFilter only handles availability_zone from request_spec; but in Gantt, AvailabilityZoneFilter can handle availability_zone from both request_spec and aggregation metadata, we cannot sync AvailabilityZoneFilterfrom oslo to Gantt.<br>
<br></div>What about split the AvailabilityZoneFilter in Gantt to two filters, one is AvailabilityZoneFilter which has same logic with oslo, the other we can name it as AggregateAvailabilityZoneFilter which will only handle availability_zone from aggregation metadata, this can make sure Gantt can sync AvailabilityZoneFilter from oslo and make AvailabilityZoneFilter a common scheduler filter for both Gantt and Cinder. What do you think?<br>
<br></div>Thanks,<br><br></div>Jay<br></div>
<br></div></div><div class="im">_______________________________________________<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></div></blockquote></div><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></div>