quota info for flavors in database instance create broken

[David Lyle]

The flavor specification for db flavors has different fields than nova flavors, this causes javascript errors on the page stating number cannot be of type None.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/47652
Committed: http://github.com/openstack/horizon/commit/9209e11b89a653c7beb4393c9236723a98bc6a3f
Submitter: Jenkins
Branch: master

commit 9209e11b89a653c7beb4393c9236723a98bc6a3f
Author: David Lyle <email address hidden>
Date: Fri Sep 20 16:53:17 2013 -0600

    Fixing database instance launch workflow

    Two fixes related to one broken workflow.

    First, 1227918 is a lack of support for trove backends that don't
    have volume support enabled. To fix this, the user can now enter
    into 0 for the volume size to work around this. This alters how
    the value is passed troveclient. Working with trove team to get a
    programmatic way to determine is volume support is enabled.

    Second, 1228416 is broken javascript when trying to launch a
    database instance due to a couple of factors. The template for the
    help is mislinked to use the project/instance one. Two, the fields
    in the flavor that trove returns are different than the fields that
    nova returns for flavor. This causes an exception when trying to
    generate the quota/usage graphs on the right hand side of the form.
    Since the javascript is looking for hardcoded values, this is not a
    trivial fix so the offensive code has been removed until it can be
    revisited. Additionally, there is no guarantee that the nova backend
    trove uses is the same as the one regular compute uses. Needs more
    thought/work.

    Combined bug fixes because they are closely related to the same
    action.

    Change-Id: Ia378896d1d52067ac136c55ece9b527f44dd646b
    Closes-bug: #1227918
    Closes-bug: #1228416