mirror-announce May 2016

mirror-announce@lists.centos.org

1 participants
2 discussions

CentOS 6.8 release and mirror status
by Fabian Arrotin 25 May '16

25 May '16

Hi Mirrors Admins, As you probably know, CentOS 6.8 is now built. So expect to see some traffic when it will be released - very soon - (when the whole tree/isos will land on your mirror, and when people will then start downloading/rsyncing from your mirror). Just to let you know also that expected size is ~31Gb. After some time we'll remove the 6.7 folder and will archive it to vault.centos.org, so you'll get back that space. If you have questions, feel free to discuss that on the centos-mirror list, or in #centos-mirror, on irc.freenode.net Kind Regards, -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

[infra] : availability of msync.centos.org over IPv6 (please read)
by Fabian Arrotin 24 May '16

24 May '16

Dear Mirrors Admins, Recently we worked with the various sponsors hosting nodes for our msync network, and we were able to have enough IPv6 connectivity to publicly announce the availability of msync.centos.oorg over IPv6. Actually we have ~50% ipv6 coverage in the msync network to open it up to you. What does that mean ? if you have native ipv6 connectivity, you'll be able to automatically sync from us over ipv6 instead of ipv4, using the same rsync url ( msync.centos.org::CentOS/ - see https://wiki.centos.org/HowTos/CreatePublicMirrors) We decided to make it transparent, so we just added AAAA record[s] in our GeoIP pdns backend for msync.centos.org. Worth knowing that we're still using the same rsync target as before, and so also doing IP check for incoming connections (see initial announce mail for this : https://lists.centos.org/pipermail/centos-mirror-announce/2014-June/000015.…) This so remains in place but we'll add ipv6 addresses in the same ACL (already working and confirmed by some testers on the centos-mirror list,or #centos-mirror) What do you have to do ? normally nothing as if you advertise AAAA record for your public mirror, we have added it in the ACL already (and instead of just adding it, we added the whole /48 subnet around it, in case you're using a different IPv6 address for the outgoing connection) What if it doesn't work anymore ? feel free to answer to that thread (on the centos-mirror list only, not on the moderated centos-mirror-announce list) or reach us in #centos-mirror on irc.freenode.net and we'll verify your IPv6 address/subnet block in the ACL. What if you have IPv6 but still want to enforce rsync over IPv4 ? you can just do that at the rsync level through the "-4" parameter (man rsync) Should you encounter an issue, or should you have questions, feel free to reach us directly. -- on behalf of the CentOS sysadmin/infra team, Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mirror-announce May 2016