.
Thanks,
Kevin
From: Kevin Benton [blak...@gmail.commailto:blak...@gmail.com]
Sent: Thursday, July 30, 2015 4:22 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova, cinder, neutron] quota-update tenant-name
bug
[blak...@gmail.com]
*Sent:* Thursday, July 30, 2015 4:22 PM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [nova, cinder, neutron] quota-update
tenant-name bug
Good point. Unfortunately the other issues are going to be the hard part
to deal
--
*From:* Kevin Benton [blak...@gmail.com]
*Sent:* Thursday, July 30, 2015 4:22 PM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [nova, cinder, neutron] quota-update
tenant-name bug
Good point. Unfortunately the other issues are going
From: Kevin Benton [blak...@gmail.com]
Sent: Thursday, July 30, 2015 4:22 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova, cinder, neutron] quota-update tenant-name
bug
Good point. Unfortunately the other issues
To the best of my knowledge Neutron is unable to enforce tenant quotas
using the tenant name; this should be undocumented.
What Kevin suggests also goes in this direction, even if we have to be
careful as we're making assumptions on how tenant ids are represented (if
the deployment is not using
. Performance of them
can take the hit.
Thanks,
Kevin
--
*From:* Kevin Benton
*Sent:* Wednesday, July 29, 2015 10:44:49 PM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [nova, cinder, neutron] quota-update
] [nova, cinder, neutron] quota-update tenant-name
bug
Dev lessons learned: we need to validate better our inputs and refuse to
update a tenant-id that does not exist.
This is something that has come up in Neutron discussions before. There are two
issues here:
1. Performance: it will require
This is probably affecting other people as well, so hopefully message will
avoid some headaches.
[nova,cinder,neutron] will allow you to do a quota-update using the
tenant-name (instead of tenant-id). They will also allow you to do a
quota-show tenant-name and get the expected values back.
Then
Dev lessons learned: we need to validate better our inputs and refuse to
update a tenant-id that does not exist.
This is something that has come up in Neutron discussions before. There are
two issues here:
1. Performance: it will require a round-trip to Keystone on every request.
2. If the
