Cloud Network and Cloud Subnet Create form is too specific to OpenStack

[agrare]

When creating a Cloud Network the form requires a cloud_tenant be selected but that isn't true across all provider types. The Provider Network Type list should be filtered by the provider type, and Physical Network and Segment ID don't exist on all providers

For the cloud subnet form not all cloud provider support dhcp and ipv6.

[agrare]

cc @skateman

[skateman]

We could do something like we did for providers: API-driven DDF schema defined in the provider repos.

[jaywcarman]

I'm looking at implementing cloud volume creation for the IBM Cloud PowerVS provider and am running into a similar situation (geared towards OpenStack Cinder, with some Amazon EBS jammed in: https://github.com/ManageIQ/manageiq-ui-classic/blob/master/app/assets/javascripts/controllers/cloud_volume/cloud_volume_form_controller.js#L282-L286).

We could do something like we did for providers: API-driven DDF schema defined in the provider repos.

This would be awesome - is there any plan to implement it soon? How can we help?

[skateman]

@jaywcarman I'd need a list (or a DDF schema) of common fields and a list (or DDF schema) of provider specific fields for each provider. But you're talking about Cloud Volumes, while this issue is about Networks and Subnets, should we create a separate issue to track it? There we could collect all the necessary data with fancy checkboxes 😉

[skateman]

I guess the form's current state reflects OpenStack, so I can just move parts of it into a DDF schema in the openstack provider repo. The NSX-T provider has its own form already, just accessed elsewhere so I can deal with that too. I'd like to know what kind of other providers are there (amazon, ibm, nuage? is there any more?) and with what kind of specific fields and requirements. cc @agrare @jaywcarman