RedHat/CentOS(Stream) 8 Alpaca Upgrade
This is an upgrade guide for an existing Alpaca installation.
Assumptions
- An existing installation of Alpaca.
- Credentials to access the Alpaca server as root.
- Working knowledge of
ssh
and file transfer tool such asscp
.
Guide
The guide is split into sections based on the server or machine that the operations should be performed. It is also in chronological order. Performing the steps from top to bottom is the desired procedure.
Local Work Station
- Step: O-1
- Download the Alpaca Server installation RPM. This requires an ECG Portal Account.
- Transfer the downloaded installation package to the Alpaca Server's "/tmp" directory.
- Step: O-2 (Skip if not using a Highly Available Clustering setup (HA))
- Download the Alpaca Eureka installation RPM. This requires an ECG Portal Account.
- Transfer the downloaded installation package to the Alpaca Server's "/tmp" directory.
- Step: O-3 (Skip if not using a Highly Available Clustering setup (HA))
- Download the Alpaca Gateway installation RPM. This requires an ECG Portal Account.
- Transfer the downloaded installation package to the Alpaca Server's "/tmp" directory.
- Step: O-4
- Download the Alpaca Remote installation RPM. This requires an ECG Portal Account.
- Transfer the downloaded installation package to each BroadWorks Application Server's "/tmp" directory.
Alpaca Server
General Upgrade Process
These are the general steps for upgrading Alpaca Server. Please check caveats for specific instructions for the version that you are upgrading to.
- Step: A-1
- Commands:
- Turn off the existing Alpaca service.
- # service alpaca-server stop
- Perform RPM upgrade
- rpm -U alpaca-server-ALPACA_VERSION_1.x86_64.rpm
- Restart Alpaca service.
- # service alpaca-server start
- Turn off the existing Alpaca service.
Caveats
Upgrading to 9.1.0 from any previous version- The default Alpaca store location has been moved from
/tmp/alpacastore
to/var/alpaca/store
. If your Alpaca installation includes a configuration foralpaca.file-store.location
, this new default will not overwrite that. This change will only affect users who did not specify an Alpaca store location and are using the default. For those who used the default directory, you will need to manually move the contents of/tmp/alpacastore
to/var/alpaca/store
. - The following configurations have been removed:
alpaca.file-store.cleanup-interval
andalpaca.task.retention-period-days
. They have been replaced withalpaca.file-store.temp-file-retention-period-days
,alpaca.file-store.task-file-retention-period-months
andalpaca.file-store.report-file-retention-period-months
.
- RabbitMQ is a required part of the Alpaca system for version 9.0.0 and following. Please follow the installation guide to complete the RabbitMQ installation.
- There is additional configuration required for connection to Eureka, RabbitMQ, and the optional Amazon S3 bucket
support. Please follow the configuration guide and update
the
/etc/alpaca/server/config/application-prod.yml
file accordingly. - Note that upgrading to Alpaca 9.0.0 will remove any Recurring (scheduled) Tasks that are configured.
- Please note that in the
application-https.yml
that theECDHE_RSA_WITH_AES_256_CBC_SHA384
cipher has been renamedTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
. This means that if the https configuration is moved from the Server to the Gatway that the cipher needs to be renamed. - Note that if using a Highly Available Clustering setup (HA), the SSL configuration has been moved from the Alpaca Server configuration to the Alpaca Gateway configuration.
- In 8.1.0 the configuration that was previously
uc-one
is nowcisco-soft-client
. Property files that contain the olduc-one
tag will need to be updated.
If running Alpaca 7.2.0 or earlier, an incremental upgrade to Alpaca 7.2.1 is required before upgrading to 8.0.0 or higher. After the update to 7.2.1, shut off Alpaca, and then upgrade to Java11 before upgrading to Alpaca 8.0.0 or higher.
If using an existing
/plugins
directory for Alpaca. This directory will need to be backed up manually and the plugins re-added to the Alpaca plugins directory.
- Back up all configuration files in
/opt/alpaca/config/
. - After upgrade, configuration files will be located in
/etc/alpaca/<ALPACA_PACKAGE>/config/
.- The backed up configurations files will need to be copied here.
- After upgrade, log files will be located in
/var/log/alpaca/
.
- If running Alpaca 6.6.6 or earlier, an incremental upgrade to Alpaca 6.6.7 is required before upgrading to 7.0.0 or higher.
- Step: A-1
- Commands:
- # cd /tmp
- # rpm -U alpaca-server-21sp1-8.0.3-SNAPSHOT_1.x86_64.rpm
- Step: A-1
- Commands:
- Turn off the existing Alpaca service.
- # service alpaca stop
- Remove the Alpaca service script.
- # rm /etc/init.d/alpaca
- Remove the Alpaca symlink in the "/opt" directory if it exists.
- # rm /opt/alpaca
- Install the Alpaca Server RPM
- # yum install -y alpaca-server-ALPACA_VERSION.x86_64.rpm
- Turn off the existing Alpaca service.
Alpaca Eureka
General Upgrade Process
These are the general steps for upgrading Alpaca Eureka.
- Step: A-1
- Commands:
- Turn off the existing Alpaca Eureka service.
- # service alpaca-eureka stop
- Perform RPM upgrade
- rpm -U alpaca-eureka-ALPACA_VERSION_1.x86_64.rpm
- Restart Alpaca service.
- # service alpaca-eureka start
- Turn off the existing Alpaca Eureka service.
Alpaca Gateway
General Upgrade Process
These are the general steps for upgrading Alpaca Gateway.
- Step: A-1
- Commands:
- Turn off the existing Alpaca Gateway service.
- # service alpaca-gateway stop
- Perform RPM upgrade
- rpm -U alpaca-gateway-ALPACA_VERSION_1.x86_64.rpm
- Restart Alpaca service.
- # service alpaca-gateway start
- Turn off the existing Alpaca Gateway service.