infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <>
Subject [jira] [Resolved] (INFRA-16859) Explore the possibilities of GeoSLB for projects like ATS
Date Sun, 30 Dec 2018 02:47:00 GMT


Chris Lambertus resolved INFRA-16859.
    Resolution: Won't Fix

Costs of managing geoDNS for via route53 are prohibitive. I don't see any options
other than self-hosting geo for a.o, and we've already kind of given up on that for various

> Explore the possibilities of GeoSLB for projects like ATS
> ---------------------------------------------------------
>                 Key: INFRA-16859
>                 URL:
>             Project: Infrastructure
>          Issue Type: New Feature
>          Components: DNS
>            Reporter: Leif Hedstrom
>            Assignee: Chris Lambertus
>            Priority: Minor
> We have and
hosted by an ATS instance. In order to expand testing of our software, and also provide a
better user experience, I'd like to put up parent proxies in Asia and Europe. This allows
for content to be cached locally as well as pooling connections over long distances (and test
new features of ATS :).
> In order to do so, we would need some basic GeoSLB DNS feature. For example, AWS's Route
53 does provide such policies:
> They call it Geolocation routing policy and Geoproximity routing policy. I'm not sure
exactly which one we would use though.
> One concern here would be if they require all end-points to be on AWS availability zones.
If that's the case, we would also have to move these sites to AWS hosted VMs (which is currently
not the case).

This message was sent by Atlassian JIRA

View raw message