Next to the different operating modes, a number of options are available that influence the operation. Not all options have an impact on all operating modes.
In case that you want to specify the list of nodes not interactively but on the command line, you can use the option
--nodes together with a comma-separated list of hostnames and/or IP addresses to do so.
If this option is provided, existing configuration files like
/etc/dis/dishosts.conf will not be considered.
By default, the complete software stack will be installed to /opt/DIS. To change the installation path, use the
This will install into
/usr/dolphin. It is recommended to install into a dedicated directory that is located on a local storage device (not mounted via the network). When doing a full cluster install (
--install-all, or default operation), the same installation path will be used on all nodes, the frontend and potentially the installation machine (if different from the frontend).
If you are re-running an installation for which the binary RPM package have already been built, you can save time by not building these packages again, but use the existing ones. The packages have to be placed in two subdirectories
frontend_RPMS, just as the SIA does. Then, provide the name of the directory containing these two subdirectories to the installer using the
The installer does not verify if the provided packages match the installation target, but the RPM installation itself will fail in this case.
It is possible to specify the number of Megabytes per node that the low-level interconnect driver
dis_irm should allocate on startup for exportable memory segments. The amount of this memory determines i.e. how many SuperSockets-based sockets can be opened. The default setting was chosen to work well with clustered databases. Change this setting if you know you will need more memory to be exported, or will use a very high number of stream sockets per node (datagram sockets are multiplexed and thus need less resources).
By default, the driver allocates
8 + N*MB Megabytes of memory, with
N being the number of nodes in the cluster and
MB = 4 by default. A maximum of 256MB will be allocated. The factor MB can be specified on installation using the
On a 16 node cluster, this will make the
8 + 16*8 = 136MB on each node.
The operating system can not use preallocated memory for other purposes - it is effectively invisible.
MB to -1 will disable all modifications to this configuration option, and the fixed default of 16MB will be preallocated independently from the number of nodes. Setting MB to 0 is also valid (8 MB will be allocated).
This option changes a value in the module configuration file
dis_irm.conf. It is only effective on an initial installation. An existing configuration file
dis_irm.conf will never be changed, i.e. when upgrading an existing installation.
If the installed packages should be replaced with the packages build from the SIA you are currently using even if the installed packages are more recent (have a higher version number), use the option
--enforce. This will enforce the installion of the same software version (the one delivered within this SIA) on all nodes and the frontend no matter what might be installed on any of these machines. Examples:
When doing a full cluster install, the installation script will automatically look for the cluster configuration files
networkmanager.conf in the default path
/etc/dis on the installation machine. If these files are not stored in the default path (i.e. because you have created them on another machine or received them from Dolphin and stored them someplace else), you can specify this path using the
The script will look for both configuration files in
If you need to specify the two configuration files being stored in different locations, use the options
<filename>, respectively, to specify where each of the configuration files can be found.
In case you want to run the installation unattended, you can use the
--batch option to have the script assume the default answer for every question that is asked. Additionally, you can avoid most of the console output (but still have the full logfile) by providing the option
--quiet. This option can be very useful if you are upgrading an already installed cluster. I.e., to enforce the installation of newly compiled RPM packages and reboot the nodes after the installation, you could issue the following command on the frontend:
# ./DIS_install_<version> --batch --reboot --enforce >install.log
After this command returns, your cluster is guaranteed to be freshly installed unless any error messages can be found in the file
When building RPMs only (using the
--build-rpm option), it is possible to specify that no GUI-applications (
dis_netconfig) should be build. This is done by providing the
--disable-gui option. This removes the dependency on the QT libraries and header files for the build process Example:
To remove all software that has been installed via SIA, simply use the --uninstall option:
This will remove all packages from the node, and stop all drivers (if they are not in use). A more thorough cleanup, including all configuration data and possible remainings of non-SIA installations, can be achieved with the
This option is a superset of