If you don’t have access to a Linux terminal or prefer not to install tools locally, you can use Google Cloud Shell. You’ll need a Google diff --git a/02-storage.html b/02-storage.html index bab6554..f08dd7f 100644 --- a/02-storage.html +++ b/02-storage.html @@ -118,11 +118,11 @@ CMS Open Data processing in Google Cloud Platform (GCP)
For the moment, for a new project created for testing these -instructions, this fails. Investigating…
+Failure with errors of type
+Code: QUOTA_EXCEEDED
+Message: Quota 'N2_CPUS' exceeded.are due to requested machine type no being available in the requested +zone. Nothing to do with you quota.
+Try in a different region or with a different machine type. You can
+give them as parameters
+e.g. --zone=europe-west4-a --machine-type=e2-standard-4.
+Independent of the zone specified in parameters, the disk image will
+have eu as the location, so any zone in europe
+is OK (if you plan to create your cluster in a zone in
+europe).
Note that the bucket for logs has to be in the same region so you
+might need to create another one. Remove the old one with
+gcloud storage rm -r gs://<BUCKET_FOR_LOGS>.
If you don’t have access to a Linux terminal or prefer not to install tools locally, you can use Google Cloud Shell. You’ll need a Google @@ -795,11 +807,11 @@
Content from Disk image
+Content from Disk image
Last updated on 2024-10-16 | - Edit this page
+ Edit this pageA script is available but building the disk image does not work for a +new GCP account for the moment.
+Investigating….
To build an image disk, we will use a script that produces some logs. +We create a bucket for these logs with
+gcloud storage buckets create gs://<BUCKET_FOR_LOGS>/ --location europe-west4Before you can create resources on GCP, you will need to enable the corresponding services.
Your project usually has several services enabled already. You can list them with
-You can list all available services with
-but that’s a long list!
To build a disk image, you will need to enable -Compute Engine API (compute.googleapis.com) with
-gcloud services enable compute.googleapis.comgcloud services enable cloudbuild.googleapis.com compute.googleapis.comWhen services are enabled, some “service accounts” with specific +roles get created. You can list them with
+ -Often, the resources need to work with each other. In this case, the +Cloud Build service needs to have two additional roles to access Compute +resources (the image disk belongs to that category)
+Add them with
+$ gcloud compute disks create pfnano-disk --zone=europe-west4-c --size=100GB --type=pd-standard
-WARNING: You have selected a disk size of under [200GB]. This may result in poor I/O performance. For more information, see: https://developers.google.com/compute/docs/disks#performance.
-Created [https://www.googleapis.com/compute/v1/projects/<PROJECT_ID>/zones/europe-west4-c/disks/pfnano-disk].
-NAME ZONE SIZE_GB TYPE STATUS
-pfnano-disk europe-west4-c 100 pd-standard READY
-
-New disks are unformatted. You must format and mount a disk before it
-can be used. You can find instructions on how to do this at:
-
-https://cloud.google.com/compute/docs/disks/add-persistent-disk#formattinggcloud projects add-iam-policy-binding <PROJECT_ID> --member serviceAccount:<PROJECT_NR>@cloudbuild.gserviceaccount.com --role roles/compute.serviceAgent$ gcloud compute instances create vm-work --zone=europe-west4-c --machine-type=e2-standard-4 --disk=name=pfnano-disk --boot-disk-size=100GB --image-family=cos-113-lts --image-project=cos-cloud
-WARNING: You have selected a disk size of under [200GB]. This may result in poor I/O performance. For more information, see: https://developers.google.com/compute/docs/disks#performance.
-Created [https://www.googleapis.com/compute/v1/projects/<PROJECT_ID>/zones/europe-west4-c/instances/vm-work].
-WARNING: Some requests generated warnings:
- - Disk size: '100 GB' is larger than image size: '10 GB'. You might need to resize the root repartition manually if the operating system does not support automatic resizing. See https://cloud.google.com/compute/docs/disks/add-persistent-disk#resize_pd for details.
-
-NAME ZONE MACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IP STATUS
-vm-work europe-west4-c e2-standard-4 10.164.0.2 35.204.202.73 RUNNINGLogin to this VM
-$ gcloud compute ssh vm-work --zone=europe-west4-c
-Updating project ssh metadata...⠶Updated [https://www.googleapis.com/compute/v1/projects/<PROJECT_ID>].
-Updating project ssh metadata...done.
-Waiting for SSH key to propagate.
-Warning: Permanently added 'compute.5401844593939611330' (ED25519) to the list of known hosts.
-kati@vm-work ~ $ Check the logical links that indicate the disk address
-$ ls -l /dev/disk/by-id/google-*
-lrwxrwxrwx 1 root root 9 Oct 16 13:31 /dev/disk/by-id/google-persistent-disk-0 -> ../../sda
-lrwxrwxrwx 1 root root 10 Oct 16 13:31 /dev/disk/by-id/google-persistent-disk-0-part1 -> ../../sda1
-[...]
-google-persistent-disk-0-part9 -> ../../sda9
-lrwxrwxrwx 1 root root 9 Oct 16 13:31 /dev/disk/by-id/google-persistent-disk-1 -> ../../sdbIt is the one without partitioning, in this sdb. Note
-that it can be other way round!
Format the disk
-$ sudo mkfs.ext4 -m 0 -E lazy_itable_init=0,lazy_journal_init=0,discard /dev/sdb
-mke2fs 1.47.0 (5-Feb-2023)
-Discarding device blocks: done
-Creating filesystem with 26214400 4k blocks and 6553600 inodes
-Filesystem UUID: 3975c0a0-6b73-4b5c-81a0-9d8531837479
-Superblock backups stored on blocks:
- 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
- 4096000, 7962624, 11239424, 20480000, 23887872
-
-Allocating group tables: done
-Writing inode tables: done
-Creating journal (131072 blocks): done
-Writing superblocks and filesystem accounting information: done$ sudo mkdir -p /mnt/disks/img
-$ sudo mount -o discard,defaults /dev/sdb /mnt/disks/img
-$ sudo chmod a+w /mnt/disks/imggcloud projects add-iam-policy-binding <PROJECT_ID> --member serviceAccount:<PROJECT_NR>@cloudbuild.gserviceaccount.com --role roles/compute.adminYou need to create a credential file to run the script:
+ +and authenticate in the browser window that opens.
+Add a line "data-root": "/mnt/disks/img" to the docker
-config file /etc/docker/daemon.json so that docker stores
-data in the mounted disk. The file becomes:
{
- "live-restore": true,
- "log-opts": {
- "tag": "{{.Name}}"
- },
- "storage-driver": "overlay2",
- "mtu": 1460,
- "data-root": "/mnt/disks/img"
-}Remember the comma before the line that you added! I made the -mistake, you do not have to…
-Restart the docker service
-sudo systemctl restart dockerPull the images that you need. In the example workflow we use three -of them (in addition to a tiny python image), so we pull:
-docker pull ghcr.io/katilp/pfnano-image-build:main
-docker pull cernopendata/cernopendata-client
-docker pull rootproject/root:latestAfter the pull is ready, you can see them with:
-$ docker image ls
-REPOSITORY TAG IMAGE ID CREATED SIZE
-rootproject/root latest 34eb35079484 4 weeks ago 2.76GB
-cernopendata/cernopendata-client latest f690d7308889 7 weeks ago 282MB
-ghcr.io/katilp/pfnano-image-build main d95521bc96a9 11 months ago 32.1GBExit from the VM with exit and stop it
gcloud compute instances stop vm-workPull the code from https://github.com/GoogleCloudPlatform/ai-on-gke/tree/main/tools/gke-disk-image-builder
+If you want only this directory and not the full repository, use the +sparse checkout:
+git init <your_new_folder>
+cd <your_new_folder>
+git remote add -f origin git@github.com:GoogleCloudPlatform/ai-on-gke.gitThis takes a while.
+git config core.sparseCheckout true
+echo "tools/gke-disk-image-builder/" >> .git/info/sparse-checkout
+git pull origin main
+cd tools/gke-disk-image-builder/gcloud compute images create pfnano-image-disk --project=hip-new-full-account --source-disk=pfnano-disk --source-disk-zone=europe-west4-c --storage-location=europe-west4Now as you have the image created, you can delete the VM and the -original disk.
-gcloud compute instances delete vm-work --zone=europe-west4-cgcloud compute disks delete pfnano-disk --zone=europe-west4-cTo create the image with the script, you must have go
+installed.
Run the script with
+The VM costs depends on the time
+go run ./cli --project-name=<PROJECT_ID> --image-name=pfnano-disk-image --zone=europe-west4-a --gcs-path=gs://<BUCKET_FOR_LOGS> --disk-size-gb=50 --container-image=ghcr.io/katilp/pfnano-image-build:main --timeout 100mFailure with errors of type
+Code: QUOTA_EXCEEDED
+Message: Quota 'N2_CPUS' exceeded.are due to requested machine type no being available in the requested +zone. Nothing to do with you quota.
+Try in a different region or with a different machine type. You can
+give them as parameters
+e.g. --zone=europe-west4-a --machine-type=e2-standard-4.
+Independent of the zone specified in parameters, the disk image will
+have eu as the location, so any zone in europe
+is OK (if you plan to create your cluster in a zone in
+europe).
Note that the bucket for logs has to be in the same region so you
+might need to create another one. Remove the old one with
+gcloud storage rm -r gs://<BUCKET_FOR_LOGS>.
Content from Kubernetes cluster
Last updated on 2024-10-16 | @@ -1078,14 +1063,84 @@
gcloud services enable container.googleapis.comIf you worked through Section 02, you have now a storage bucket for +the output files.
+List the buckets with
+ +If you worked through Section 03, you have a secondary boot disk +image available
The example Terraform scripts and Argo Workflow configuration are +in
+Get them with
+ +Set the variable in the terraform.tfvars files.
Run
+ +and confirm “yes”.
+Content from Set up workflow
+Last updated on 2024-10-16 | + + Edit this page
+Make sure that you are in the GCP account and project that you intend +to use for this work. In your Linux terminal, type
+ +The output shows your account and project.
+If you worked through Section 02, you have +now a storage bucket for the output files.
+List the buckets with
+ +You should have Argo CLI installed, see Software setup.
+The example Terraform scripts and Argo Workflow configuration are +in
+Get them with
+ +Deploy Argo Workflows services with
+kubectl apply -n argo -f https://github.com/argoproj/argo-workflows/releases/download/v3.5.10/install.yaml
+kubectl apply -f argo/service_account.yaml
+kubectl apply -f argo/argo_role.yaml
+kubectl apply -f argo/argo_role_binding.yamlWait for the services to start.
+You should see the following:
+$ kubectl get all -n argo
+NAME READY STATUS RESTARTS AGE
+pod/argo-server-5f7b589d6f-jkf4z 1/1 Running 0 24s
+pod/workflow-controller-864c88655d-wsfr8 1/1 Running 0 24s
+
+NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
+service/argo-server ClusterIP 34.118.233.69 <none> 2746/TCP 25s
+
+NAME READY UP-TO-DATE AVAILABLE AGE
+deployment.apps/argo-server 1/1 1 1 24s
+deployment.apps/workflow-controller 1/1 1 1 24s
+
+NAME DESIRED CURRENT READY AGE
+replicaset.apps/argo-server-5f7b589d6f 1 1 1 24s
+replicaset.apps/workflow-controller-864c88655d 1 1 1 24sEdit the parameters in the argo/argo_bucket_run.yaml so
+that they are
parameters:
+ - name: nEvents
+ #FIXME
+ # Number of events in the dataset to be processed (-1 is all)
+ value: 1000
+ - name: recid
+ #FIXME
+ # Record id of the dataset to be processed
+ value: 30511
+ - name: nJobs
+ #FIXME
+ # Number of jobs the processing workflow should be split into
+ value: 2
+ - name: bucket
+ #FIXME
+ # Name of cloud storage bucket for storing outputs
+ value: <YOUR_BUCKET_NAME>Now submit the workflow with
+ +Observe its progress with
+ +Once done, check the ouput in the bucket with
+$ gcloud storage ls gs://<YOUR_BUCKET_NAME>/**
+gs://<YOUR_BUCKET_NAME>/pfnano/30511/files_30511.txt
+gs://<YOUR_BUCKET_NAME>/pfnano/30511/logs/1.logs
+gs://<YOUR_BUCKET_NAME>/pfnano/30511/logs/2.logs
+gs://<YOUR_BUCKET_NAME>/pfnano/30511/plots/h_num_cands.png
+gs://<YOUR_BUCKET_NAME>/pfnano/30511/plots/h_pdgid_cands.png
+gs://<YOUR_BUCKET_NAME>/pfnano/30511/scatter/pfnanooutput1.root
+gs://<YOUR_BUCKET_NAME>/pfnano/30511/scatter/pfnanooutput2.rootkubectl.argo.gcloud
+commands or on Google Cloud Console Web UI.If you don’t have access to a Linux terminal or prefer not to install tools locally, you can use Google Cloud Shell. You’ll need a Google diff --git a/instructor/02-storage.html b/instructor/02-storage.html index f9cd802..18fe364 100644 --- a/instructor/02-storage.html +++ b/instructor/02-storage.html @@ -118,11 +118,11 @@ CMS Open Data processing in Google Cloud Platform (GCP)
For the moment, for a new project created for testing these -instructions, this fails. Investigating…
+Failure with errors of type
+Code: QUOTA_EXCEEDED
+Message: Quota 'N2_CPUS' exceeded.are due to requested machine type no being available in the requested +zone. Nothing to do with you quota.
+Try in a different region or with a different machine type. You can
+give them as parameters
+e.g. --zone=europe-west4-a --machine-type=e2-standard-4.
+Independent of the zone specified in parameters, the disk image will
+have eu as the location, so any zone in europe
+is OK (if you plan to create your cluster in a zone in
+europe).
Note that the bucket for logs has to be in the same region so you
+might need to create another one. Remove the old one with
+gcloud storage rm -r gs://<BUCKET_FOR_LOGS>.
If you don’t have access to a Linux terminal or prefer not to install tools locally, you can use Google Cloud Shell. You’ll need a Google @@ -799,11 +811,11 @@
Content from Disk image
+Content from Disk image
Last updated on 2024-10-16 | - Edit this page
+ Edit this pageEstimated time: 15 minutes
A script is available but building the disk image does not work for a +new GCP account for the moment.
+Investigating….
To build an image disk, we will use a script that produces some logs. +We create a bucket for these logs with
+gcloud storage buckets create gs://<BUCKET_FOR_LOGS>/ --location europe-west4Before you can create resources on GCP, you will need to enable the corresponding services.
Your project usually has several services enabled already. You can list them with
-You can list all available services with
-but that’s a long list!
To build a disk image, you will need to enable -Compute Engine API (compute.googleapis.com) with
-gcloud services enable compute.googleapis.comgcloud services enable cloudbuild.googleapis.com compute.googleapis.comWhen services are enabled, some “service accounts” with specific +roles get created. You can list them with
+ -Often, the resources need to work with each other. In this case, the +Cloud Build service needs to have two additional roles to access Compute +resources (the image disk belongs to that category)
+Add them with
+$ gcloud compute disks create pfnano-disk --zone=europe-west4-c --size=100GB --type=pd-standard
-WARNING: You have selected a disk size of under [200GB]. This may result in poor I/O performance. For more information, see: https://developers.google.com/compute/docs/disks#performance.
-Created [https://www.googleapis.com/compute/v1/projects/<PROJECT_ID>/zones/europe-west4-c/disks/pfnano-disk].
-NAME ZONE SIZE_GB TYPE STATUS
-pfnano-disk europe-west4-c 100 pd-standard READY
-
-New disks are unformatted. You must format and mount a disk before it
-can be used. You can find instructions on how to do this at:
-
-https://cloud.google.com/compute/docs/disks/add-persistent-disk#formattinggcloud projects add-iam-policy-binding <PROJECT_ID> --member serviceAccount:<PROJECT_NR>@cloudbuild.gserviceaccount.com --role roles/compute.serviceAgent$ gcloud compute instances create vm-work --zone=europe-west4-c --machine-type=e2-standard-4 --disk=name=pfnano-disk --boot-disk-size=100GB --image-family=cos-113-lts --image-project=cos-cloud
-WARNING: You have selected a disk size of under [200GB]. This may result in poor I/O performance. For more information, see: https://developers.google.com/compute/docs/disks#performance.
-Created [https://www.googleapis.com/compute/v1/projects/<PROJECT_ID>/zones/europe-west4-c/instances/vm-work].
-WARNING: Some requests generated warnings:
- - Disk size: '100 GB' is larger than image size: '10 GB'. You might need to resize the root repartition manually if the operating system does not support automatic resizing. See https://cloud.google.com/compute/docs/disks/add-persistent-disk#resize_pd for details.
-
-NAME ZONE MACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IP STATUS
-vm-work europe-west4-c e2-standard-4 10.164.0.2 35.204.202.73 RUNNINGLogin to this VM
-$ gcloud compute ssh vm-work --zone=europe-west4-c
-Updating project ssh metadata...⠶Updated [https://www.googleapis.com/compute/v1/projects/<PROJECT_ID>].
-Updating project ssh metadata...done.
-Waiting for SSH key to propagate.
-Warning: Permanently added 'compute.5401844593939611330' (ED25519) to the list of known hosts.
-kati@vm-work ~ $ Check the logical links that indicate the disk address
-$ ls -l /dev/disk/by-id/google-*
-lrwxrwxrwx 1 root root 9 Oct 16 13:31 /dev/disk/by-id/google-persistent-disk-0 -> ../../sda
-lrwxrwxrwx 1 root root 10 Oct 16 13:31 /dev/disk/by-id/google-persistent-disk-0-part1 -> ../../sda1
-[...]
-google-persistent-disk-0-part9 -> ../../sda9
-lrwxrwxrwx 1 root root 9 Oct 16 13:31 /dev/disk/by-id/google-persistent-disk-1 -> ../../sdbIt is the one without partitioning, in this sdb. Note
-that it can be other way round!
Format the disk
-$ sudo mkfs.ext4 -m 0 -E lazy_itable_init=0,lazy_journal_init=0,discard /dev/sdb
-mke2fs 1.47.0 (5-Feb-2023)
-Discarding device blocks: done
-Creating filesystem with 26214400 4k blocks and 6553600 inodes
-Filesystem UUID: 3975c0a0-6b73-4b5c-81a0-9d8531837479
-Superblock backups stored on blocks:
- 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
- 4096000, 7962624, 11239424, 20480000, 23887872
-
-Allocating group tables: done
-Writing inode tables: done
-Creating journal (131072 blocks): done
-Writing superblocks and filesystem accounting information: done$ sudo mkdir -p /mnt/disks/img
-$ sudo mount -o discard,defaults /dev/sdb /mnt/disks/img
-$ sudo chmod a+w /mnt/disks/imggcloud projects add-iam-policy-binding <PROJECT_ID> --member serviceAccount:<PROJECT_NR>@cloudbuild.gserviceaccount.com --role roles/compute.adminYou need to create a credential file to run the script:
+ +and authenticate in the browser window that opens.
+Add a line "data-root": "/mnt/disks/img" to the docker
-config file /etc/docker/daemon.json so that docker stores
-data in the mounted disk. The file becomes:
{
- "live-restore": true,
- "log-opts": {
- "tag": "{{.Name}}"
- },
- "storage-driver": "overlay2",
- "mtu": 1460,
- "data-root": "/mnt/disks/img"
-}Remember the comma before the line that you added! I made the -mistake, you do not have to…
-Restart the docker service
-sudo systemctl restart dockerPull the images that you need. In the example workflow we use three -of them (in addition to a tiny python image), so we pull:
-docker pull ghcr.io/katilp/pfnano-image-build:main
-docker pull cernopendata/cernopendata-client
-docker pull rootproject/root:latestAfter the pull is ready, you can see them with:
-$ docker image ls
-REPOSITORY TAG IMAGE ID CREATED SIZE
-rootproject/root latest 34eb35079484 4 weeks ago 2.76GB
-cernopendata/cernopendata-client latest f690d7308889 7 weeks ago 282MB
-ghcr.io/katilp/pfnano-image-build main d95521bc96a9 11 months ago 32.1GBExit from the VM with exit and stop it
gcloud compute instances stop vm-workPull the code from https://github.com/GoogleCloudPlatform/ai-on-gke/tree/main/tools/gke-disk-image-builder
+If you want only this directory and not the full repository, use the +sparse checkout:
+git init <your_new_folder>
+cd <your_new_folder>
+git remote add -f origin git@github.com:GoogleCloudPlatform/ai-on-gke.gitThis takes a while.
+git config core.sparseCheckout true
+echo "tools/gke-disk-image-builder/" >> .git/info/sparse-checkout
+git pull origin main
+cd tools/gke-disk-image-builder/gcloud compute images create pfnano-image-disk --project=hip-new-full-account --source-disk=pfnano-disk --source-disk-zone=europe-west4-c --storage-location=europe-west4Now as you have the image created, you can delete the VM and the -original disk.
-gcloud compute instances delete vm-work --zone=europe-west4-cgcloud compute disks delete pfnano-disk --zone=europe-west4-cTo create the image with the script, you must have go
+installed.
Run the script with
+The VM costs depends on the time
+go run ./cli --project-name=<PROJECT_ID> --image-name=pfnano-disk-image --zone=europe-west4-a --gcs-path=gs://<BUCKET_FOR_LOGS> --disk-size-gb=50 --container-image=ghcr.io/katilp/pfnano-image-build:main --timeout 100mFailure with errors of type
+Code: QUOTA_EXCEEDED
+Message: Quota 'N2_CPUS' exceeded.are due to requested machine type no being available in the requested +zone. Nothing to do with you quota.
+Try in a different region or with a different machine type. You can
+give them as parameters
+e.g. --zone=europe-west4-a --machine-type=e2-standard-4.
+Independent of the zone specified in parameters, the disk image will
+have eu as the location, so any zone in europe
+is OK (if you plan to create your cluster in a zone in
+europe).
Note that the bucket for logs has to be in the same region so you
+might need to create another one. Remove the old one with
+gcloud storage rm -r gs://<BUCKET_FOR_LOGS>.
Content from Kubernetes cluster
Last updated on 2024-10-16 | @@ -1084,14 +1069,267 @@
gcloud services enable container.googleapis.comIf you worked through Section 02, you have now a storage bucket for +the output files.
+List the buckets with
+ +If you worked through Section 03, you have a secondary boot disk +image available
+The example Terraform scripts and Argo Workflow configuration are +in
+Get them with
+ +Set the variable in the terraform.tfvars files.
Run
+ +and confirm “yes”.
+Content from Set up workflow
+Last updated on 2024-10-16 | + + Edit this page
+Estimated time: 15 minutes
+Make sure that you are in the GCP account and project that you intend +to use for this work. In your Linux terminal, type
+ +The output shows your account and project.
+If you worked through Section 02, you have +now a storage bucket for the output files.
+List the buckets with
+ +You should have Argo CLI installed, see Software setup.
The example Terraform scripts and Argo Workflow configuration are +in
+Get them with
+ +Deploy Argo Workflows services with
+kubectl apply -n argo -f https://github.com/argoproj/argo-workflows/releases/download/v3.5.10/install.yaml
+kubectl apply -f argo/service_account.yaml
+kubectl apply -f argo/argo_role.yaml
+kubectl apply -f argo/argo_role_binding.yamlWait for the services to start.
+You should see the following:
+$ kubectl get all -n argo
+NAME READY STATUS RESTARTS AGE
+pod/argo-server-5f7b589d6f-jkf4z 1/1 Running 0 24s
+pod/workflow-controller-864c88655d-wsfr8 1/1 Running 0 24s
+
+NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
+service/argo-server ClusterIP 34.118.233.69 <none> 2746/TCP 25s
+
+NAME READY UP-TO-DATE AVAILABLE AGE
+deployment.apps/argo-server 1/1 1 1 24s
+deployment.apps/workflow-controller 1/1 1 1 24s
+
+NAME DESIRED CURRENT READY AGE
+replicaset.apps/argo-server-5f7b589d6f 1 1 1 24s
+replicaset.apps/workflow-controller-864c88655d 1 1 1 24sEdit the parameters in the argo/argo_bucket_run.yaml so
+that they are
parameters:
+ - name: nEvents
+ #FIXME
+ # Number of events in the dataset to be processed (-1 is all)
+ value: 1000
+ - name: recid
+ #FIXME
+ # Record id of the dataset to be processed
+ value: 30511
+ - name: nJobs
+ #FIXME
+ # Number of jobs the processing workflow should be split into
+ value: 2
+ - name: bucket
+ #FIXME
+ # Name of cloud storage bucket for storing outputs
+ value: <YOUR_BUCKET_NAME>Now submit the workflow with
+ +Observe its progress with
+ +Once done, check the ouput in the bucket with
+$ gcloud storage ls gs://<YOUR_BUCKET_NAME>/**
+gs://<YOUR_BUCKET_NAME>/pfnano/30511/files_30511.txt
+gs://<YOUR_BUCKET_NAME>/pfnano/30511/logs/1.logs
+gs://<YOUR_BUCKET_NAME>/pfnano/30511/logs/2.logs
+gs://<YOUR_BUCKET_NAME>/pfnano/30511/plots/h_num_cands.png
+gs://<YOUR_BUCKET_NAME>/pfnano/30511/plots/h_pdgid_cands.png
+gs://<YOUR_BUCKET_NAME>/pfnano/30511/scatter/pfnanooutput1.root
+gs://<YOUR_BUCKET_NAME>/pfnano/30511/scatter/pfnanooutput2.rootkubectl.argo.gcloud
+commands or on Google Cloud Console Web UI.kubectl.argo.gcloud
+commands or on Google Cloud Console Web UI.kubectl.argo.gcloud
+commands or on Google Cloud Console Web UI.