Quantcast
Channel: Intel Developer Zone Articles
Viewing all articles
Browse latest Browse all 3384

SMB Platform Upgrade Instructions 10.8.0

$
0
0

Background

Release Notes

10.8.0

Download link

Download the following files from registrationcenter.intel.com. Use the serial number that is sent to you via email to begin the download process.

saffron-install_10_8_0.bin     
rhel6-setup-lite.tgz                

UpgradeSpecifics

  • Step 1. Uninstall your current version of SMB.
  • Step 2. Update the smbtool utility in the POSTOS Setup Script (rhsetup) IMPORTANT: This is a centralized logging-specific upgrade only. Follow the instructions below. 
  • Step 3: Install SMB 10.8.0.

General Upgrade Notes:

  • For site installations with both SMB and Streamline, ensure that the installation meets inter-product dependencies as defined by the Saffron Product Support team. 
  • The SMB installer maintains site-specific customizations in the ~saffron/smb/conf and ~saffron/smb/catalina/conf directories.
  • In general, only saffron user permissions (not root) are required to upgrade the SMB installer.
  • DO NOT RUN THE RHSETUP SCRIPT. See the instructions below for extracting rhsetup and then installing the updated smbtool utility. The root user is required to perform this upgrade.
  • Saffron recommends testing this first in your development environment to verify operation with site-specific environment and components.

Upgrade SMB 

Pre-Steps

1.  Review the 10.8.0 Release Notes for additional information that extend the instructions here. If the upgrade is over multiple releases, e.g., from 10.2.0 to 10.4.0, review each intervening set of release notes for specific installation instructions.  

2.  Download the SMB installer (saffron-install_10_8_0.bin) using the link provided in your registration email and copy to the head node of the SMB cluster in the Saffron home directory. This can be done in several ways and might be site-specific, but Saffron recommends using as few hops as possible to put the SMB installer in the ~saffron directory. 

3.  Ensure that the provided SMB installer is executable. Log in as the saffron user and enter the following command:

$ chmod u+x saffron-install_10_8_0.bin 
 

Uninstall SMB

4.  Shut down the cluster from the admin node. Log in as the saffron user and enter the following commands:

cluster stop

5.  Create a cluster-wide global backup of the Space configurations. Use the SMB archive utility. For example:

archive -g -p archivefilename -d bkup      

This tells the archive utility to make a cluster-wide global back up and place it in the bkup directory.

An archive file called archivefilename-20161017120511 is created.

If you need to restore the global backup in the future, enter the following command:

archive -r archivefilename bkup/archivefilename-20161017120511

For more information, refer to the archive information by entering the following on the command line:

man archive

6. Uninstall the current release. As the saffron user, enter the following command:

uninstall

Answer the prompt verifying the uninstall with yes.
 

Update the smbtool utility

7.  The smbtool utility (for systems tasks) in the PostOS setup (rhsetup) script has been updated to include the new centralized logging feature. Execute the following steps on all nodes in the cluster. Log in as the root user.

a.  Download rhsetup (rhel6-setup-lite.tgz) using the link provided in your registration email.

b.  Copy rhsetup into the /tmp directory of the admin node and each worker node.

cp rhel6-setup-lite.tgz /tmp 

c.  Untar rhsetup. 

tar xzf rhel6-setup-lite.tgz 

d.  Locate rhel6-setup/rpms/smbtool-8.0-8.x86_64.rpm.  

e.  Update smbtool.

rpm -e smbtool 
rpm -ivh smbtool-8.0-8.x86_64.rpm
 

Install SMB

8.  Run the installer. Logged in as the saffron user in the home directory, enter the following command:

./saffron-install_10_8_0.bin

This unpacks the installer including its embedded rpm for smb, runs a post install procedure, and copies out the software to all nodes in the cluster.

9.  Review configuration files in the following directories to see if they have been modified since the last upgrade. Modified files are appended with as-shipped. Be sure to diff your files with the changed files from the new installation. 

~saffron/smb/conf

~saffron/smb/catalina/conf     

Note: In this release, the following files have been modified from ~saffron/smb/conf:

admin-config.properties 

saffron.xml

advantage-config.properties (for users of SaffronAdvantage)

NOTE: Verify that the validFileRoots property is properly set to your File Source location (from where you ingest data). Failure to do so will result in all affected Spaces to go offline. See the SMB 10.8.0 Release Notes for information on setting this property.

10. Restart the mysql daemons on all nodes only if your mySQL server-specific configuration has changed; otherwise, it is not necessary.

As the saffron user, enter the following command:  

creset -r 

11. Restart the SMB cluster and Ganglia.  As the saffron user, enter the following commands:

cluster start

12. Restart Ganglia only if Gangila-specific configurations have been changed by the system administrator. For a general SMB update, this is not required.

ganglia restart 

13. Verify that you have version 10.8.0. Enter the following command:

cluster version

14. Verify operation of the new cluster.  Enter the following command:

cluster status

15. Verify in the latest log files in ~/smb/logs that no errors exist.

16. Log in to Saffron Admin and Saffron Advantage websites to verify proper operation. 

17. (Optional) If your site has site-specific jdbc jars (e.g., SQL Server jtds or Teradata drivers) or jars that extend SMB functionality, do the following as the saffron user:

cluster stop
cp -p dir_containing_jars/*.jar ~/smb/lib
rd    (The "rd" command syncs the worker node smb/lib directory with the head node.)  
cluster start

Repeat steps 14, 15, and 16.


Viewing all articles
Browse latest Browse all 3384

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>