HP 1032 ClusterPack V2.4 Tutorial - Page 60

Adding software bundles to Golden Images

Page 60 highlights

To install a CPACK-FILES bundle on an individual compute node, or group of compute nodes, the clsh utility can be used: % /opt/clusterpack/bin/clsh -C "/usr/sbin/swinstall -s :/var/opt/clusterpack/depot " References: z 3.1.5 clsh - Runs commands on one, some, or all nodes in the cluster. z 1.5.4 Adding software bundles to Golden Images Back to Top 1.5.4 Adding software bundles to Golden Images Software bundles created with SD can be asociated with a Golden Image, and will be installed on the compute nodes following an installation with that image. The software bundles should be swcopy'd to /var/opt/clusterpack/depot. A list of all the bundels that are available in the depot can be found using:e % /usr/sbin/swlist -l bundle @ /var/opt/clusterpack/depot The bundles are associated with an image using the sysimage_register command: % /opt/clusterpack/bin/sysimage_register -i -b The "-b bundle" option can be repeated on the command line to associate additional SD bundles to the image. The bundles will remain associated with the image until sysimage_register is run again. The bundle should include the full revision of the bundle (i.e. bundle,r=revision), to avoid conflicts during installation. Back to Top Index | Administrators Guide | Users Guide | Tool Overview | Related Documents | Dictionary Copyright 1994-2004 hewlett-packard company

  • 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

Index
|
Administrators Guide
|
Users Guide
|
Tool Overview
|
Related Documents
|
Dictionary
Copyright 1994-2004 hewlett-packard company
To install a CPACK-FILES bundle on an individual compute node, or group of compute nodes,
the clsh utility can be used:
%
/opt/clusterpack/bin/clsh -C <node(s)> "/usr/sbin/swinstall -s
<manager_ip>:/var/opt/clusterpack/depot <CPACK-FILES bundle
version>"
References:
3.1.5 clsh
-
Runs commands on one, some, or all nodes in the cluster.
1.5.4 Adding software bundles to Golden Images
Back to Top
1.5.4 Adding software bundles to Golden Images
Software bundles created with SD can be asociated with a Golden Image, and will be installed
on the compute nodes following an installation with that image. The software bundles should
be swcopy'd to /var/opt/clusterpack/depot. A list of all the bundels that are available in the
depot can be found using:e
%
/usr/sbin/swlist -l bundle @ /var/opt/clusterpack/depot
The bundles are associated with an image using the sysimage_register command:
%
/opt/clusterpack/bin/sysimage_register -i <image> -b <bundle>
The "-b bundle" option can be repeated on the command line to associate additional SD bundles
to the image. The bundles will remain associated with the image until sysimage_register is run
again. The bundle should include the full revision of the bundle (i.e. bundle,r=revision), to
avoid conflicts during installation.
Back to Top