Mounting Object Storage buckets to the file system of Yandex Data Processing hosts
In Yandex Data Processing, you can use initialization actions to configure hosts.
With them, you can automate the installation and setup of GeeseFS, the software enabling Yandex Data Processing cluster hosts to mount Yandex Object Storage buckets via FUSE
To set up GeeseFS:
- Prepare the initialization action.
- Create a cluster that uses the initialization action.
- Check bucket availability.
If you no longer need the created resources, delete them.
Getting started
Prepare the infrastructure:
-
Create a service account with the
dataproc.agent
anddataproc.provisioner
roles. -
Create an Object Storage bucket.
-
Grant the service account read access to the bucket. For this, use one of the following methods:
-
Set up the bucket's ACL and grant the
READ
access to the service account.The service account will get read access only to the specified bucket.
-
Assign the service account the
storage.viewer
role.The service account will get read access to all buckets in the folder.
-
-
Create a NAT gateway for the subnet you want to create your Yandex Data Processing cluster in.
-
If you do not have Terraform yet, install it.
-
Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.
-
Configure and initialize a provider. There is no need to create a provider configuration file manually, you can download it
. -
Place the configuration file in a separate working directory and specify the parameter values. If you did not add the authentication credentials to environment variables, specify them in the configuration file.
-
Download the data-processing-init-actions-geesefs.tf
configuration file to the same working directory.This file describes:
- Network
- Subnet
- Route table
- NAT gateway
- Security group and rules required to connect to the Yandex Data Processing cluster
- Service account with the roles required to work with the Object Storage bucket and Yandex Data Processing cluster
- Static key for the service account to manage the Object Storage bucket
- Object Storage bucket
- Yandex Data Processing cluster
-
In the
data-processing-init-actions-geesefs.tf
file, specify the following parameters:dp_network_name
: Name of the network for your Yandex Data Processing cluster.dp_subnet_name
: Name of the subnet for your Yandex Data Processing cluster.dp_sg_name
: Name of the security group for your Yandex Data Processing cluster.dp_sa_folder_id
: ID of the folder to create your infrastructure and Yandex Data Processing cluster in.dp_sa_name
: Name of the service account for your Yandex Data Processing cluster and Object Storage bucket.dp_bucket_name
: Object Storage bucket name.dataproc_name
: Yandex Data Processing cluster name.ssh-path
: Path to the file of the public SSH key for your Yandex Data Processing cluster.
-
Check that the Terraform configuration files are correct using this command:
terraform validate
If there are any errors in the configuration files, Terraform will point them out.
-
Create the required infrastructure:
-
Run the command to view planned changes:
terraform plan
If the resource configuration descriptions are correct, the terminal will display a list of the resources to modify and their parameters. This is a test step. No resources are updated.
-
If you are happy with the planned changes, apply them:
-
Run the command:
terraform apply
-
Confirm the update of resources.
-
Wait for the operation to complete.
-
All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console
. -
Prepare the initialization action
-
Create the initialization action file named
geesefs_mount.sh
accepting two positional arguments: the name of the Object Storage bucket and the host's file system directory where you are going to mount it.#!/bin/bash set -e BUCKET=$1 MOUNT_POINT=$2 # Downloading GeeseFS wget https://github.com/yandex-cloud/geesefs/releases/latest/download/geesefs-linux-amd64 -O /opt/geesefs chmod a+rwx /opt/geesefs mkdir -p "${MOUNT_POINT}" # Preparing a script to run on every boot BOOT_SCRIPT="/var/lib/cloud/scripts/per-boot/80-geesefs-mount.sh" echo "#!/bin/bash" >> ${BOOT_SCRIPT} echo "/opt/geesefs -o allow_other --iam ${BUCKET} ${MOUNT_POINT}" >> ${BOOT_SCRIPT} chmod 755 ${BOOT_SCRIPT} # Running the script ${BOOT_SCRIPT}
-
Upload the
geesefs_mount.sh
file to the previously created Object Storage bucket.
Create a cluster that would use the initialization action
Create a Yandex Data Processing cluster with the following settings:
-
In the Version field, select
2.0
. -
In the Service account field, select the service account you previously created.
-
In the Custom scripts field, click Add and set the script parameters:
-
In the URI field, specify the path to the script file in the bucket, such as:
s3a://<bucket_name>/geesefs_mount.sh
-
In the Arguments field, specify the name of the previously created bucket and
/mnt/test
as your mount point. Arguments are specified on separate lines:<bucket_name> /mnt/test
-
-
In the Bucket name field, select the previously created bucket.
-
In the Subclusters menu, enable Public access in the settings. This will enable you to connect to subcluster hosts without an intermediate virtual machine.
-
In the
data-processing-init-actions-geesefs.tf
file, set the value for this variable as follows:create_cluster
=1
. -
Check that the Terraform configuration files are correct using this command:
terraform validate
If there are any errors in the configuration files, Terraform will point them out.
-
Create the required infrastructure:
-
Run the command to view planned changes:
terraform plan
If the resource configuration descriptions are correct, the terminal will display a list of the resources to modify and their parameters. This is a test step. No resources are updated.
-
If you are happy with the planned changes, apply them:
-
Run the command:
terraform apply
-
Confirm the update of resources.
-
Wait for the operation to complete.
-
All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console
. -
Check bucket availability.
-
After the cluster status changes to Alive, connect via SSH to any of its hosts as the
ubuntu
user. -
To make sure that the bucket has been mounted successfully, run the command:
ls /mnt/test
As a result, it will output the list of objects stored in the root folder of the bucket. In this case, the file name
geesefs_mount.sh
.
Delete the resources you created
Tip
Before deleting the infrastructure, manually delete all objects from the bucket.
Delete the resources you no longer need to avoid paying for them:
- Delete the Yandex Data Processing cluster.
- If you used static public IP addresses to access the cluster hosts, release and delete them.
- Delete the Object Storage bucket.
- Delete the service account.
-
In the terminal, go to the working directory with the
data-processing-init-actions-geesefs.tf
configuration file. -
Delete the resources using this command:
terraform destroy
-
Type
yes
and press Enter.All the resources described in the
data-processing-init-actions-geesefs.tf
configuration file will be deleted.