There should be a placement policy like 'best fit' AND taking vCPU into account

The current 'balanced CPU' puts a new partition onto the system with least percentage of CPU usage. With packing and striping "processing units" is one of the metrics (entitled capacity).
In our situation it is often more useful to use the vCPU (Virtual Processor) settings when deploying a new LPAR (or remote restarting it somewhere), as the number of LPARs (and the situation at failover) forces us to set "processing units" quite low. It would be good if PowerVC placement could take the desired number of vCPU into account.

Also, when placing an LPAR, it could try to place it at a host (given the correct host group, connectivity to storage and networking is there etc.) which has enough available CPU (not a percentage but a true number of CPU that is never - or hardly ever - used). Meaning: if I deploy an LPAR with 4 vCPU, it should select a host where 95% of the time 4 CPU worth of capacity is still available (if there is none, the 'processing units' metric could be used to determine placement).

It should also select the host which has enough CPU available to take an additional load of X vCPU; if there are multiple hosts that satisfy this criteria, it should place the LPAR on the host that will have the least CPU remaining. That way, if you deploy a few smaller partitions followed by a big one, changes are bigger there will be a host left to accomodate the big partition.