Open Stack

To whom it may concern,

We were hoping to propose something akin to filtering/dynamic listing to the horizon team in order to rectify the issue.
In turn, for the keystone team, we were wondering whether there is anything we can do with the API in order to simplify the aforementioned horizon proposal; we are hoping to get both teams on board.
Subsequently, should we reach an agreement, we would be more than happy to create a bug report, follow that with (a) blueprint(s) and proceed immediately; unless any other terms of engagement are amicable.

Please let me know how everyone would like to proceed.
Best Regards,
Sergey Drozdov
Software Engineer 
The Hut Group

> On 19 Jul 2022, at 14:47, Danny Webb <Danny.Webb at thehutgroup.com> wrote:
> 
> It was a conscious decision by the keystone team back in 2015 as far as we can tell.  There was a large discussion on the mailing list regarding this that seemed to have left this issue unresolved (most specifically around user pagination, but this seems to have affected project / domain elements as well).  
> 
> https://lists.openstack.org/pipermail/openstack-dev/2015-August/thread.html#72082 <https://lists.openstack.org/pipermail/openstack-dev/2015-August/thread.html#72082>
> 
> Ultimately what we're seeking to do is start a discussion within the keystone / horizon (and potentially skyline) community about how we can rectify the current issues we're facing around the usability of the UX portion of keystone elements.  Eg, if pagination isn't the way the keystone community wants to go should we look at instead having dynamic filtering instead in the UI?  Are there any other options that people can think of that might be a better way forward?
> From: Julia Kreger <juliaashleykreger at gmail.com <mailto:juliaashleykreger at gmail.com>>
> Sent: 19 July 2022 14:21
> To: Danny Webb <Danny.Webb at thehutgroup.com <mailto:Danny.Webb at thehutgroup.com>>
> Cc: Dmitriy Rabotyagov <noonedeadpunk at gmail.com <mailto:noonedeadpunk at gmail.com>>; openstack-discuss <openstack-discuss at lists.openstack.org <mailto:openstack-discuss at lists.openstack.org>>
> Subject: Re: [dev] directions to the right project team
>  
> CAUTION: This email originates from outside THG
> 
> On Tue, Jul 19, 2022 at 3:44 AM Danny Webb <Danny.Webb at thehutgroup.com> wrote:
> >
> > Unfortunately pagination was removed from keystone in the v3 api and as far as we're aware it was never re-added.
> >
> 
> This is quite concerning, and a quick look at the code confirms it.
> Mostly. There are remnants of "hints" and SQL Query filtering, but the
> internal limit is just a truncation which seems bad as well.
> 
> https://github.com/openstack/keystone/blame/d7b1d57cae738183f8d85413e942402a8a4efb31/keystone/server/flask/common.py#L675 <https://github.com/openstack/keystone/blame/d7b1d57cae738183f8d85413e942402a8a4efb31/keystone/server/flask/common.py#L675>
> 
> This seems like a fundamental performance oriented feature because the
> overhead in data conversion can be quite a bit when you have a large
> number of well... any objects being returned from a database.
> 
> Does anyone know if a bug is open for this issue?
> Danny Webb 
> Principal OpenStack Engineer
> The Hut Group <http://www.thehutgroup.com/> 
> 
> Tel: 
> Email: Danny.Webb at thehutgroup.com <mailto:Danny.Webb at thehutgroup.com>
> 
> For the purposes of this email, the "company" means The Hut Group Limited, a company registered in England and Wales (company number 6539496) whose registered office is at Fifth Floor, Voyager House, Chicago Avenue, Manchester Airport, M90 3DQ and/or any of its respective subsidiaries. 
> 
> Confidentiality Notice 
> This e-mail is confidential and intended for the use of the named recipient only. If you are not the intended recipient please notify us by telephone immediately on +44(0)1606 811888 or return it to us by e-mail. Please then delete it from your system and note that any use, dissemination, forwarding, printing or copying is strictly prohibited. Any views or opinions are solely those of the author and do not necessarily represent those of the company. 
> 
> Encryptions and Viruses 
> Please note that this e-mail and any attachments have not been encrypted. They may therefore be liable to be compromised. Please also note that it is your responsibility to scan this e-mail and any attachments for viruses. We do not, to the extent permitted by law, accept any liability (whether in contract, negligence or otherwise) for any virus infection and/or external compromise of security and/or confidentiality in relation to transmissions sent by e-mail. 
> 
> Monitoring 
> Activity and use of the company's systems is monitored to secure its effective use and operation and for other lawful business purposes. Communications using these systems will also be monitored and may be recorded to secure effective use and operation and for other lawful business purposes.
> 
> hgvyjuv

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20220720/8f12d1a3/attachment-0001.htm>