On Thu, Nov 4, 2021 at 8:13 AM Pavel Raiskup <praiskup@xxxxxxxxxx> wrote:
On Thursday, November 4, 2021 8:56:33 AM CET Pavel Raiskup wrote:
> On Wednesday, October 20, 2021 6:44:20 PM CET Kevin Fenzi wrote:
> > not up/reachable on it's dns name/ip) would you be ok using that as
> > well? Or should we seperate out copr from maintainer-test/proxies?
>
> Definitely, it would simplify our life. Actually, very soon we'll have to
> migrate our servers from F33 to F35 so we would benefit from this change.
One possible problem for Copr (or any other IPv6 enabled service) is the
absence of elastic IPv6 addresses:
https://docs.pagure.org/copr.copr/how_to_upgrade_persistent_instances.html#fix-ipv6-dns-records
So we have to go to dns.git and update AAAA records manually when spawning
the infra machines...
There is a possibility to automate this within AWS but may require a change of url.
We could delegate a subdomain to route53, something like copr-aws.fedoraproject.org
then when the instances are created we can get the ip6/4 address as an output and update
route53 with <serverx>.copr-aws.fedoraproject.org as part of the playbook.
An example of which we use in arc projects: ec2_instance_create
Mark
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
