I have implemented a (single-node) constraint-based / rules-based scheduler
that attempts to find a "good" solution to potentially conflicting rules. I
used it to implement eday's "openstack:location=machine1.rack1.room1.dfw"
type pragma that we discussed in the past. I think this could helpful f
On Mar 10, 2011, at 11:35 AM,
wrote:
> a) Looks like one of the major drivers is the rules based scheduling -
> mutual exclusion, temporal and spatial rules, and so forth. Is there an
> existing way to capture these placement pragmas ? Or should we have a light
> rules framework ?
to be worked out." This might be a good time to introduce the concept of distributed cmDb that has the run time configurations. c) Do we have a blueprint yet ? Would be happy to contribute ... Cheers
Original Message
Subject: [Openstack] DIstributed Scheduler blueprint u
I've updated the specification for the Distributed Scheduler blueprint
to include details of the proposed implementation. Up until now it hasn't been
possible to provide any detail, since this depended on the implementation of
the changes for multi-cluster/zones. Now that Sandy has made
4 matches
Mail list logo
