Hi Nikola, Firstly, thanks for waiting for me to respond and sorry I was absent for the last couple of weeks.
The extensible resource tracker bp deals with two distinct information flows: 1. information about resources that is passed from the compute node to the scheduler, 2. information about resource requirements passed to the scheduler and the compute node. If I understand your email below correctly, you are saying that information such as extra_specs, is not made available to the compute node or the resource plugins. This is specifically about the second item (2.) above. The patch that you propose to revert addresses the first item (1.), i.e. it provides a means to select which resources are tracked and to pass that information to the scheduler. It gives us two things: we can add resource plugins and pass information to the scheduler without having to change the resource tracker or scheduler. We can also pick and chose which resource plugins to use, and so what information we want to write to the database and pass to the scheduler. The ability to omit resource information is as useful as the ability to add it. So if new a resource plugin is added, operators that do not use that information do not need to configure it. As an operator myself, I would be happy to omit the proliferation of compute node details that are coming, while benefiting from those that are of use to me. The interface for the plugins does not need to be considered a fixed external interface, it is not. It is ok to add necessary parameters if there is no other sensible way to pass information you need. So in short, the ability to add resource information without impacting everybody is the value that the patch you want to revert brings. If in the future another design is settled on for resource tracking and scheduling it will still have to face the same requirement. The compute node will have a set of resource information that could be tracked and used, but not everyone will want the overhead of discovering and reporting all of it, so they should not need to have all of it. Paul On 19 August 2014 10:11, Nikola Đipanov <ndipa...@redhat.com> wrote: > Since after a week of discussing it I see no compelling argument against > reverting it - here's the proposal: > > https://review.openstack.org/115218 > > Thanks, > N. > > On 08/12/2014 12:21 PM, Nikola Đipanov wrote: > > Hey Nova-istas, > > > > While I was hacking on  I was considering how to approach the fact > > that we now need to track one more thing (NUMA node utilization) in our > > resources. I went with - "I'll add it to compute nodes table" thinking > > it's a fundamental enough property of a compute host that it deserves to > > be there, although I was considering Extensible Resource Tracker at one > > point (ERT from now on - see ) but looking at the code - it did not > > seem to provide anything I desperately needed, so I went with keeping it > > simple. > > > > So fast-forward a few days, and I caught myself solving a problem that I > > kept thinking ERT should have solved - but apparently hasn't, and I > > think it is fundamentally a broken design without it - so I'd really > > like to see it re-visited. > > > > The problem can be described by the following lemma (if you take 'lemma' > > to mean 'a sentence I came up with just now' :)): > > > > """ > > Due to the way scheduling works in Nova (roughly: pick a host based on > > stale(ish) data, rely on claims to trigger a re-schedule), _same exact_ > > information that scheduling service used when making a placement > > decision, needs to be available to the compute service when testing the > > placement. > > """ > > > > This is not the case right now, and the ERT does not propose any way to > > solve it - (see how I hacked around needing to be able to get > > extra_specs when making claims in , without hammering the DB). The > > result will be that any resource that we add and needs user supplied > > info for scheduling an instance against it, will need a buggy > > re-implementation of gathering all the bits from the request that > > scheduler sees, to be able to work properly. > > > > This is obviously a bigger concern when we want to allow users to pass > > data (through image or flavor) that can affect scheduling, but still a > > huge concern IMHO. > > > > As I see that there are already BPs proposing to use this IMHO broken > > ERT ( for example), which will surely add to the proliferation of > > code that hacks around these design shortcomings in what is already a > > messy, but also crucial (for perf as well as features) bit of Nova code. > > > > I propose to revert  ASAP since it is still fresh, and see how we can > > come up with a cleaner design. > > > > Would like to hear opinions on this, before I propose the patch tho! > > > > Thanks all, > > > > Nikola > > > >  > https://blueprints.launchpad.net/nova/+spec/virt-driver-numa-placement > >  https://review.openstack.org/#/c/109643/ > >  https://review.openstack.org/#/c/111782/ > >  https://review.openstack.org/#/c/89893 > > > > _______________________________________________ > > OpenStack-dev mailing list > > OpenStackfirstname.lastname@example.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStackemail@example.com > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev