Open Stack

Hi Brian

Thanks for pointing that out!
The tool is able to exclude a table from a database so it's possible to
exclude by default glance.images in the config file with an explicit
message pointing to the OSSN-0075.

A more robust solution may be to hard code the glance.images exclusion and add
a boolean flag set to false by default that you may enable to delete the table.

Regards,

--
PS

Brian Rosmaita <rosmaita.fossdev at gmail.com> wrote on mar. [2019-mai-21 08:42:11 -0400]:
> On 5/9/19 11:14 AM, Pierre-Samuel LE STANG wrote:
> > Hi all,
> >
> > At OVH we needed to write our own tool that archive data from OpenStack
> > databases to prevent some side effect related to huge tables (slower response
> > time, changing MariaDB query plan) and to answer to some legal aspects.
> [snip]
>
> Please make sure your tool takes into account OSSN-0075 [0].  Please
> read [1] to understand how the glance-manage tool currently deals with
> this issue.
>
> [0] https://wiki.openstack.org/wiki/OSSN/OSSN-0075
> [1]
> https://docs.openstack.org/glance/latest/admin/db.html#database-maintenance
>
> [snip]
> > Thanks in advance for your feedbacks.
>
> Happy to help!
> brian
>
>
>