Contents

Transfering Data into Cloud Storage

Transfering Data into Cloud Storage

We distinguish between two primary types of data to upload: “Original” and “Published” data.

  • Published Data has been published and archived in a publically accessible location (e.g. a data repository like zenodo or figshare). We do not recommend uploading this data to the cloud directly, but instead use Pangeo Forge to transform and upload it to the cloud. This ensures that the data is stored in an ARCO format and can be easily accessed by other LEAP members.

  • Original Data is any dataset that is produced by researchers at LEAP and has not been published yet. The main use case for this data is to share it with other LEAP members and collaborate on it. For original data we support direct uploaded to the cloud. Be aware that original data could change rapidly as the data producer is iterating on their code. We encourage all datasets to be archived and published before using them in scientific publications.

Step one is always to check whether data already exists in the LEAP data catalog, in which case access is simply a matter of pasting a code snippet.

Ingesting Datasets into Cloud Storage

If you do not find your dataset in the data catalog we can ingest it. Data ingestion in this context means that we have a programatic way to download and transform data into Analysis-Ready Cloud-Optimized (ARCO) formats in a reproducible way, so that the dataset is available for the LEAP community and beyond (see LEAP-Pangeo Cloud Storage Buckets for who can access which resource).

Based on the 3 types of data we host in the The Data Library there are different ways of ingesting data:

  • Linking an existing (public, egress-free) ARCO dataset to the Data Catalog

  • Ingesting and transforming data into an ARCO copy on LEAP-Pangeo Cloud Storage Buckets.

  • (Work in Progress): Creating a virtual zarr store from existing publically hosted legacy format data (e.g. netcdf)

The end result should feel indistingushable to the user (i.e. they just copy and paste a snippet and can immediately get to work Data Access)

If you are interested in publishing archival or original data, please refer to our How-To guide on data ingestion.

Upload medium sized original data from your local machine

For medium sized datasets that can be uploaded within an hour, you can use a temporary access token generated on the JupyterHub to upload data to the cloud.

  • Set up a new environment on your local machine (e.g. laptop)

mamba env create --name leap_pangeo_transfer python=3.9 google-auth gcsfs jupyterlab xarray zarr dask

Add any other dependencies (e.g. netcdf4) that you need to read your data at the end of the line

  • Activate the environment

conda activate leap_pangeo_transfer

and set up a jupyter notbook (or a pure python script) that loads your data in as few xarray datasets as possible. For instance, if you have one dataset that consists of many files split in time, you should set your notebook up to read all the files using xarray into a single dataset, and then try to write out a small part of the dataset to a zarr store.

Now generate a temporary token and copy the resulting token into a plain text file token.txt in a convenient location on your local machine.

  • Now start a JupyterLab notebook and paste the following code into a cell:

import gcsfs
import xarray as xr
from google.cloud import storage
from google.oauth2.credentials import Credentials

# import an access token
# - option 1: read an access token from a file
with open("path/to/your/token.txt") as f:
    access_token = f.read().strip()

# setup a storage client using credentials
credentials = Credentials(access_token)
fs = gcsfs.GCSFileSystem(token=credentials)

Make sure to replace the path/to/your/token.txt with the actual path to your token file.

Try to write a small dataset to the cloud:

ds = xr.DataArray([1]).to_dataset(name="test")
mapper = fs.get_mapper(
    "gs://leap-scratch/<your_username>/test_offsite_upload.zarr"
)  # This additional step is necessary to have the correct authentication set
ds.to_zarr(mapper)

Replace <your_username> with your actual username on the hub.

  • Make sure that you can read the test dataset from within the hub (go back to Basic writing to and reading from cloud buckets).

  • Now the last step is to paste the code to load your actual dataset into the notebook and use .to_zarr to upload it.

Make sure to give the store a meaningful name, and raise an issue in the data-management repo to get the dataset added to the LEAP Data Library.

Make sure to use a different bucket than leap-scratch, since that will be deleted every 7 days! For more info refer to the available storage buckets.

Uploading large original data from an HPC system (no browser access on the system available)

A commong scenario is the following: A researcher/student has run a simulation on a High Performance Computer (HPC) at their institution, but now wants to collaboratively work on the analysis or train a machine learning model with this data. For this they need to upload it to the cloud storage.

The following steps will guide you through the steps needed to authenticate and upload data to the cloud, but might have to be slightly modified depending on the actual setup of the users HPC.

Conversion Script/Notebook

In most cases you do not just want to upload the data in its current form (e.g. many netcdf files).

Instead we will load the data into an xarray.Dataset and then write that Dataset object directly to a zarr store in the cloud. For this you need a python environment with xarray, gcsfs, zarr installed (you might need additional dependencies for your particular use case).

  1. Spend some time to set up a python script/jupyter notebook on the HPC system that opens your files and combines them in to one or more xarray.Datasets (combine as many files as sensible into a single dataset). Make sure that your data is lazily loaded and the Dataset.data is a dask array

  2. Check your dataset:

    • Check that the metadata is correct.

    • Check that all the variables/dimensions are in the dataset

    • Check the dask chunksize. A general rule is to aim for around 100MB size, but the size and structure of chunking that is optimal depends heavily on the later use case.

  3. Try to write out a subset of the data locally by calling the .to_zarr method on the dataset.

Once that works we can move on to the authentication.

Upload Prerequisites

Before we are able to set up authentication we need to make sure our HPC and local computer (required) are set up correctly.

  • You have to be signed up to LEAP’s Google Groups.

  • Make sure to install the Google Cloud SDK in both your HPC environment, and your local computer that can open a web browser (e.g. your laptop).

Steps Steps executed on your ”local” computer (e.g. laptop) will be colored in green and steps on your ”remote” computer (e.g. HPC) in purple.

  1. SSH into the HPC

  2. Check that you have an internet connection with ping www.google.com

  3. Request no browser authentication: 

    gcloud auth application-default login --scopes=https://www.googleapis.com/auth/devstorage.read_write,https://www.googleapis.com/auth/iam.test --no-browser

    🚨 It is very important to include the --scopes= argument for security reasons. Do not run this command without it!

  4. Follow the onscreen prompt and paste the command into a terminal on your local machine.

  5. This will open a browser window. Authenticate with the gmail account that was added to the google group.

  6. Go back to the terminal and follow the onscreen instructions. Copy the text from the command line and paste the command in the open dialog on the remote machine.

  7. Make sure to note the path to the auth json! It will be something like .../.config/gcloud/....json.

Now you are have everything you need to authenticate.

Lets verify that you can write a small dummy dataset to the cloud. In your notebook/script run the following (make sure to replace the filename and your username as instructed).

Your dataset should now be available for all LEAP members 🎉🚀

import xarray as xr
import gcsfs
import json

with open(
    "your_auth_file.json"
) as f:  # 🚨 make sure to enter the `.json` file from step 7
    token = json.load(f)

# test write a small dummy xarray dataset to zarr
ds = xr.DataArray([1, 4, 6]).to_dataset(name="data")
# Once you have confirmed

fs = gcsfs.GCSFileSystem(token=token)
mapper = fs.get_mapper(
    "gs://leap-persistent/<username>/testing/demo_write_from_remote.zarr"
)  # 🚨 enter your leap (github) username here
ds.to_zarr(mapper)

Now you can repeat the same steps but replace your dataset with the full dataset from above and leave your python code running until the upload has finished. Depending on the internet connection speed and the size of the full dataset, this can take a while.

If you want to see a progress bar, you can wrap the call to .to_zarr with a dask progress bar

from dask.diagnostics import ProgressBar

with ProgressBar():
    ds.to_zarr(mapper)

Once the data has been uploaded, make sure to erase the .../.config/gcloud/....json file from step 7, and ask to be removed from the Google Group.

Manually uploading/downloading data to cloud buckets (deprecated)

Warning

This section of the docs is just retained for completeness. There might be special situations where it is beneficial/necessary to upload data to the LEAP-Pangeo Cloud Storage Buckets but we generally encourage data ingestion to the m2lines OSN Pod due to the public access and reduced running cost. See above for instructions.

We discourage manually moving datasets to our cloud storage as much as possible since it is hard to reproduce these datasets at a future point (if e.g. the dataset maintainer has moved on to a different position) (see Reproducibility. We encourage you to try out the methods above, but if these should not work for some reason (and you were not able to find a solution with the Data and Computation Team), you should try the methods below. We will always prioritize unblocking your work.

The below solutions fundamentally rely on the data being ‘pushed’ to the LEAP-Pangeo Cloud Storage Buckets which usually requires intervention on part of the Data Expert. This stands in contrast to e.g. data ingestion via Pangeo-Forge where the Data Expert only has to work on the recipe creation and the data is ‘pulled’ in a reproducible way. For more information see LEAP-Pangeo Data Policy.

Fundamentally the ‘pushing’ of datasets relies on two components:

previous

Data Guide

next

Working with the LEAP Data Catalog