I still want GET API. what is the criteria of "overkill"?
Horizon team receives the following patches ONLY to sync neutron changes.
From feedbacks in Horizon reviews, horizon reviewers has a consensus that this kind of things should not happen in Horizon and Neutron should expose some API.
Horizon has settings for supported_provider_types, segmentation_id_range and extra_provider_types (proposed).
Mirroring this kind of parameters is unproductive. All of them are unnecessary if neutron has a proper API.
I still want GET API. what is the criteria of "overkill"?
Horizon team receives the following patches ONLY to sync neutron changes.
From feedbacks in Horizon reviews, horizon reviewers has a consensus that this kind of things should not happen in Horizon and Neutron should expose some API.
Horizon has settings for supported_ provider_ types, segmentation_ id_range and extra_provider_ types (proposed).
Mirroring this kind of parameters is unproductive. All of them are unnecessary if neutron has a proper API.
https:/ /review. openstack. org/#/c/ 233934 Sync segmentation ID ranges with Neutron /review. openstack. org/#/c/ 233933 Add Geneve support /review. openstack. org/#/c/ 232975 Add network types used by midonet
https:/
https:/