Versions Compared

Old Version 21

changes.mady.by.user MS

Saved on

compared with

New Version 22

changes.mady.by.user MS

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updating numbered headings

...

Warning

  • The upgrade will overwrite lang_en_US_labels.json. If you have customized labels or translations, back them up before the upgrade and restore them afterwards accordingly.

  • The upgrade will overwrite the SAML login configuration for multiple IdPs. If you use SAML with multiple IdPs, back up the configuration files before the upgrade and add the multiple IdPs afterwards accordingly. See Restore SAML security beans after upgrade


1.1. Prevent cloud users from performing VM operations

  1. In the UI in the Infrastructure view, select each physical machine and click Disable

  2. Using the API, set the state of each physical machine to DISABLED

...


1.2. API servers

On each API Server do these steps. If you have a separate DB server, do the DB upgrade steps on that server.

...

  1. Add translations for new UI labels to lang_xx_XX_custom.json. See Abiquo UI client language configuration

  2. Optionally add new configuration to client-config-custom.json. See Configure Abiquo UI

  3. In your UI configuration, check that the API endpoint is pointing to your Abiquo API server:

    Code Block
    {
    "config.endpoint": "http://<API_IP_ADDRESS>/api"
}


  4. Add new API properties to the abiquo.properties file found in the /opt/abiquo/config/ folder. See Changes to Abiquo Configuration properties


1.3. Remote services servers

On each remote services server do these steps.

...

  1. Add new RS properties to the abiquo.properties file found in the /opt/abiquo/config/ folder. See Changes to Abiquo Configuration Properties


...


1.4. Monitoring servers

On each Watchtower monitoring server do these steps.

Code Block
# Log in as root and stop services
sudo su -
systemctl stop abiquo-emmett
systemctl stop abiquo-delorean
systemctl stop kairosdb
systemctl stop cassandra
 

# Really kill Cassandra by getting its process number (e.g. XXXXX) and killing it
ps auwx | grep cassandra
kill -9 XXXXX


# Install latest yum release package for your target version using link
yum remove 'abiquo-release-*'
# Find the correct link at https://https://abiquo.atlassian.net/wiki/spaces/doc/pages/311363475/Abiquo-release-ee+packages+list
# For 6.1
yum localinstall https://user:passwd@mirror.abiquo.com/el7/6.1/os/x86_64/abiquo-release-ee-6.1.0-20230112_211400.el7.noarch.rpm

# Prepare yum repository for your target version 
yum-config-manager --enable abiquo-base
yum-config-manager --enable abiquo-updates

 
# Perform update
yum clean all && yum makecache
yum update 'abiquo-*'

 
# Update watchtower database
watchtower-db [-h DB hostname] [-P DB port] [-u user] [-p password] update


...


1.5. Start Abiquo server and services

Start all servers in the correct order.

Code Block
# On API Server
service httpd restart
service abiquo-tomcat start
 

# On Remote Services including V2V
service abiquo-tomcat start
 

# On the Monitoring Server, start the Cassandra service
sudo service cassandra start
 

# WAIT about 5 minutes until Cassandra is up and running
# Start the KairosDB service
sudo service kairosdb start
 

# Start the other services in this order
sudo service abiquo-emmett start
sudo service abiquo-delorean start

# In the Abiquo UI, reenable the physical machines


1.6. Reporting server

We recommend that you update your reports server to JasperReports v7.8.0.

...