Thanks Jay Pipes and Boris for the comments. @Jay Pipes, agree, I can name it as AvailabilityZoneAggregateFilter.
@Boris, For your first question, we may want to get some answer from @Robert Collins. For second question, perhaps you can refer to https://blueprints.launchpad.net/nova/+spec/forklift-scheduler-breakout , from this bp specification, *Gantt's goal is **is to deprecate nova-scheduler in I and remove in J*, so perhaps your bp can be implemented on Gantt? For third question, the goal of Gantt is for a common scheduler for OpenStack, you can refer to https://blueprints.launchpad.net/nova/+spec/forklift-scheduler-breakout for more detail. Thanks, Jay 2014/1/6 Boris Pavlovic <[email protected]> > Hi Jay, > > I have 3 points: > > First of all: > https://github.com/openstack/gantt/ > Why this project has all history of Nova? It seems very odd way to create > new project aka clone Nova remove all from Nova.. > > Second: > This blueprint > https://blueprints.launchpad.net/nova/+spec/no-db-schedulershould be > implement before switching to separated scheduler aaS. > 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. > > Third: > Why this project, that is actually just Nova copy paste is under > "openstack"? > > > Best regards, > Boris Pavlovic > > > > On Sun, Jan 5, 2014 at 6:13 PM, Jay Lau <[email protected]> wrote: > >> Greetings, >> >> Here come a question related to AvailabilityZoneFilter. >> >> 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. >> >> 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. >> >> 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. >> >> 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? >> >> Thanks, >> >> Jay >> >> _______________________________________________ >> OpenStack-dev mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
