MAAS selection of node for juju constraints does not choose "best/least-capable" match

a quick search through the code shows no filtering for the result set for the node that best matches, just a first item off the result set.

>A quick search through the code shows no filtering for the result set for the node that best matches, just a first item off the
> result set.

You're right. MAAS could be more intelligent and try to minimize the resources while still satisfying the constraints.

But for this strategy to be really useful, MAAS would need to grow a "cost function" (similar to what aws provides) to decide which machine gets picked up among all the machines that match the constraints.

The current workaround (when you have a limited set of machines and want to allocate them with precision) is to use tags.

> MAAS would need to grow a "cost function"

Ideally an admin should be able to define a "cost function" but a first step could be to provide something meaningful (for instance based on AWS pricing) out of the box.

Marking this fixed for now. We've added a tiny cost function that should make the call to acquire() prefer machines with fewer resources when multiple machines fit.