More permanent hosting place for Fedora/RISC-V SRPMS and RPMS #6840

Closed
opened 2018-04-07 14:47:29 +00:00 by rjones · 13 comments

The Fedora/RISC-V project is rebuilding Fedora for the RISC-V architecture:

https://fedoraproject.org/wiki/Architectures/RISC-V

Currently we're using a fedorapeople.org group account:

https://fedorapeople.org/groups/risc-v/

We have so far rebuilt large parts of Fedora 27 and provided bootable disk images.

This uses a lot of space, 97 GB so far, split approximately like this:

223M	/project/risc-v/disk-images
3.1G	/project/risc-v/logs
43G	/project/risc-v/RPMS
42G	/project/risc-v/SRPMS
5.5G	/project/risc-v/tmp
4.0G	/project/risc-v/tmp_rpm

The tmp directories are not really temporary.

There are some things we could be doing better and are working on:

  • We are not using Koji -- instead, our own home-grown autobuilder which runs jobs through qemu. This will be replaced by Koji shadow soon.
  • We have had to use newer versions of certain packages and do some bootstrapping by hand, so it's not all F27.
  • Packages from noarch SRPMS are just downloaded and copied in from Fedora Koji. We should instead be using a noarch repo, but there were some problems with that.

But essentially the problem is this uses a lot of space (although only a tiny bit of bandwidth), and it would be good to have a more permanent place for hosting this.

The Fedora/RISC-V project is rebuilding Fedora for the RISC-V architecture: https://fedoraproject.org/wiki/Architectures/RISC-V Currently we're using a fedorapeople.org group account: https://fedorapeople.org/groups/risc-v/ We have so far rebuilt large parts of Fedora 27 and provided bootable disk images. This uses a lot of space, 97 GB so far, split approximately like this: ``` 223M /project/risc-v/disk-images 3.1G /project/risc-v/logs 43G /project/risc-v/RPMS 42G /project/risc-v/SRPMS 5.5G /project/risc-v/tmp 4.0G /project/risc-v/tmp_rpm ``` The `tmp` directories are not really temporary. There are some things we could be doing better and are working on: * We are not using Koji -- instead, our own home-grown autobuilder which runs jobs through qemu. This will be replaced by Koji shadow soon. * We have had to use newer versions of certain packages and do some bootstrapping by hand, so it's not all F27. * Packages from noarch SRPMS are just downloaded and copied in from Fedora Koji. We should instead be using a noarch repo, but there were some problems with that. But essentially the problem is this uses a lot of space (although only a tiny bit of bandwidth), and it would be good to have a more permanent place for hosting this.

I think we can store this on alt... ie, dl.fedoraproject.org/pub/alt/risc-v

Who will be uploading content there? we will need to add them to a group for access and make sure your ssh keys are setup in fas right.

I think we can store this on alt... ie, dl.fedoraproject.org/pub/alt/risc-v Who will be uploading content there? we will need to add them to a group for access and make sure your ssh keys are setup in fas right.
Author

We have a group for this in FAS:

https://admin.fedoraproject.org/accounts/group/view/risc-v

Only 3 members so far.

We have a group for this in FAS: https://admin.fedoraproject.org/accounts/group/view/risc-v Only 3 members so far.

Are all of them likely to need to upload? We would prefer to keep it to as small a number of people as possible...

Are all of them likely to need to upload? We would prefer to keep it to as small a number of people as possible...
Author

It can be just me if that makes things easier.

It can be just me if that makes things easier.
Author

I should have said the FAS group above is connected to the fedorapeople.org hosting space.

I should have said the FAS group above is connected to the fedorapeople.org hosting space.

ok. I have added you to the hosted content group.

You should now be able to login to 'secondary01.fedoraproject.org' with the ssh key that you have in fas. From there you should have access to /srv/web/pub/alt/risc-v/

If some of the other folks in the group need to upload things there, let me know and I can get them added.

Let us know in general if there's any issues with that space...

Happy arch bringup.

ok. I have added you to the hosted content group. You should now be able to login to 'secondary01.fedoraproject.org' with the ssh key that you have in fas. From there you should have access to /srv/web/pub/alt/risc-v/ If some of the other folks in the group need to upload things there, let me know and I can get them added. Let us know in general if there's any issues with that space... Happy arch bringup.

Metadata Update from @kevin:

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

I would like to request access to the new storage location. I am part of RISC-V FAS group.

I would like to start mirroring data (incl. repo and disk images) from the current Fedora/RISC-V infrastructure (which is not hosted in Fedora infra.)

I would like to request access to the new storage location. I am part of RISC-V FAS group. I would like to start mirroring data (incl. repo and disk images) from the current Fedora/RISC-V infrastructure (which is not hosted in Fedora infra.)
Author

Yes please let us know how we can add davidlt to this.

Yes please let us know how we can add davidlt to this.

Metadata Update from @smooge:

  • Issue priority set to: Next Meeting
  • Issue tagged with: request-for-resources
**Metadata Update from @smooge**: - Issue priority set to: Next Meeting - Issue tagged with: request-for-resources

I have added him to the group. He should be able to login there in 10-20min.

I have added him to the group. He should be able to login there in 10-20min.

I think, the location moved to "/srv/pub/alt/risc-v" and I tried to touch a new file I got "Permission denied".

Shouldn't the gid be "risc-v" for the directory?

I think, the location moved to "/srv/pub/alt/risc-v" and I tried to touch a new file I got "Permission denied". Shouldn't the gid be "risc-v" for the directory?

I don't know how it would have changed, but it's fixed now.

I don't know how it would have changed, but it's fixed now.
Sign in to join this conversation.
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/fedora-infrastructure#6840
No description provided.