Comment 1 for bug 1716955

We probably need some discussion on how to approach this, since the profiles list command only really cares about the per-profile tagging performed via capabilities: profile, and not per-node tagging via capabilities: node (which aren't mapped to any profile, but instead work via *SchedulerHints parameters to control placement precisely on deploy.

I think we may need another command, or a pre-deployment validation to catch when the *SchedulerHints doesn't match the node tagging in ironic - I'm not really sure extending the profiles command to understand heat SchedulerHints is the right approach, but open to suggestions about how we might do that (currently it just looks at the nodes/flavors, the heat parameters aren't defined until the overcloud deploy).