My name is Oliver Grower. I'm technical marketing engineer at Netup for Google Cloud Netup Volumes and I'm here today to present you um how to use Terraform to manage Google Cloud NetUP volumes resources.So what are we covering? First the welcome when we quickly talk about what NetUP volumes is. Then we will have a look at the Terraform provider and finally a short demo. Google Cloud NetUP Volumes is a fully managed NAS service. So, a file sharing service for NFS and SMB file shares built into Google Cloud. It can handle all kinds of um file sharing workloads. It's fully integrated into Google including IM, G-Cloud support, Google Cloud Console, billing, logging, billing, logging, billing, logging, the full integration. It has a very powerful data protection and data management capabilities like instant snapshots, volume reversion, volume cloning, volume replication, volume backup and you can protect your data with access control and um customer managed encryption keys. This is how the um service looks into in the Google cloud console. So like many other Google services. So you have your cloud console. You have all your projects listed here. Uh as the kind of services listed here and here we chose the netup volume service and here you can see all the resources which are available in the service and now our objective is to manage them using terraform.um is a tool which allows you to manage resources via um declaration by code. So basically you declare how your environment should look likein a text file. You run the Terraform tool on it and it will read your existing environment, compare it to the definition on how you want it to be to look like and then yeah it will do all the necessary changes to make the reality correspond your intent for that. Terraform deploys providers think drivers uh for all kinds of services. Google has such a terraform provider. It's a Google provider. It manages hundreds of different Google resources [snorts] and part of it is um all the netup volume resources. So they all start with Google NetUp and then you basically will find resources for all the resources in the service. So things like storage pools, volumes, snapshot, replication,backup, AD and so on. So if you go to the standard documentation website of a Google provider, you will find this documentation and for each resource, you will also find example code on how to use it and a definition of all the mandatory and optional attributes you can specify. [snorts]And now let's start a short demo. So here we see I [clears throat] have a project which is basically empty. No storage pools, no resources. Here I already prepared some terraform code in I will deploy some resources into the region Europe West 6. [snorts] So first I read my VPC my existing VPC within the VPC I'm creating a storage pool called Google next pool of size 2 terabyteand within that pool I create an NFSV3 volume with a size of 200 GBTE. So now I'm using the terraform apply command. It reads that definition compares it with reality. So here you see nothing is there. So it is adding multiple resources, a storage pool and a volume.And now it basically creates these resources in the right order because the pool the volume will live inside the volume. So we need it needs to create the pool first and then the volume. But the terraform tool will take care of all these dependencies by itself. So here so we did a refresh. So you see the pool was created with two terabyte in size in Europe bestex wics just like um we defined and here the volume is now also done after 20 seconds let let's have a look at the volume. So here is for volume also correct region correct size everything.[clears throat] Next we will change the volume size. So we increase the number size from 200 to 500 gabyte. We save the content and we rerun the terraform apply tool again. it real it will say hey look one resource will be changed not added not deleted but changed the size will increase from 200 to 500 GB so it automatically figured out what needs to be done to change we deploy deployed resources to reflect your intention in the code and as you can see here it's already 500 GB Next, I want to create an SMB volume. To create an SMB volume, I first need an Active Directory policy, which are basically instructions on how to connect to Active Directory because that's a prerequisite for an SMB volume. And finally to attach that Active Directory to the storage pool we already created. And if you do that then we can create an SMB volume. So here I did all the necessary changes like um two resources will be added which is the active directory policy and the SMB volume and one resource will be changed which is the storage pool which gets VA a policy attached. And so here you see here VAD policy was already created. The modification of the pool is al also done. And now the SMB volume will be created. And after a few seconds that will also be done and we will see a second volume on top of the existing NFSV3 volume. We will have an SMB volume. Let's update the volume list again. And here we have an NFS volume and an SMB volume. And that concludes the demo. Um again look into the documentation of a provider. Um Netup Volumes is a worldclass file sharing solution on Google Cloud. That's takeaway number one. Um, the resources of that service can be managed via the UI web interface, via G-Cloud, via an API or via Terraform which we demoed here. And you can read more starter information in my blog post with the link you can find here. So, happy terraforming.