yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #29576
[Bug 1432897] [NEW] [Launch Instance Fix] source step - fix donut chart dynamic update - limit instance count
Public bug reported:
In the current version of the Launch Instance Wizard Source Step, the
instance count field is not correctly limited based on current instance
usage and nova limits (maxTotalInstances). There is a bug whereby the
user can enter an instance count of more than what is available, and in
addition the donut chart does not update properly when this occurs. We
should correct this so that if a user enters a number greater than what
is available, it should automatically round down to the available count.
Example. If I have 10 max instances quota, and currently have 6
instances in use, I should only be able to specify 4 as my instance
count (which will update the donut chart to 100%). However there is
nothing in the code that limits me from entering a higher number. We
should add some code that limits the instance count based on #
remaining, and automatically rounds down to the highest number of
instances that would prevent the user from going over 100%
** 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/1432897
Title:
[Launch Instance Fix] source step - fix donut chart dynamic update -
limit instance count
Status in OpenStack Dashboard (Horizon):
New
Bug description:
In the current version of the Launch Instance Wizard Source Step, the
instance count field is not correctly limited based on current
instance usage and nova limits (maxTotalInstances). There is a bug
whereby the user can enter an instance count of more than what is
available, and in addition the donut chart does not update properly
when this occurs. We should correct this so that if a user enters a
number greater than what is available, it should automatically round
down to the available count.
Example. If I have 10 max instances quota, and currently have 6
instances in use, I should only be able to specify 4 as my instance
count (which will update the donut chart to 100%). However there is
nothing in the code that limits me from entering a higher number. We
should add some code that limits the instance count based on #
remaining, and automatically rounds down to the highest number of
instances that would prevent the user from going over 100%
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1432897/+subscriptions
Follow ups
References