d16ed45e06
"Get-me-a-network" feature is supported in Nova API 2.37 or later. To support this in horizon, a dummy "auto_allocated_network" is shown in the launch instance form. I believe this approach fits the current way of the launch instance form. The dummy network is a special network ID and if specified the nova API wrapper converts 'nics' parameter properly. In addition, a dummy "auto_allocated_network" is now shown in the network table. This is because Neutron creates an actual auto allocated network once a server is created specifying nics=="auto". I believe this fake behavior brings consistency in the network table to some extent, while this is just a compromise. Note that this patch does not cover the network topology integration. "auto_allocated_network" is not shown until the actual auto allocated network is created. The network topology integration requires more work. For example, the link for the fake auto allocated network should be disabled in the flat view. The pop-up for the fake auto allocated network should be disabled in the graph view. Change-Id: I062fc1b7ed75dc771ddc7f13c8324ed4ffab6808 Closes-Bug: #1690433
16 lines
696 B
YAML
16 lines
696 B
YAML
---
|
|
features:
|
|
- |
|
|
[:bug:`1690433`] "Get me a network" feature provided by nova and neutron
|
|
is now exposed in the launch server form.
|
|
This feature will sets up a neutron network topology for a project
|
|
if there is no network in the project. It simplifies the workflow when
|
|
launching a server.
|
|
In the horizon support, when there is no network which can be used
|
|
for a server, a dummy network named 'auto_allocated_network' is shown
|
|
in the network choices.
|
|
The feature is disabled by default because it requires preparations
|
|
in your neutron deployment.
|
|
To enable it, set ``enable_auto_allocated_network`` in
|
|
``OPENSTACK_NEUTRON_NETWORK`` to ``True``.
|