Akihiro: I am getting all my bug numbers and links all mixed up.
Yes, it along the same lines as the duplicate bug. For the exact same reasons listed in the duplicate bug as well.
I won't bother editing bug due to the decision to not fix.
Reasons for doing being: avoiding hardcoded network provider types in Horizon, and ease of use for Horizon admins.
Exposing some of the values (type_drivers, mechanism_drivers, etc..) from the ml2_conf.ini so admins can understand what is supported.
These are all the related Horizon bugs reported that I could find: https://bugs.launchpad.net/horizon/+bug/1419988 https://bugs.launchpad.net/horizon/+bug/1477522 https://bugs.launchpad.net/horizon/+bug/1478887
If it is a concern that has come up multiple times. There should be another discussion about it. I don't think the "too much engineering" is a valid reason not to do it if resources are available.
Akihiro: I am getting all my bug numbers and links all mixed up.
Yes, it along the same lines as the duplicate bug.
For the exact same reasons listed in the duplicate bug as well.
I won't bother editing bug due to the decision to not fix.
Reasons for doing being: avoiding hardcoded network provider types in Horizon, and ease of use for Horizon admins.
Exposing some of the values (type_drivers, mechanism_drivers, etc..) from the ml2_conf.ini so admins can understand what is supported.
These are all the related Horizon bugs reported that I could find: /bugs.launchpad .net/horizon/ +bug/1419988 /bugs.launchpad .net/horizon/ +bug/1477522 /bugs.launchpad .net/horizon/ +bug/1478887
https:/
https:/
https:/
If it is a concern that has come up multiple times. There should be another discussion about it.
I don't think the "too much engineering" is a valid reason not to do it if resources are available.