Skip to content

Commit 9b3ef86

Browse files
Update Blog “highly-available-nfs-workload-on-hpe-greenlake-for-private-cloud-enterprise-using-serviceguard-for-linux”
1 parent b154541 commit 9b3ef86

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

content/blog/highly-available-nfs-workload-on-hpe-greenlake-for-private-cloud-enterprise-using-serviceguard-for-linux.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -171,15 +171,35 @@ curl -s -k -X POST \
171171
Querying for infrastructure components
172172

173173
Your next step with the TF file is to query the HPE GreenLake provider to collect information needed to create your first VM instance. From the documentation, you can see that you need to gather the following information:
174+
175+
174176
• Cloud ID
177+
178+
175179
• Group ID
180+
181+
176182
• Layout ID
183+
184+
177185
• Plan ID
186+
187+
178188
• Instance type code
189+
190+
179191
• Network ID
192+
193+
180194
• Resource Pool ID
195+
196+
181197
• Template ID
198+
199+
182200
• Folder Code
201+
202+
183203
For this, you will use the Terraform data statements. For example, the following statement retrieves the Cloud ID and stores it (in variable called cloud), which we can later retrieve using: data.hpegl_vmaas_cloud.cloud.id
184204

185205
```

0 commit comments

Comments
 (0)