© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
I was going to open a new bug for this code:
https:/
But this existing bug is probably close enough, especially since in Pike we removed RamFilter and DiskFilter from the default list of enabled filters, so the limits for those aren't going to come from the scheduler to the compute anymore for claims (by default for new installs).
But the code here specifically:
https:/
Is mimicing the RamFilter and uses the ComputeNode information, when it should be using the Placement service now which would have the latest inventory information for that ComputeNode resource provider at this point.
So as we remove core/ram/disk filters from the scheduler and replace those with using the Placement service, in the hopes of eventually removing that kind of claims logic in the compute service, we need to replace anything that relied on it to also use Placement, like this code in conductor.