1566048 - Static code coverage website bucket on AWS or GCP

Status: RESOLVED FIXED

(Cloud Services :: Operations: Miscellaneous, task)

Description

[Bastien Abadie [:bastien]]

I'm working on the code coverage frontend (a Javascript application), and would like to deploy it on a simple storage bucket (i'm used to S3 + Cloudfront, but i'm open to storing it on GCP if you have an alternative solution).

I need 2 buckets to support 2 deployment environments:

• code-coverage-production
• code-coverage-testing

The production domain name would be cov.moz.tools: this domain name is currently managed in https://github.com/mozilla-releng/build-cloud-tools through Route 53 .

Comment 1

[Habibullah Pagarkar (use Slack)]

Bastien, static sites are better suited for AWS with S3 and CloudFront, we'll keep them there.

What's the urgency behind this request?

Comment 2

[Bastien Abadie [:bastien]]

I'm totally okay with AWS as we already have S3 integration in our deployment tools for code-review's frontend.

I need those buckets to finish the code-coverage migration from release-services: this is the last step needed.

Would it be possible to get them this week ? If you already have the static-analysis buckets configuration in Terraform or another tool, you may be able to clone them for code-coverage ?

Comment 3

[Habibullah Pagarkar (use Slack)]

This week will be tough as we have a few high priority projects (subscription platform launch, premium services launch) and PTO coming up. At present we are running close to 2 weeks out. Please assign this to :oremj if that's acceptable.

Comment 4

[Bastien Abadie [:bastien]]

I've assigned the bug to Jeremy. Thanks Habibullah, and good luck for shipping these projects !

Comment 5

[Bastien Abadie [:bastien]]

Any update on this ?

Comment 6

[Jeremy Orem [:oremj]]

Please add the following records:

cov.moz.tools. IN NS ns-534.awsdns-02.net.
cov.moz.tools. IN NS ns-1350.awsdns-40.org.
cov.moz.tools. IN NS ns-1745.awsdns-26.co.uk.
cov.moz.tools. IN NS ns-416.awsdns-52.com.

I should be able to complete this pretty quickly after that is done. It's blocking the cert issuance.

Comment 7

[Bastien Abadie [:bastien]]

Could you update the production domain name to coverage.moz.tools ? We now have access to that subdomain, after moving the api to api.coverage.moz.tools

I published a pull-request on build-cloud-tools where our DNS is currently managed : https://github.com/mozilla-releng/build-cloud-tools/pull/391/files

Jeremy, does that work for you ? Could you also merge & apply that PR ?

Thanks.

Comment 8

[Jeremy Orem [:oremj]]

The list of nameservers for that coverage.moz.tools is:

ns-1151.awsdns-15.org.
ns-584.awsdns-09.net.
ns-1748.awsdns-26.co.uk.
ns-60.awsdns-07.com.

I don't have access to apply or merge in the mozilla-releng space.

Comment 9

[Jeremy Orem [:oremj]]

I'm out next week, so if we can get this sorted out by tomorrow, that'd be great.

Comment 10

[Bastien Abadie [:bastien]]

I updated the pull request on build-cloud-tools using those new NS records.

Jake, could you review & apply those changes by tomorrow ? Sorry for the late notice... Thanks !

Comment 11

[Jake Watkins [:dividehex]]

(In reply to Bastien Abadie [:bastien] from comment #10)

I updated the pull request on build-cloud-tools using those new NS records.

Jake, could you review & apply those changes by tomorrow ? Sorry for the late notice... Thanks !

Done :-)

Comment 12

[Jeremy Orem [:oremj]]

Production:

"website_bucket_name" = "codecoverage-prod-site-static-website"
"dns_name" = "coverage.moz.tools"

Testing:

"dns_name" = "codecoverage-testing.stage.mozaws.net"
"website_bucket_name" = "codecoverage-testing-site-static-website"

I've e-mailed you access keys GPG encrypted with key 0xF5F60CAA5BB69CAA (from phonebook).

Comment 13

[Bastien Abadie [:bastien]]

Thank you Jeremy, i was able to use those settings & access keys to deploy both testing and production sites.