The purpose of this document is to allow our client`s Data Science team prepare and deploy their models in a Google Cloud environment.
...
| Note |
|---|
Your user email (as the requester) will be given the Editor, Owner and Project Billing Manager role. Share access to other people who need access to the project. |
| Tip |
|---|
The application is launched in a Virtual Machine in the project. The commands from commands.txt are executed. Additionally, you can SSH on the VM and update/check content. |
...
BigQuery Data Editor : <client>_lab, <client>_views
BigQuery Data Viewer : <client>_core, <client>_stage, <client>_reports, <client>_intelligence
If your application is meant to edit the subscriber properties, get familiar with the structure of the subscriber properties https://boxalino.atlassian.net/wiki/spaces/BPKB/pages/303825148/subscriber+properties
1. Project Deploy
Required Information
Create a project in the Boxalino ecosystem by completing the form https://gcp-deploy-du3do2ydza-ew.a.run.app/project
In order to create a GCP Project, in which the application will be run, the following information is required:
| 1 | project name | as will appear in your project`s project's list |
| 2 | the requestor is the one managing the applications running on the project; this email will receive messages (alert and notifications) for when the project is ready to be used; | |
| 3 | client name | (also known as the Boxalino account name) this is to ensure the access to the views, core & reports datasets (https://boxalino.atlassian.net/wiki/spaces/BPKB/pages/303792129/GCP+Project+Deployment#BigQuery-Datasets-Access ) |
| 4 | optional; the labels are used as project meta-information. see Labels | |
| 5 | optional; by default, the requestor will have full access and can further share with others. see Permissions |
Once the project is created (2-3 Once the project is created (2-3 min), the requestor will have access to it, in their Google Cloud Console.
| Tip |
|---|
As an editor on the project, the requestor will be able to:
|
...
Labels (optional)
Labels are key-value pairs meant to better organize the projects.
Lets imagine the scenario when the client has multiple Data Scientists working on different projects. Labeling them will allow better structure.
| Code Block |
|---|
team:data-science
component:<main-application-name>
environment:production
|
More information on labels: https://cloud.google.com/resource-manager/docs/creating-managing-labels
Permissions (optional)
The permissions are added when the project is created.
By default, the requestor`s email has the project editor role
Once the project is released, the requestor can add more emails / users to the IAM policies of the project.
Here is a sample of provided permissions (optional):
| Code Block |
|---|
user:dana@boxalino.com:roles/editor
user:dana@boxalino.com:roles/resourcemanager.projectIamAdmin
user:dana@boxalino.com:roles/compute.osLogin
user:dana@boxalino.com:roles/compute.osAdminLogin
user:dana@boxalino.com:roles/bigquery.dataOwner
serviceAccount:service-account-from-other-projects:roles/iam.serviceAccountUser
serviceAccount:service-account-from-other-projects:roles/bigquery.dataOwner
serviceAccount:service-account-from-other-projects:roles/bigquery.dataEditor |
...
|
...
2. Billing Information
In order to access the Google Cloud resources - a billing account must be set on the project.
...
Provide the following information:
| 1 | project Project ID Project Number | the project ID is unique; the project ID is diplayed on the dashboard of your project https://console.cloud.google.com/home/dashboard  | ||||||||
| 2 | GCS bucket name | the bucket name where the Required Files are located (ex: gs://<project-name>-<app-name>); the contents will be made available on the application as well.
| 3 | access code | as provided by Boxalino |
| Tip |
|---|
Once the application has been launched, a script will initialize the environment and load all your content from the GCS bucket. |
...
| Code Block |
|---|
sudo gsutil rsync -r gs://<BUCKET>/ <APPLICATION-PATH> |
| Note |
|---|
Replace <BUCKET> with your storage bucket name (where the application files have been loaded). Replace <APPLICATION-PATH> with the path to your application (default: /home/project-name). |
...