Launch instance from Volumes Page opens LEGACY launch instance, even if LEGACY is set to False in local_settings

[Amogh]

Launch instance from Volumes Page opens LEGACY launch instance, even if LEGACY is set to False in local_settings
1. Create bootable volume.
2. Launch the instance from volume, Observe that 'legacy' launch instance is opened. local_settings is set with below settings:

LAUNCH_INSTANCE_NG_ENABLED = True
LAUNCH_INSTANCE_LEGACY_ENABLED = False

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/219925

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/219925
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=9a9772ab80318d8fa88600dcc719f178fdd318a2
Submitter: Jenkins
Branch: master

commit 9a9772ab80318d8fa88600dcc719f178fdd318a2
Author: mavinagi <email address hidden>
Date: Wed Sep 2 19:04:02 2015 -0500

    Handle Volume launch as instance(NG) in Volume tables.

    The launch as instance option for Volumes launches the legacy
    launch instance wizard even if local_settings is configured
    for LAUNCH_INSTANCE_LEGACY_ENABLED = False. This Fix addresses
    the issue.

    Volume snapshots will be a separate patch.

    Horizon tables.js has a separate bug that needs to be fixed:

    https://bugs.launchpad.net/horizon/+bug/1514627

    Change-Id: Id4a7dc2a48c63cbe27ece4dba1825eb89b7a0388
    Closes-bug: #1491645
    Co-Authored-By: Travis Tripp <email address hidden>