Comment 3 for bug 1747457

The first support for LXD constraints has been committed to the develop and 2.4 branches.

In this scenario, the "cores" constraint ends up as the "limits.cpu" configuration setting when using it to provision a container machine.

This same LXD config item is used to set affinity by giving it range syntax; "1-1" for core 1, "1-2" for 1 and 2 etc.

The blocker for piggy-backing on the current functionality is that the cores constraint is validated as numeric, so supplying those strings will not work. However, I don't think it would take much to enable this feature.