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
Copy file name to clipboardExpand all lines: content/blog/highly-available-nfs-workload-on-hpe-greenlake-for-private-cloud-enterprise-using-serviceguard-for-linux.md
+52-25Lines changed: 52 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -339,13 +339,27 @@ Terraform init
339
339
340
340
341
341
Before you can use Terraform, you need to initialize it from the configuration file we have created. This is done with the following step:
342
-
terraform init
342
+
`terraform init`
343
+
344
+
##
343
345
Terraform ready to plan
346
+
347
+
344
348
To validate your configuration file, it is recommended to run the terraform validate command. Once ready, the terraform plan command will provide the a summary of the deployment that would be built when terraform apply method would be used.
345
349
Once you agree with the plan and confirm, you can apply the configuration.
346
-
Terraform ready to apply
347
-
The command you need to use is now: terraform apply. This will rerun the plan command, then prompt you to confirm before it starts building what is in the plan:
350
+
351
+
352
+
## Terraform ready to apply
353
+
354
+
355
+
The command you need to use is now:
356
+
357
+
`terraform apply`
358
+
359
+
This will rerun the plan command, then prompt you to confirm before it starts building what is in the plan:
348
360
Here is some sample output from the terraform apply command:
361
+
362
+
```
349
363
Do you want to perform these actions?
350
364
Terraform will perform the actions described above.
351
365
Only 'yes' will be accepted to approve.
@@ -364,37 +378,48 @@ hpegl_vmaas_instance.my_drbd\[0]: Creation complete after 2m8s \[id=3111]
364
378
hpegl_vmaas_instance.my_quorum\[0]: Creation complete after 2m8s \[id=3108]
Once the command completes, your virtual machines are ready.
368
386
369
-
Configuring a Highly Available NFS solution
387
+
# Configuring a Highly Available NFS solution
370
388
371
389
Now that the VMs are provisioned, we can now deploy HPE Serviceguard for Linux on these VMs to create a cluster to provide high availability for the applications running on the VMs, NFS server in this case.
372
390
373
-
Installing Serviceguard for Linux
391
+
## Installing Serviceguard for Linux
392
+
393
+
374
394
Serviceguard and all its components can be installed using Ansible playbooks
Master playbook` site.yml `contains the roles which will be executed for the inventory defined in hosts.
384
409
When the master playbook is run, version specified in the parameters file will be installed. The parameters for the master playbook, roles are configured in group_vars/all.yml. We will now look into some of the fields in this file which needs to be configured.
385
410
We should configure the version of Serviceguard to be installed, in this case SGLX 15.10.00 will be installed.
386
-
sglx_version : 15.10.00
411
+
`sglx_version : 15.10.00`
387
412
Now provide the Serviceguard for Linux ISO location on the controller node
Serviceguard installation mandates a replicated user configuration. As part of the installation, a replicated user for Serviceguard Manager (sgmgr) is created on the hosts and the password for the same can be configured under the below parameter.
`Serviceguard installation mandates a replicated user configuration. As part of the installation, a replicated user for Serviceguard Manager (sgmgr) is created on the hosts and the password for the same can be configured under the below parameter.
Once these parameters are populated, one can modify the hosts file to add the 2 VMs that were provisioned earlier where the cluster will be formed, and the quorum server that was provisioned earlier. In this case, it’s as shown below
409
-
\[sglx-storage-flex-add-on-hosts]
434
+
`[sglx-storage-flex-add-on-hosts]
410
435
drbd-0-808
411
-
drbd-1-808\
412
-
\[sglx-cluster-hosts:children]
436
+
drbd-1-808`\
437
+
`[sglx-cluster-hosts:children]
413
438
sglx-storage-flex-add-on-hosts
414
-
\[quorum-server-hosts]
439
+
[quorum-server-hosts]
415
440
drbd-0-qs-808
416
-
\[primary]
441
+
[primary]
417
442
drbd-0-808
418
-
\[secondary]
419
-
drbd-1-808
443
+
[secondary]
444
+
drbd-1-808`
420
445
When the parameters specified above are configured, playbook site.yml can be run from the directory where the repository is cloned on the ansible control node.
This completes the Serviceguard software installation.
424
449
425
-
Configuring data replication using Serviceguard flex Storage Add-on
450
+
## Configuring data replication using Serviceguard flex Storage Add-on
451
+
452
+
426
453
Serviceguard for Linux Flex Storage Add-on is a software-based, shared-nothing, replicated storage solution that mirrors the content of block devices. NFS server export data will be replicated to all Serviceguard cluster nodes using this add-on. Ansible snippet below can be used to configure the replication.
0 commit comments