[RFE] Validation to ensure NeutronNetworkType and NeutronTunnelTypes are the same

[Dan Trainor]

Neutron Tunnel types that aren't specified in Neutron Network types will not be available and may fail a deployment.

Ensure that NeutronTunnelTypes is the value or in the list of allowed values for NeutronNetworkType prior to deployment.

[Katerina Pilatova (kpilatov)]

How can one get the values of NeutronTunnelTypes and NeutronNetworkType?

[Julie Pichon (jpichon)]

I'm not sure if it's accessible from the validations but they are in the mistral environment for the plan (e.g. `mistral environment-get overcloud` for the default plan) in the parameter_defaults. They might not exist in the environment though if the user didn't override them. I'm not sure if there's a way to get to them besides hardcoding the default, lLooks like the defaults come from THT at the moment: https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/neutron-plugin-ml2.yaml#L26 and #L60 too.

[Jiri Tomasek (jtomasek)]

We should probably be able to specify allowed_values constraint on NeutronTunnelTypes parameter (http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#allowed-values) such as this:

NeutronTunnelTypes:
  ...
  constraints:
    allowed_values: {get_param: NeutronNetworkType}

In addition, GUI is able to leverage this and provide a multi-select input.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE