Create a Route53 hosted zone for CI-private hgweb mirrors
Categories
(Developer Services :: Mercurial: hg.mozilla.org, enhancement)
Tracking
(Not tracked)
People
(Reporter: sheehan, Assigned: sheehan)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
To support easier DNS resolution of private hgweb mirrors running in AWS/GCP,
we plan to create a Route53 hosted zone and associate it with Taskcluster VPC
in various AWS regions. The run-task
script will then create the correct
hostname to clone/pull down from by prepending the current AWS region to the
hostname and querying from there. For example, a host attempting to clone from
the private mirrors in us-west-2 will query http://us-west-2.hgmointernal.com,
and the hosted zone will correctly resolve to an instance running in that
region.
Assignee | ||
Comment 1•6 years ago
|
||
To route traffic from Taskcluster workers to the correct region, we will use a Route53 private hosted zone that resolves to the CI-only hgweb instances. This commit adds a hosted zone and test record to the Terraform `ci-only` module. The hostname selected is "hgmointernal.com". For now, we manage this resource from the CI-only module. In the future we will likely need to refactor this resource out and into the "main" module to support multiple regions with the same hosted zone, but that is fairly straightforward.
Assignee | ||
Comment 2•6 years ago
|
||
The Route53 docs seem to indicate we will need this for DNS resolution to work. We don't actually need to run any queries for `hgmointernal.com` from the Mercurial VPC, but it doesn't hurt to have.
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Pushed by cosheehan@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/48d2b14ec6ef
terraform: add Route53 hosted zone and hgmointernal
DNS record r=bstack
https://hg.mozilla.org/hgcustom/version-control-tools/rev/01ed676059c7
terraform: enable DNS hostnames in ci-only vpc r=bstack
Description
•