Change neutron quota default in local_settings.py

Bug #1227102 reported by Julie Pichon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Invalid
Undecided
Unassigned

Bug Description

The default for OPENSTACK_NEUTRON_NETWORK 'enable_quotas' is set to True in the local_settings.py.example file.

https://github.com/openstack/horizon/blob/master/openstack_dashboard/local/local_settings.py.example#L162

It means by default, when Neutron is enabled, quotas will be displayed and updated in the Project Update form.

However, the default quota driver for Neutron doesn't support updates (cf. bug 1189671), which causes an error message to get displayed whenever the Project details/membership/etc are updated - "Error: Unauthorized: Modified project information and members, but unable to modify project quotas."

When deploying for the first time, it's recommended to simply copy-paste the example file, and tools like e.g. devstack do it automatically. It would make more sense to have a more conservative default until Neutron's default driver changes.

Tags: neutron
Revision history for this message
Julie Pichon (jpichon) wrote :

...although, even with read-only quotas at least users can see their floating IP quotas in the Project Overview / Floating IPs panel without an issue, this still/only affects admin users who may not be aware of the default quota driver limitations. "Access to this resource is denied", as is returned by Neutron here, is a confusing error message when one is logged in as admin.

Revision history for this message
Julie Pichon (jpichon) wrote :

Having thought on it some more, if enabled_quotas is False, the assumption is that the backend plugin doesn't support quotas at all, and therefore that there are no quotas in place, i.e. "infinite resources" - resulting in quotas such as floating IP limits being shown as "unlimited" to users when this might not be true. This would affect all users.

Even if only "read-only" quotas are available then it sounds worthwhile showing them correctly. Then the only affected users are admins on project updates, and there is no actual loss of functionality since the other quotas (nova, cinder) still update correctly. I think it's the less-worse solution, and will leave enable_quotas set to True as is currently.

Closing this, though feel free to reopen if in disagreement.

Changed in horizon:
status: New → Invalid
importance: Medium → Undecided
assignee: Julie Pichon (jpichon) → nobody
milestone: havana-rc1 → none
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.