Google Doc doesn't seem to be shared with dev@. Can anybody double-check? On Wed, Aug 28, 2019 at 7:36 AM Hannah Jiang <hannahji...@google.com> wrote:
> add dev@ > > On Tue, Aug 27, 2019 at 9:29 PM Hannah Jiang <hannahji...@google.com> > wrote: > >> Thanks for commenting and discussions. >> I created a Google Docs >> <https://docs.google.com/document/d/1LOraxUHdmuykgOPsjRC00iDqvSapoCuCjZcZm-Vh8o0/edit?usp=sharing> >> for >> easy commenting and reviewing. From this moment, all changes will be >> updated to the Google Docs and I will sync to wiki after finalize all plans. >> >> Thanks, >> Hannah >> >> On Tue, Aug 27, 2019 at 9:24 PM Ahmet Altay <al...@google.com> wrote: >> >>> Hi datapls-engprod, >>> >>> I have a question. Do you know what would it take to create a new gcp >>> project similar to apache-beam-testing for purposes of distributing gcr >>> packages? We can use the same billing account. >>> >>> Hannah, Robert, depending on the complexity of creating another gcp >>> project we can go with that, or simply create a new bintray account. Either >>> way would give us a clean new project to publish artifacts. >>> >>> Ahmet >>> >>> ---------- Forwarded message --------- >>> From: Robert Bradshaw <rober...@google.com> >>> Date: Tue, Aug 27, 2019 at 6:48 PM >>> Subject: Re: Improve container support >>> To: dev <dev@beam.apache.org> >>> >>> >>> On Tue, Aug 27, 2019 at 6:20 PM Ahmet Altay <al...@google.com> wrote: >>> > >>> > On Tue, Aug 27, 2019 at 5:50 PM Robert Bradshaw <rober...@google.com> >>> wrote: >>> >> >>> >> On Tue, Aug 27, 2019 at 3:35 PM Hannah Jiang <hannahji...@google.com> >>> wrote: >>> >> > >>> >> > Hi team >>> >> > >>> >> > I am working on improving docker container support for Beam. We >>> would like to publish prebuilt containers for each release version and >>> daily snapshot. Current work focuses on release images only and it would be >>> part of the release process. >>> >> >>> >> This would be great! >>> >> >>> >> > The release images will be pushed to GCR which is publicly >>> accessible(pullable). We will use the following locations. >>> >> > Repository: gcr.io/beam >>> >> > Project: apache-beam-testing >>> >> >>> >> Given that these are release artifacts, we should use a project with >>> >> more restricted access than "anyone who opens a PR on github." >>> > >>> > >>> > We have two options: >>> > - gcr.io works based on the permissions of the gcs bucket that is >>> backing it. GCS supports bucket only permissions. These permissions needs >>> to be explicitly granted and the service accounts used by jenkins jobs does >>> not have these explicit permissions today. >>> > - we can create a new project in gcr, bintray or anything else that >>> offers the same service. >>> >>> I think the cleanest is to simply have a new project whose membership >>> consists of (interested) PMC members. If we have to populate this >>> manually I think that'd still be OK as the churn is quite low. >>> >> -- Cheers, Gleb
