#8564 registry.fp.o will soon run out of space
Closed: Fixed 4 years ago by kevin. Opened 4 years ago by cverna.

Describe what you would like us to do:

Currently the nfs storage used by registry.fp.o is 81% full and will soon run out of space.

ntap-phx2-c01-fedora01-nfs.storage.phx2.redhat.com:/oci_registry  285G  230G   56G  81% /srv/registry

I used to cleanup the containers which reach eol but now most of the content on registry.fp.o are flatpaks.

@Kalev @otaylor Can we delete or archive older flatpaks version ? Or do we have another strategy to avoid running out of space on the registry ?

@Kevin Could we add more space on the nfs share ?


When do you need this to be done by? (YYYY/MM/DD)



Metadata Update from @cverna:
- Issue priority set to: Waiting on External (was: Needs Review)

4 years ago

Yes, we can easily add space, just let me know when and how much.

Yes, we can easily add space, just let me know when and how much.

I think we could double the current disk size. Would the outage be long ? If not I think we can schedule it whenever it is convenient to us.

I would like to learn how to do that if we could work on this together that would be great :-)

Also I still think we need to have a policy to either delete or archive some of the flatpak because we are going to hit the same problem in the future.

How do I see what flatpaks are taking up space? If it's more than expected, perhaps nothing is removing older version when a flatpak is updated?

The only flatpaks that we need to keep should be those that are referenced from https://registry.fedoraproject.org/index/flatpak.json and https://registry.fedoraproject.org/index/flatpak-testing.json

How do I see what flatpaks are taking up space? If it's more than expected, perhaps nothing is removing older version when a flatpak is updated?

This is not that straight forward, you need to query the registry API to get back the size of each image:tag blob.

I don't if we remove older version when there is an update, maybe @otaylor would know.

The only flatpaks that we need to keep should be those that are referenced from https://registry.fedoraproject.org/index/flatpak.json and https://registry.fedoraproject.org/index/flatpak-testing.json

Yes, we can easily add space, just let me know when and how much.

I think we could double the current disk size. Would the outage be long ? If not I think we can schedule it whenever it is convenient to us.

So after talking with @kevin. There would be no outage so let's go and double the registry size that should leave us a little bit of time to find a way to keep the storage under control :smile:

I would like to learn how to do that if we could work on this together that would be great :-)
Also I still think we need to have a policy to either delete or archive some of the flatpak because we are going to hit the same problem in the future.

[11:24:51] <nirik> ntap-phx2-c01-fedora01::> df -h oci_registry
[11:24:51] <nirik> Filesystem total used avail capacity Mounted on
[11:24:51] <nirik> /vol/oci_registry/ 285GB 234GB 50GB 82% /oci_registry
[11:25:11] <nirik> ntap-phx2-c01-fedora01::> volume modify -volume oci_registry -size 600GB
[11:25:21] <nirik> ntap-phx2-c01-fedora01::> df -h oci_registry
[11:25:21] <nirik> Filesystem total used avail capacity Mounted on
[11:25:21] <nirik> /vol/oci_registry/ 570GB 234GB 335GB 41% /oci_registry
[11:25:25] <nirik> done

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata