Hey all,
Fedora 29 has been staged and should now be available at
/pub/fedora/linux/releases//29/ /pub/alt/releases//29/ /pub/fedora-secondary/releases//29/
it is 454G in pub/fedora, 15G in pub/alt, 294G in pub/fedora-secondary and the rpms are hardlinked to pub/fedora/linux/development/29/Everything/
Our release is Tuesday the 30th of October 2018, at 14:00 UTC.
Thanks, Mohan Boddu Fedora Release Engineering
Is rsync://download-ib01.fedoraproject.org/fedora-enchilada/linux/ no longer the place to grab Fedora pre-release? My private mirror is part of Fedora Mirror Manager and it should be in various ACLs in place for pre-release access to Fedora content, but I was syncing from the ib01 server and I never got Fedora 29 staged. Even yesterday after 14:00 UTC, the download-ib01 server did not have Fedora 29.
What is the proper Tier 0 or Tier 1 server where I should grab releases before they are released so I have them the minute the bit-flip is done? Thanks.
/Brian/
On 10/26/18, 3:02 PM, "Mohan Boddu" mboddu@bhujji.com wrote:
Hey all,
Fedora 29 has been staged and should now be available at
/pub/fedora/linux/releases//29/
/pub/alt/releases//29/
/pub/fedora-secondary/releases//29/
it is 454G in pub/fedora, 15G in pub/alt, 294G in pub/fedora-secondary and the rpms are hardlinked to pub/fedora/linux/development/29/Everything/
Our release is Tuesday the 30th of October 2018, at 14:00 UTC.
Thanks,
Mohan Boddu
Fedora Release Engineering
On Wed, 31 Oct 2018 at 10:14, Brian Long (brilong) brilong@cisco.com wrote:
Is rsync://download-ib01.fedoraproject.org/fedora-enchilada/linux/ no longer the place to grab Fedora pre-release? My private mirror is part of Fedora Mirror Manager and it should be in various ACLs in place for pre-release access to Fedora content, but I was syncing from the ib01 server and I never got Fedora 29 staged. Even yesterday after 14:00 UTC, the download-ib01 server did not have Fedora 29.
Fedora-enchilada does not get pre-release. Only fedora-enchilada0 for various tier0 systems gets it for pre-release.
The data was staged on download-ib01 over the weekend, but I don't know why the switch did not turn over at 14:00. I expect it was between runs and showed up at the next cron job.
As it is, we need to work on what hosts have tier0 access and we also need to work on who is on the mirror admin list as many people who are registered mirrors do not have subscriptions here.
What is the proper Tier 0 or Tier 1 server where I should grab releases before they are released so I have them the minute the bit-flip is done? Thanks.
To get them before the bit-flip you need to be a tier0 server. If you were able to get them before, then your site IP must have changed as we have a list of ips which are only IP related (versus hostname). Can you give me the IP address the server should show up as?
/Brian/
On 10/26/18, 3:02 PM, "Mohan Boddu" mboddu@bhujji.com wrote:
Hey all,
Fedora 29 has been staged and should now be available at
/pub/fedora/linux/releases//29/
/pub/alt/releases//29/
/pub/fedora-secondary/releases//29/
it is 454G in pub/fedora, 15G in pub/alt, 294G in pub/fedora-secondary and the rpms are hardlinked to pub/fedora/linux/development/29/Everything/
Our release is Tuesday the 30th of October 2018, at 14:00 UTC.
Thanks,
Mohan Boddu
Fedora Release Engineering
Mirror-admin mailing list -- mirror-admin@lists.fedoraproject.org To unsubscribe send an email to mirror-admin-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/mirror-admin@lists.fedoraproje...
Hi. As a new member of the mirror community, I would like to ask how to check presence in ACL.
Currently we are a tier2 mirror, but would like to help as a tier1 mirror. Could you please advice on that?
regards
ariel
El 31/10/18 a las 11:43, Stephen John Smoogen escribió:
On Wed, 31 Oct 2018 at 10:14, Brian Long (brilong) brilong@cisco.com wrote:
Is rsync://download-ib01.fedoraproject.org/fedora-enchilada/linux/ no longer the place to grab Fedora pre-release? My private mirror is part of Fedora Mirror Manager and it should be in various ACLs in place for pre-release access to Fedora content, but I was syncing from the ib01 server and I never got Fedora 29 staged. Even yesterday after 14:00 UTC, the download-ib01 server did not have Fedora 29.
Fedora-enchilada does not get pre-release. Only fedora-enchilada0 for various tier0 systems gets it for pre-release.
The data was staged on download-ib01 over the weekend, but I don't know why the switch did not turn over at 14:00. I expect it was between runs and showed up at the next cron job.
As it is, we need to work on what hosts have tier0 access and we also need to work on who is on the mirror admin list as many people who are registered mirrors do not have subscriptions here.
What is the proper Tier 0 or Tier 1 server where I should grab releases before they are released so I have them the minute the bit-flip is done? Thanks.
To get them before the bit-flip you need to be a tier0 server. If you were able to get them before, then your site IP must have changed as we have a list of ips which are only IP related (versus hostname). Can you give me the IP address the server should show up as?
/Brian/
On 10/26/18, 3:02 PM, "Mohan Boddu" mboddu@bhujji.com wrote:
Hey all,
Fedora 29 has been staged and should now be available at
/pub/fedora/linux/releases//29/
/pub/alt/releases//29/
/pub/fedora-secondary/releases//29/
it is 454G in pub/fedora, 15G in pub/alt, 294G in pub/fedora-secondary and the rpms are hardlinked to pub/fedora/linux/development/29/Everything/
Our release is Tuesday the 30th of October 2018, at 14:00 UTC.
Thanks,
Mohan Boddu
Fedora Release Engineering
Mirror-admin mailing list -- mirror-admin@lists.fedoraproject.org To unsubscribe send an email to mirror-admin-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/mirror-admin@lists.fedoraproje...
"asy" == ariel sabiguero yawelak asabigue@fder.edu.uy writes:
asy> Hi. As a new member of the mirror community, I would like to ask asy> how to check presence in ACL.
Since anything but the actual configuration would probably be out of date, you might as well go straight to the source and look at the rsync server configuration in ansible.
The rsyncd.conf file is templated from: https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/rsyncd/...
The list of IP addresses that are templated into the ACL comes from https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/inventory/gro...
As for what constitutes a tier1 mirror, there's a document at https://fedoraproject.org/wiki/Infrastructure/Mirroring/Tiering but some of it is out of date. (You need way more than 1TB of storage, for example.)
- J<
El 1/11/18 a las 16:41, Jason L Tibbitts III escribió:
Since anything but the actual configuration would probably be out of date, you might as well go straight to the source and look at the rsync server configuration in ansible.
The rsyncd.conf file is templated from: https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/rsyncd/...
The list of IP addresses that are templated into the ACL comes from https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/inventory/gro...
As for what constitutes a tier1 mirror, there's a document at https://fedoraproject.org/wiki/Infrastructure/Mirroring/Tiering but some of it is out of date. (You need way more than 1TB of storage, for example.)
Well, we already allocated more than that to Fedora (enchilada):
espejito:/zp0/mirrors # du -sh fedora/ 3,2T fedora/
We are connected to Internet2 through RAU, but, we offer the mirror to our ISP network. We plan to offer it too through RAU/Internet2
Shall we go for Tier1 or get a "good" mirror source?
- J<
On 10/31/18, 10:43 AM, "Stephen John Smoogen" smooge@gmail.com wrote:
On Wed, 31 Oct 2018 at 10:14, Brian Long (brilong) brilong@cisco.com wrote: > > Is rsync://download-ib01.fedoraproject.org/fedora-enchilada/linux/ no longer the place to grab Fedora pre-release? My private mirror is part of Fedora Mirror Manager and it should be in various ACLs in place for pre-release access to Fedora content, but I was syncing from the ib01 server and I never got Fedora 29 staged. Even yesterday after 14:00 UTC, the download-ib01 server did not have Fedora 29.
Fedora-enchilada does not get pre-release. Only fedora-enchilada0 for various tier0 systems gets it for pre-release.
The data was staged on download-ib01 over the weekend, but I don't know why the switch did not turn over at 14:00. I expect it was between runs and showed up at the next cron job.
As it is, we need to work on what hosts have tier0 access and we also need to work on who is on the mirror admin list as many people who are registered mirrors do not have subscriptions here.
Now I remember the problem. I had to move my private mirror to an RFC1918 IP that gets NAT'd by our corporate network. This means my server is coming from any one of a number of IP's in a /26 subnet. I forgot that since I reip'd the server, I had to forgo the pre-bitflip content since I doubted you'd add a NAT pool subnet into the ACL. __
I apologize for the noise.
/Brian/
Sorry for coming in late here; I'm still behind on email.
"SJS" == Stephen John Smoogen smooge@gmail.com writes:
JS> The data was staged on download-ib01 over the weekend, but I don't SJS> know why the switch did not turn over at 14:00. I expect it was SJS> between runs and showed up at the next cron job.
I don't have hard evidence because I didn't watch the release this time, but I suspect that the file lists were not regenerated immediately after the bit flip happened. That means that hosts using quick-fedora-mirror (which as I understand it includes download-ib01) would not have any way to notice that the content had changed. They would have noticed the next time the file lists changed, which was probably the next updates push.
https://pagure.io/releng/issue/7477 is relevant but maybe it's been solved in the meantime.
- J<
mirror-admin@lists.fedoraproject.org