Public bug reported: The compute API 2.37 microversion allows the user to specify networks='auto' to auto-create a network for the server if an existing network is not available for the tenant.
I setup a current devstack for master (rocky): stack@multiattach:~/devstack$ git log -1 commit 730ce45466a903c639554b2e70f6e40a02e9e29d There are networks available to the tenant: stack@multiattach:~/devstack$ openstack network list +--------------------------------------+---------+----------------------------------------------------------------------------+ | ID | Name | Subnets | +--------------------------------------+---------+----------------------------------------------------------------------------+ | 1cb455be-a537-418e-84ff-fb1e4f300e99 | private | 50866a53-ed31-486f-b493-5e4f002c897c, f27e2124-cf47-44f2-8e2c-aa3a30ff14b0 | | ad1ab7b3-8ba2-478c-94ff-1ca1b8fdacf7 | public | 541605c5-283d-40ea-8ef5-cfc771df5415, b6a3d03e-866a-4aeb-84a0-51c014795df3 | +--------------------------------------+---------+----------------------------------------------------------------------------+ But for some reason when I was creating the server, the networks panel didn't show any available networks (see attached screenshot). That seems like a bug in itself, but the purpose of this bug, is that let's assume the tenant didn't have any available networks - if compute API 2.37 is available, horizon *could* present some kind of 'auto' option for the user to tell nova to auto-allocate a network (via neutron). So I guess this is a feature request. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1751560 Title: horizon doesn't allow auto-allocate network during server create Status in OpenStack Dashboard (Horizon): New Bug description: The compute API 2.37 microversion allows the user to specify networks='auto' to auto-create a network for the server if an existing network is not available for the tenant. I setup a current devstack for master (rocky): stack@multiattach:~/devstack$ git log -1 commit 730ce45466a903c639554b2e70f6e40a02e9e29d There are networks available to the tenant: stack@multiattach:~/devstack$ openstack network list +--------------------------------------+---------+----------------------------------------------------------------------------+ | ID | Name | Subnets | +--------------------------------------+---------+----------------------------------------------------------------------------+ | 1cb455be-a537-418e-84ff-fb1e4f300e99 | private | 50866a53-ed31-486f-b493-5e4f002c897c, f27e2124-cf47-44f2-8e2c-aa3a30ff14b0 | | ad1ab7b3-8ba2-478c-94ff-1ca1b8fdacf7 | public | 541605c5-283d-40ea-8ef5-cfc771df5415, b6a3d03e-866a-4aeb-84a0-51c014795df3 | +--------------------------------------+---------+----------------------------------------------------------------------------+ But for some reason when I was creating the server, the networks panel didn't show any available networks (see attached screenshot). That seems like a bug in itself, but the purpose of this bug, is that let's assume the tenant didn't have any available networks - if compute API 2.37 is available, horizon *could* present some kind of 'auto' option for the user to tell nova to auto-allocate a network (via neutron). So I guess this is a feature request. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1751560/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp