You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| prime_hostname | Hostname or IP address of primary cluster. |`string`|| Yes |
22
22
| prime_fsxid | FSx ID of the primary cluster. |`string`|| Yes |
23
-
| prime_clus_name | This is the name of the cluster given for ONTAP TF connection profile. This is a user created value, that can be any string. It is referenced in many ONTAP TF resources |`string`| primary_clus | Yes |
23
+
| prime_clus_name | This is the name of the cluster given for ONTAP TF connection profile. This is a user created value, that can be any string. It is referenced in many ONTAP TF resources |`string`| primary_clus | Yes |
24
24
| prime_svm | Name of the primary SVM for the volumes that will be replicated. |`string`|| Yes |
25
25
| prime_cluster_vserver | Name of the ONTAP cluster vserver for intercluster LIFs in the primary cluster. Can be found by running `network interface show` on the primary cluster. It will have the format FsxId################# |`string`| Yes |
26
26
| prime_aws_region | AWS region of the primary FSx ONTAP system |`string`|| Yes |
@@ -60,6 +60,113 @@ SnapMirror replication requires **ICMP** and ports **11104** and **11105**.
60
60
| dr_cidr_for_sg | The VPC ID where the DR FSxN and security group will be created. |`string`| 10.0.0.0/8 | No |
61
61
| dr_source_sg_id | The ID of the security group to allow access to the FSxN file system. Set to an empty string if you want to use the cidr_for_sg as the source. |`string`|| No |
62
62
63
+
## Usage
64
+
65
+
#### 1. Clone the repository
66
+
67
+
In your server's terminal, navigate to the location where you wish to store this Terraform repository, and clone the repository using your preferred authentication type. In this example we are using HTTPS clone:
This directory represents a standalone Terraform module. Run the following command to initialize the module and install all dependencies:
82
+
83
+
```shell
84
+
terraform init
85
+
```
86
+
87
+
A succesfull initialization should display the following output:
88
+
89
+
```shell
90
+
91
+
Initializing the backend...
92
+
Initializing modules...
93
+
94
+
Initializing provider plugins...
95
+
- Reusing previous version of netapp/netapp-ontap from the dependency lock file
96
+
- Reusing previous version of hashicorp/aws from the dependency lock file
97
+
- Using previously-installed netapp/netapp-ontap v1.1.4
98
+
- Using previously-installed hashicorp/aws v5.69.0
99
+
100
+
Terraform has been successfully initialized!
101
+
102
+
You may now begin working with Terraform. Try running "terraform plan" to see
103
+
any changes that are required for your infrastructure. All Terraform commands
104
+
should now work.
105
+
106
+
If you ever set or change modules or backend configuration for Terraform,
107
+
rerun this command to reinitialize your working directory. If you forget, other
108
+
commands will detect it and remind you to do so if necessary.
109
+
110
+
```
111
+
112
+
You can see that Terraform recognizes the modules required by our configuration: `hashicorp/aws` and `hashicorpt/netapp-ontap`.
113
+
114
+
#### 4. Create Variables Values
115
+
116
+
- Copy or Rename the file **`terraform.sample.tfvars`** to **`terraform.tfvars`**
117
+
118
+
- Open the **`terraform.tfvars`** file in your preferred text editor. Update the values of the variables to match your preferences and save the file. This will ensure that the Terraform code deploys resources according to your specifications.
0 commit comments