1703615 - Request to provision Rally Study: Your Time Online and "Doomscrolling"

Status: RESOLVED FIXED

(Firefox :: Pioneer, task)

Description

[Hamilton]

+++ This bug was initially created as a clone of Bug #1693305 +++

Hello,

We are planning on launching the Rally team's first authored study. We'd like to provision a new schema+env+keys for this.

schema
measurements.1.schema.json

namespace
We'd like to use rally-study-zero-one as the namespace.

analysis environment access:
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]

:than: will confirm these details. Please let me know if I can answer any questions.

Comment 1

[Wesley Dawson [:whd]]

:amiyaguchi will be responsible for filing the MPS PR.

Comment 2

[Marissa Gorlick]

please also add [e-mail] to the analysis environment. To be confirmed by :than:

Comment 3

[Wesley Dawson [:whd]]

Current list:

[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail] (originally misspelled)
[e-mail]

Comment 4

[Wesley Dawson [:whd]]

From a management perspective, the study name rally-study-zero-one is too long to fit in a GCP project name (30 chars), when combined with the standard project prefix moz-fx-data-rally-. As such, we will need to come up with another project naming convention (the current one for internal studies yielding moz-fx-data-rally-study-zero-one). One solution is to drop study- from the namespace, yielding moz-fx-data-rally-zero-one. A different solution might be to avoid spelling out numbers and using a namespace that is descriptive as to the intent of the study e.g. moz-fx-data-rally-time-online.

For external partner studies, we have the convention of part 9 of https://bugzilla.mozilla.org/show_bug.cgi?id=1677567#c4. We'll likely need to adopt something similar (i.e. with salt) in any case for internal studies with unavoidably long names. One argument might be to treat mozilla as a partner like any other, creating e.g. namespace rally-mozilla-study-zero-one/rally-mozilla-time-online and project id moz-fx-data-rally-mozilla-a60f.

I'd like opinions on which option (or another) is most acceptable before proceeding with study provisioning.

Comment 5

[Ted Han]

Okay, let's go with rally-zero-one then. Thank you very much!

Comment 6

[Wesley Dawson [:whd]]

The project moz-fx-data-rally-zero-one and key:

{
  "crv": "P-256",
  "kid": "zero-one",
  "kty": "EC",
  "x": "edhPpqhgK9dD7NaqhQ7Ckw9sU6b39X7XB8HnA366Rjs",
  "y": "GzsfM19n-iH-DVR0iKEoA8BE2CFF46wR__siJ3SdiNs"
}

have been provisioned via https://github.com/mozilla-services/cloudops-infra/pull/3006/files. GCP has been contacted to enable DNS restrictions. Once that PR is merged I will ask :oremj to add the project to the secure perimeter, after which it will be usable for analysis.

This project is now in the same state as bug #1698913 (waiting on provisioning BQ resources via a schemas PR to MPS). We'll also want to land the dependent bug's PR before actually ingesting any data for this study.

Comment 7

[Ted Han]

Hooray! Thank you so much!

Comment 8

[Hamilton]

:whd: I don't have access to that GitHub PR. Can you let us know in this bug once that PR is merged?

Comment 9

[Wesley Dawson [:whd]]

All PRs except the schemas PR have been merged and deployed. The schemas PR, assuming it is written today or Monday, will likely go out Monday during US business hours, after which I will close this bug.

Comment 10

[GitHub Bugzilla PR Linker]

Attachment: Link to GitHub pull-request: https://github.com/mozilla-services/mozilla-pipeline-schemas/pull/670

Comment 11

[Anthony Miyaguchi [:amiyaguchi]]

Schema has been merged against the default branch of mozilla-pipeline-schemas.

Comment 12

[GitHub Bugzilla PR Linker]

Attachment: Link to GitHub pull-request: https://github.com/mozilla-services/mozilla-pipeline-schemas/pull/671

Comment 13

[Anthony Miyaguchi [:amiyaguchi]]

After some discussion with :hamilton, this schema may not be correct. I've reverted this and will follow up with the correct schema.

Comment 14

[GitHub Bugzilla PR Linker]

Attachment: Link to GitHub pull-request: https://github.com/mozilla/mozilla-schema-generator/pull/191

Comment 15

[GitHub Bugzilla PR Linker]

Attachment: Link to GitHub pull-request: https://github.com/mozilla-services/mozilla-pipeline-schemas/pull/672

Comment 16

[Wesley Dawson [:whd]]

Schemas have been deployed to the production project.