Enable next gneration instance launch in Horizon

Change the horizon defaults to use the next generation instance management
panels. This change allows deployers to better manage their instances as well
as access to more features/functionality in horizon.

Change-Id: I3502b3e7402223b450773f668545bd6b4a8e7671
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This commit is contained in:
Kevin Carter 2016-05-05 10:52:38 -05:00
parent 50d8dea61c
commit f0dc5195aa
No known key found for this signature in database
GPG Key ID: 69FEFFC5E2D9273F
2 changed files with 18 additions and 2 deletions

View File

@ -141,8 +141,8 @@ horizon_ssl_no_verify: "{{ (keystone_service_adminuri_insecure | bool or keyston
horizon_default_role_name: _member_
## Launch instance
horizon_launch_instance_legacy: True
horizon_launch_instance_ng: False
horizon_launch_instance_legacy: False
horizon_launch_instance_ng: True
## Neutron features to enable
horizon_enable_neutron_lbaas: False

View File

@ -0,0 +1,16 @@
---
features:
- The horizon next generation instance management panels have been
enabled by default. This changes horizon to use the upstream defaults
instead of the legacy panels. `Documentation can be found here <http://docs.openstack.org/developer/horizon/topics/settings.html#launch-instance-ng-enabled>`_.
upgrade:
- |
The default horizon instance launch panels have been changed to the
next generation panels. To enable legacy functionality set the following
options accordingly:
.. code-block:: yaml
horizon_launch_instance_legacy: True
horizon_launch_instance_ng: False