kevin reported a new issue against the project: `releng` that you are following:
``
Later this year our storage provider is moving to newer appliances. These appliances will
only have 2 grades of storage: sata disks or flash. The idea is that anything that
doesn't require access very often or speed can be on the sata disks, and anything that
is accessed/used a lot can be on the flash storage.
Currently our fedora_koji volume is 45TB and growing.
Currently our fedora_ftp master mirror volume is 12TB.
In order to take advantage of the new flash storage we need to seperate out our data by
usage.
For fedora_ftp we should easily be able to split out the archive part. That ends up being
about 6.5TB.
Even if that data is accessed a fair bit having archive and non archive would help us
better be able to fit into flash with it.
For fedora_koji we can take advantage of koji's "volumes" support. Basically
we make a new volume and mount it on /mnt/koji/koji_archive and then tell koji about that
volume and then we script something that moves builds over to that volume. We could start
with the oldest fc6 builds and move up from there. I am not sure how much space all the
EOL releases will get us, we will just have to wait and see, but it should help reduce the
massive size and make it more possible to get the active set into flash.
So, actions here:
* Run this by koji deveopers and see if it all makes sense and is implemented as we think.
* Need to create volumes (I can do this)
* need to tell koji about them (I can do this too)
* Need a script to identify all non garbage collected builds for all EOL releases and run
'koji set build-volume' on each to move those builds to the new volume.
We should be able to start on this after freeze...
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6805