Manually upgrading pmswift

To upgrade pmswift you can either uninstall and reinstall the pmswift rpm or use the native rpm upgrade command: rpm -Uvh pmswift-version-release.noarch.rpm. After upgrading, restart the service using the following command: systemctl restart pmswiftd.service.

Uninstall pmswift-version-release.noarch.rpm

Stop the pmsensors.service using the following command:
```
systemctl stop pmsensors.service
```
If uninstalling pmswift-4.1.1-4 or later, stop the pmswiftd.service using the following command:
```
systemctl stop  pmswiftd.service
```
If uninstalling pmswift-4.1.1-3, stop the pmprovidor.service using the following command:
```
systemctl stop pmprovider.service
```
Uninstall the pmswift rpm using the following command:
```
rpm -evh --nodeps pmswift
```
If you are uninstalling pmswift-4.1.1-3, it should edit the Object configuration files for all Object servers and remove the entries created at the time of installation. The Object configuration files in /etc/swift/ directory are:
- account - *.conf
- container - *.conf
- object - *.conf
- proxy - *.conf
This should also edit the sensors configuration file, /opt/IBM/zimon/ZIMonSensors.cfg, to remove the Object related sensors entries created at the time of installation. If you are uninstalling pmswift-4.1.1-4 or later these files will be left alone.
Ensure that following directories/files are removed. If they are not removed, you can, remove them manually.
1. /usr/local/swiftmon directory or /usr/local/pmswift directory
2. /var/log/swiftmon directory or /var/log/pmswift directory
3. /var/run/swiftmon directory or /var/runpmswift.pid file
4. For pmswift-4.1.1-4 and later remove /etc/rc.d/init.d/pmswift file and for pmswift-4.1.1-3 remove /etc/rc.d/init.d/pmprovider file
5. For pmswift-4.1.1-3 SwiftAccount.cfg, SwiftContainer.cfg, SwiftObject.cfg and SwiftProxy.cfg files from within the Performance Monitoring tool’s installation directory, /opt/IBM/zimon/.
Ensure that for pmswift-4.1.1-3 the pmprovider.service and for pmswift-4.1.1-4 and later the pmswftd.service is not available anymore by running the following command:
```
systemctl daemon-reload
```

Install pmswift-version-release.noarch.rpm

Install the pmswift rpm using the following command:
```
rpm -ivh pmswift-version-release.noarch.rpm
```
Ensure that following directories/files have been created:
1. /usr/local/pmswift directory
2. /var/log/pmswift directory
3. /etc/logrotate.d/pmswift file
4. /etc/rc.d/init.d/pmswiftd file
5. SwiftAccount.cfg, SwiftContainer.cfg, SwiftObject.cfg and SwiftProxy.cfg files in the Performance Monitoring tool’s installation directory, /opt/IBM/zimon/.
Edit the Object configuration files for all Object servers that reside in CCR, using the /usr/local/pmswift/bin/pmswift-config-swift set command. CCR will then propagate modified configuration files to /etc/swift/ directory on all the protocol nodes within the cluster. The modified configuration files are:
- account - *.conf
- container - *.conf
- object - *.conf
- proxy - *.conf

Edit the sensors configuration file information stored in the CCR using the /usr/local/pmswift/bin/pmswift-config-zimon set command to add the following Object related sensors entries:

			{
					# SwiftAccount operational metrics
					name = "SwiftAccount"
					period = 1
					type = "generic"
					restrict= "cesNodes"
			},
			{
					# SwiftContainer operational metrics
					name = "SwiftContainer"
					period = 1
					type = "generic"
					restrict= "cesNodes"
			},
			{
					# SwiftObject operational metrics
					name = "SwiftObject"
					period = 1
					type = "generic"
					restrict= "cesNodes"
			},
			{
					# SwiftProxy operational metrics
					name = "SwiftProxy"
					period = 1
					type = "generic"
					restrict= "cesNodes"
			},

These entries are then automatically propagated to the ZIMonSensors.cfg file in /opt/IBM/zimon on all the nodes in the cluster.

Start the pmswiftd.service using the following command:
```
systemctl start pmswiftd.service
```
Start the pmsensors.service using the following command:
```
systemctl start pmsensors.service
```