Bright Cluster Manager makes it easy to perform an Add-On installation. This article shows you how.
Let's get started.
First, install the install-bright package from the DVD.
This software has dependencies on other packages, which can be installed from the Bright DVD or from the EPEL repository. I'm going to use the EPEL repository so I'll install it first.
Download and install the EPEL repository.
[root@centos6 ~]# wget http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
[root@centos6 ~]# rpm -Uvh epel-release-6-8.noarch.rpm
Next, install the install-bright package.
[root@centos6 ~]# yum install /mnt/dvd/addon/bright-installer-6.0-246_cm6.0.noarch.rpm
Now we're ready to run the install-bright command, which was installed when you installed the install-bright package.
Before you proceed, un-mount your DVD.
The install-bright command access your DVD as a block device (/dev/sr0 in this case).
[root@centos6 ~]# unount /mnt/dvd
[root@centos6 ~]# install-bright -d /dev/sr0
Validating installation source ..... [ OK ]
Creating local repository ..... [ OK ]
Install the follow pre-requisites
----------------------------------------
lynx
dialog
bind
nfs-utils
mysql-server
xorg-x11-server-Xorg
tcl
redhat-lsb
Install the dependencies reported by the install-command.
[root@centos6 ~]# yum install lynx dialog bind nfs-utils mysql-server xorg-x11-server-Xorg \
tcl redhat-lsb
Now that you've installed the dependencies, you're ready to run the install-bright command again. Note that we've specified the -o option, which overwrites the local repository created the first time we ran install-bright.
[root@centos6 ~]# install-bright -d /dev/sr0 -o
Validating installation source ..... [ OK ]
Creating local repository ..... [ OK ]
INFO/ERROR/WARNING:
--------------------
ERROR:
MySQL is not running. Please start the mysql server,
and set the mysql root password, if not already done.
--------------------
Okay, let's start the MySQL server.
[root@centos6 ~]# service mysqld start
Initializing MySQL database: Installing MySQL system tables...
OK
Filling help tables...
OK
To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER!
To do so, start the server, then issue the following commands:
/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h centos6.zohallt.com password 'new-password'
Alternatively you can run:
/usr/bin/mysql_secure_installation
which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.
See the Bright Admin Manual for more instructions.
You can start the MySQL daemon with:
cd /usr ; /usr/bin/mysqld_safe &
You can test the MySQL daemon with mysql-test-run.pl
cd /usr/mysql-test ; perl mysql-test-run.pl
Please report any problems with the /usr/bin/mysqlbug script!
[ OK ]
Starting mysqld: [ OK ]
Set the MySQL administrative password.
Make sure you remember what you set it to. You'll need to provide it in the next step.
[root@centos6 ~]# /usr/bin/mysqladmin -u root password 'mypasswd'
[root@centos6 ~]# /usr/bin/mysqladmin -u root -h centos6.zohallt.com password 'mypasswd'
Run the install-bright command again.
[root@centos6 ~]# install-bright -d /dev/sr0 -o
Validating installation source ..... [ OK ]
Creating local repository ..... [ OK ]
Bright Cluster Manager Product Key Activation
---------------------------------------------
Product key [XXXXX-XXXXX-XXXXX-XXXXX-XXXXX]: 006128-237772-591449-845490-145565
License exists, do you wish to use existing license? [y(yes)/n(no)]: n
License Parameters
------------------
Country Name (2 letter code) []: US
State or Province Name (full name) []: California
Locality (city) []: San Jose
Organization Name (e.g. company) []: Bright Computing
Organization Unit (e.g. department) []: Development
Cluster Name []: Add-on Demo
MAC address [??:??:??:??:??:??]: 08:00:27:D7:14:AF
Submit certificate request to Bright Computing? [y(yes)/n(no)]: y
Contacting license server ... License granted.
License has been installed in /cm/local/apps/cmd/etc/
Will continue in 1 second(s))
Do you agree with the license terms and conditions? [y(yes)/n(no)/r(read)]: y
-----------------------------------------------------------------
Please be aware that the Bright Cluster Manager will re-write the
following configuration on your system:
- Update network configuration files.
- Start a DHCP server on the management network.
- Update syslog configuration
-----------------------------------------------------------------
Do you wish to proceed with the installation setup? [y(yes)/n(no)]: y
Management network parameters
-----------------------------
Network Name [internalnet]:
Base Address [10.141.0.0]:
Netmask Bits [16]:
Domain Name [eth.cluster]:
Management interface parameters
-------------------------------
Interface Name [eth0]:
IP Address [10.141.255.254]:
External network parameters
---------------------------
Network Name [externalnet]:
Base Address [DHCP]: 192.168.2.0
Netmask Bits [24]:
Domain Name []: zohallt.com
External interface parameters
-----------------------------
Interface Name [eth1]:
IP Address [DHCP]: 192.168.2.212
External name servers list (space separated)
--------------------------------------------
List [192.168.2.6]:
Head node hardware vendor
-------------------------
Vendor Name [other]:
Root password
-------------
Please enter the cluster root password:
MySQL root password
-------------------
Please enter the MySQL root password:
The following Bright packages will be installed
-----------------------------------------------
acml | acml-gcc-64 | acml-open64-64
atftp-server | blacs-openmpi-gcc-64 | blacs-openmpi-open64-64
blas-gcc-64 | blas-open64-64 | bonnie++
cciss_vol_status | cluster-tools | cmdaemon
cmdaemon-cmsh | cmdaemon-config-master | cmdaemon-remotecm
cmdaemon-pythonbinding | pythoncm-dist | cmgui
cmgui-dist | confuse | cmbios
cmburn | verify-license | cm-admin-manual
cm-user-manual | cm-busybox | cm-config-cm
cm-config-cmsupport-files | cm-config-ldap-client-master | cm-config-limits
cm-config-man | cm-config-minicom | cm-config-motd
cm-config-mysql | cm-config-named | cm-config-network-master
cm-config-nfsserver | cm-config-rootfiles | cm-config-ssh
cm-config-sysctl | cm-config-syslog | cm-config-dhclient
cm-config-yum | cm-crontabs-master | cm-dhcp
cm-logo | cm-master | cm-openssl
cm-tests | cm-webportal | cm-php-pam
cm-workload | conman | dbench
env-modules | fftw2-gcc-64 | fftw3-gcc-64
fftw2-open64-64 | fftw3-open64-64 | freeipmigcc-recent
globalarrays-gcc-openmpi-64 | globalarrays-open64-openmpi-64
gsoap | hdf5 | hpl
hpl | imb | intel-tbb-oss-intel64
intel-tbb-oss-ia32 | iozone | ipmitool
lapack-gcc-64 | lapack-open64-64 | libnet
lm_sensors | memtester | mpich-ge-gcc-64
mpich-ge-open64-64 | mpich2-ge-gcc-64 | mpich2-ge-open64-64
mysql++ | mysql++-devel | netcdf-gcc-64
netcdf-open64-64 | netperf | net-snmp-recent
node-installer | node-installer-nfsroot | openldap-servers
perl-Config-IniFiles | rsync-cm | scalapack-gcc-64
scalapack-open64-64 | sdparm | sge
sge-client | torque | torque-client
torque2 | torque2-client | pbspro
pbspro-green | munge | slurm
slurm-client | slurm-munge | slurm-plugins
slurm-slurmdbd | slurm-sql | mpiexec
shorewall | sipcalc | stresscpu
open64 | hwloc | vsmpimage
gotoblas | sntp | sshpass
buildmatic-common | buildmatic-6.0-stable | intel-wired-ethernet-drivers
intel-cluster-checker | intel-cluster-runtime | cm-config-intelcompliance-master
mlnx-ofed | mvapich-gcc-64 | mvapich-open64-64
mvapich2-gcc-64 | mvapich2-open64-64 | openmpi-geib-gcc-64
openmpi-geib-open64-64 | qlgc-ofed | openvpn
boto | cm-python-elementtree
Summary of cluster configuration
--------------------------------
Cluster configuration saved in /root/.brightcm/build-config.xml
---------------------------------------------------------------
Do you wish to proceed with the above configuration? [y(yes)/n(no)/v(view)]:y
...
[output omitted]
...
Transaction Summary
================================================================================
Install 152 Package(s)
Total download size: 1.6 G
Installed size: 4.7 G
Downloading Packages:
--------------------------------------------------------------------------------
Total 63 MB/s | 1.6 GB 00:26
Running rpm_check_debug
Running Transaction Test
Transaction Check Error:
file /usr/lib64/libsensors.so.4 from install of lm_sensors-3.3.2-69_cm6.0.x86_64 conflicts with file from package lm_sensors-libs-3.1.1-10.el6.x86_64
file /usr/include/sensors/error.h from install of lm_sensors-3.3.2-69_cm6.0.x86_64 conflicts with file from package lm_sensors-devel-3.1.1-10.el6.x86_64
file /usr/include/sensors/sensors.h from install of lm_sensors-3.3.2-69_cm6.0.x86_64 conflicts with file from package lm_sensors-devel-3.1.1-10.el6.x86_64
Error Summary
-------------
Failed to install packages
Installation of bright packages failed
--------------------
Remove the conflicting packages.
[root@centos6 ~]# rpm -e --nodeps lm_sensors-libs-3.1.1-10.el6.x86_64
[root@centos6 ~]# rpm -e --nodeps lm_sensors-devel-3.1.1-10.el6.x86_64
Run the install-bright command for the final time.
[root@centos6 ~]# install-bright -d /dev/sr0 -o
Validating installation source ..... [ OK ]
Creating local repository ..... [ OK ]
Updating database authentication ..... [ OK ]
Setting up MySQL database ..... [ OK ]
Starting syslog ..... [ OK ]
Initializing cluster mamangement daemon ..... [ OK ]
Generating admin certificates ..... [ OK ]
Starting cluster management daemon ..... [ OK ]
***
Congratulations!
Bright Cluster Manager has been installed successfully,
and this host is now a Bright head node.
To be able to provision nodes, a software image must be created
using a base image of your choice, or using the base tar image
that is included on the Bright DVD. Please refer to the Administrator's
manual for instructions on how to use 'the cm-create-image' utility to
create custom software images.
Admin and User Manuals are available at the following
location:
http://support.brightcomputing.com/manuals
***
[root@centos6 ~]#
That's it. You can now log in and use your cluster.
Here are a couple of caveats:
You will need to log in with a new shell to be able to load modules.
You will next need to add an image, but that's covered in a separate How to.
