Bump default quotas for core resources

Bug #1674787 reported by Ihar Hrachyshka
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Wishlist
Ihar Hrachyshka

Bug Description

Ports, networks, subnets default quotas are quite low so most operators still bump them, which doesn't make for a great experience. Neither it helps testing in gate where we need to bump quotas to successfully execute our own tempest suite.

I suggest we bump quotas for those resources, to remove another knob everyone needs to bump in any realistic environment (at least in gate).

Tags: usability
Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :
Changed in neutron:
importance: Undecided → Wishlist
status: New → In Progress
tags: added: usability
Changed in neutron:
assignee: nobody → Ihar Hrachyshka (ihar-hrachyshka)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/444030
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=95f621f717b2e9fe0c89f7188f6d1668200475c8
Submitter: Jenkins
Branch: master

commit 95f621f717b2e9fe0c89f7188f6d1668200475c8
Author: Ihar Hrachyshka <email address hidden>
Date: Mon Mar 6 17:03:33 2017 +0000

    Bump default quotas for ports, subnets, and networks

    It's probably not very realistic to expect power users to be happy with
    the default quotas (10 networks, 50 ports, 10 subnets). I believe that
    larger defaults would be more realistic. This patch bumps existing
    quotas for the aforementioned neutron resources x10 times.

    DocImpact change default quotas in documentation if used in examples
              anywhere.
    UpgradeImpact operators may need to revisit quotas they use.
    Closes-Bug: #1674787
    Change-Id: I04993934627d2d663a1bfccd7467ac4fbfbf1434

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 11.0.0.0b1

This issue was fixed in the openstack/neutron 11.0.0.0b1 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.