Comment 2 for bug 1716955

Hello Steven,

Maybe a new subcommand "validate" might be added to "overcloud" part?

something like:

openstack overcloud validate --profiles --environment <env_file>

openstack overcloud validate --nodes --environment <env_file>

The env_file should contain in both cases:
parameter_defaults:
  ComputeCount: 2
  ControllerCount: 3
  CephStorageCount: 1

The first case will provide profiles through the ironic properties/capabilities.

For the latter case, the env_file must contain:
  ControllerSchedulerHints:
    'capabilities:node': 'controller-%index%'
  ComputeSchedulerHints:
    'capabilities:node': 'compute-%index%'
  CephStorageSchedulerHints:
    'capabilities:node': 'ceph-storage-%index%'

That way, we can validate the values in the env file as well - for the recall, the "--*-scale" and "--*-flavor" options are deprecated in the `openstack overcloud deploy' command, and should hence be removed from the other commands for consistency sake.

More over, if the "validate" subcommand can also query nova in order to ensure it sees the nodes, it's all the best.

This might even deprecate the "profiles" subcommand, IFF the validate can also do the dynamic matching. Or maybe push the `profiles' capabilities to `validate' - this would allow to get a common base/entry point for all pre-deploy validation.

Cheers,

C.