I haven't used it with ipv6, but cobbler may be an easy way to replicate the mirrors
locally. we use it with ipv4 for that purpose all the time.
Thanks,
Kevin
________________________________________
From: rdo-list-bounces(a)redhat.com [rdo-list-bounces(a)redhat.com] on behalf of David Moreau
Simard [dms(a)redhat.com]
Sent: Tuesday, March 08, 2016 11:43 AM
To: Jacob Melton
Cc: rdo-list(a)redhat.com
Subject: Re: [Rdo-list] Accessing RDO Projet Repos from networks not supporting legacy IP
Hey Jacob,
Thanks for bringing this up.
tl;dr, only our stable RDO repositories have availability over IPv6
(with manual mirror selection)
Just so we're on the same wavelength, there are three different mirror
infrastructures involved for RDO:
"Trunk repositories":
1) "Delorean", ex:
http://trunk.rdoproject.org/centos7/current/delorean.repo (which
points to something like [1])
2) "Delorean-deps",
ex:http://trunk.rdoproject.org/centos7/delorean-deps.repo (which
points to something like [2])
"Stable repositories":
3) rdo-release RPM, ex:
https://www.rdoproject.org/repos/rdo-release.rpm (with points to
something like [3])
So, let's address each of the repository.
1) delorean repositories are not available on IPv6 right now and while
we'd love to make them, the underlying cloud infrastructure it's
running on does not support it yet. As soon as they provide the
support, we'll make it available. No ETA.
2) delorean-deps repositories are provided by the cbs/buildlogs mirror
infrastructure of CentOS. These are not available over IPv6 yet but
it's definitely in the team's roadmap. No ETA, however.
3) While
mirror.centos.org itself is not available over IPv6, there is
a lot of official CentOS mirrors available over IPv6 that could be
selected "manually" by editing your repository file to something such
as [4]. I've flagged this to the CentOS team and they will see what
they can do about
mirror.centos.org.
This said, I don't think we provide a straightforward and simple way
to mirror our mirrors (!). How are you doing it right now ?
Maybe a solution in the meantime would be to help the community host
their own copy of our mirrors over IPv6 for their usage.
[1]:
http://trunk.rdoproject.org/centos7/e9/0e/e90eee6e8430d72a7c7a522de5da9f6...
[2]:
http://buildlogs.centos.org/centos/7/cloud/x86_64/openstack-liberty/
[3]:
http://mirror.centos.org/centos/7/cloud/x86_64/openstack-liberty/
[4]:
http://centos.mirror.iweb.ca/7/cloud/x86_64/openstack-liberty/
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Tue, Mar 8, 2016 at 1:06 PM, Jacob Melton <JMelton(a)vtti.vt.edu> wrote:
For various reasons which are not worth getting into, I am currently
working on deploying RDO/TripleO on machines in an IPv6 only network
environment.
Currently the
rdoproject.org domain only presents legacy IP A records
and lists no IPv6 AAAA records. It would be extremely helpful if it was
possible to access the resources hosted on that domain from machines
which only have IPv6 networking available to them. As a stop-gap I've
elected to internally mirror the portions of the repos we require, but
I thought bringing up the topic of supporting the current version of IP
might be useful.
To avoid any ambiguitiy, I'm specifically attempting to access the
repos listed at
https://trunk.rdoproject.org.
Jacob Melton
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com