HP 1032 ClusterPack V2.4 Tutorial - Page 63

Remove Nodes from the Cluster

Get HP 1032 PDF manuals and user guides View all HP 1032 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 63 highlights

In the later case, the utility will prompt you (for each node in the cluster) whether to boot it or skip it. To boot a compute node with a system image, use the "-i" option to clbootnodes and specify the image. The image must have been created by sysimage_create and registered with sysimage_register. You can see a list of registered images by executing: The full path of the image must be given to clbootnodes: Note: After installing an image with clbootnodes -i, it may be necessary to wait several minutes after clbootnodes returns before running compute_config as the daemons may need time to start and stablize Step 4 Invoke /opt/clusterpack/bin/compute_config on Management Server This tool is the driver that installs and configures appropriate components on every Compute Node. It is invoked with the "add node" option -a as follows: % /opt/clusterpack/bin/compute_config -a This command configures the new node with the specified hostname to serve as a Compute Node in the cluster. The '-a' option can be repeated if more than one node needs to be added to the system. For more information on the usage of compute_config, refer to the man pages. % man compute_config Step 5 Invoke /opt/clusterpack/bin/finalize_config on Management Server Finalize and validate the addition of the new node to ClusterPack: % /opt/clusterpack/bin/finalize_config This step completes the configuration process, does verification checks on the Cluster Management Software, and validates the addition of the new node. Back to Top 1.6.2 Remove Node(s) from the Cluster Compute Nodes are removed from ClusterPack by using the three stage process that is used for installation:

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
In the later case, the utility will prompt you (for each node in the cluster) whether to boot it or
skip it.
To boot a compute node with a system image, use the "-i" option to clbootnodes and specify the
image. The image must have been created by sysimage_create and registered with
sysimage_register. You can see a list of registered images by executing:
The full path of the image must be given to clbootnodes:
Note:
After installing an image with clbootnodes -i, it may be necessary to wait several
minutes after clbootnodes returns before running compute_config as the
daemons may need time to start and stablize
Step 4 Invoke /opt/clusterpack/bin/compute_config on Management Server
This tool is the driver that installs and configures appropriate components on every Compute
Node. It is invoked with the "add node" option -a as follows:
%
/opt/clusterpack/bin/compute_config -a <new_node_name>
This command configures the new node with the specified hostname to serve as a Compute Node
in the cluster.
The '-a' option can be repeated if more than one node needs to be added to the system.
For more information on the usage of compute_config, refer to the man pages.
%
man compute_config
Step 5 Invoke /opt/clusterpack/bin/finalize_config on Management Server
Finalize and validate the addition of the new node to ClusterPack:
%
/opt/clusterpack/bin/finalize_config
This step completes the configuration process, does verification checks on the Cluster
Management Software, and validates the addition of the new node.
Back to Top
1.6.2 Remove Node(s) from the Cluster
Compute Nodes are removed from ClusterPack by using the three stage process that is used for
installation: