Comment 2 for bug 1129485

I believe we will need one or more new scheduler filters for baremetal deployments anyway, eg one that does exact flavor<=>host CPU/ram/disk matching. So, that being said, is there anything wrong with requiring deployers to change the scheduler filters for bare metal? If that's acceptable, then this just needs to be documented.

An alternative might be (if this is even possible) to have the CCF behave slightly differently for different hypervisor, but I don't feel like changing or writing a new scheduler filter is a good thing to do at this point (iow, until Havana opens).

Any other ideas?