Closed Bug 1539919 Opened 6 years ago Closed 5 years ago

GCP-native job support for WTMO for writing artifacts to GCS

Categories

(Data Platform and Tools Graveyard :: Operations, enhancement, P1)

enhancement

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: whd, Assigned: hwoo)

Details

(Whiteboard: [DataOps])

We have a use case where we need to upload artifacts to GCS (currently https://github.com/fbertsch/mozilla-schema-generator). There is a notion that this should be done by a service like dataproc or similar GCP-native job. We presently run WTMO in GCP, but all jobs are run via AWS/EMR credentials. We should add support for doing things like launching dataproc jobs and whatever other methods meet our use cases.

I started setting this up but after discussion with :hwoo it seemed better to file a bug and have him hash out the details. On the shared infrastructure side, the only thing that needs to be done is to grant whatever service account that will be running the artifact generation job objectCreator access to the shared artifact bucket.

Assignee: nobody → hwoo
Priority: -- → P2
Priority: P2 → P1

No longer needed

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX

To be clear, we needed GCP-native job support, which I believe we now have via GKEPodOperator and the provisioning of kubernetes clusters in GKE. The specific instance in the description was however unneeded hence the WONTFIX.

Summary: GCP-native job support for WTMO → GCP-native job support for WTMO for writing artifacts to GCS
Product: Data Platform and Tools → Data Platform and Tools Graveyard
You need to log in before you can comment on or make changes to this bug.