Comment 6 for bug 1623390

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to neutron (master)

Reviewed: https://review.openstack.org/371739
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=933af3fdac4d7d8dd8bf2b419c87b9dc27d69af8
Submitter: Jenkins
Branch: master

commit 933af3fdac4d7d8dd8bf2b419c87b9dc27d69af8
Author: Kevin Benton <email address hidden>
Date: Fri Sep 16 11:39:14 2016 -0600

    Add to rally quotas to handle worst case quota race

    Quoting the quota devref:
    """
    For a reservation to be successful, the total amount of resources requested,
    plus the total amount of resources reserved, plus the total amount of resources
    already stored in the database should not exceed the project's quota limit.
    """

    This means that in the absolute worst case scenario with 20 concurrent
    workers, 19 could have made reservations, committed resources, but not
    yet cleared their reservation. Because of the outstanding reservation
    and the resources created by the 19 workers, they will all be
    double-counted until their reservation is cleared (or it expires).

    This adjusts the rally scenarios to handle the double-count for
    concurrency.

    Related-Bug: #1623390
    Change-Id: I4808a92e7e6067aeeb62fc3b3d7f7ac71b179c44