yahoo-eng-team team mailing list archive

[OpenStack Infra <1613900@xxxxxxxxxxxxxxxxxx>]

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

commit be6bcef45289ce1a934db478e5c9c7705890af18
Author: Matt Borland <matt.borland@xxxxxxx>
Date:   Mon Aug 29 09:54:56 2016 -0600

    Let Nova to pick availability zone if more than 1
    
    In the Angular Launch Instance, if there is more than one availability zone,
    default to the option for the Nova scheduler to pick.  This is a regression
    from the legacy Launch Instance feature.
    
    If you want to simulate testing the logic with multiple avaiability zones,
    go to:  .../launch-instance/launch-instance-model.service.js line 785 and add:
    
    model.availabilityZones.push({label: 'another one', value: 'another one'});
    
    Change-Id: Ib81447382bc9d43e33ce97f78c085d2a94ff2018
    Closes-Bug: 1613900


** Changed in: horizon
       Status: In Progress => Fix Released

-- 
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/1613900

Title:
  Unable to use 'Any' availability zone when spawning instance

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  While using Mitaka, we found that by default, using js backend, it is
  not possible to choose 'any' availability zone. The issue is not fixed
  in master branch.

  For python implementation the logic is:
  https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py#L390

  The JS implementation miss the logic if number of AZs is >1
  https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/launch-instance-model.service.js#L321

  Also, JS implementation looks ugly if you have lot of subnets per
  network...

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1613900/+subscriptions