Versions Compared

Version Old Version 144 New Version Current
Changes made by

MS

Aleksandra Nowotna (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Info

These instructions are still being updated for the Abiquo 6.2 upgrade

1. Introduction

This section describes how to upgrade from from Abiquo 46.41.x or above to the current Abiquo version. Please contact Abiquo Support for further information.

Table of Contents

 

...

start-numbering-ath3

...

Abiquo YUM repositories are no longer open, please contact Abiquo Support to obtain your credentials

This upgrade process starts from Abiquo 4.4 or above. To upgrade from earlier versions, please contact Abiquo Support

...

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

Prepare branding upgrade

...

  • 4.5
  • 4.6
  • 4.6.1
  • 4.7.0

...

Before the upgrade

Before you begin, remember to:

  • Stop services
    • Remember to stop the following services on the Monitoring server: abiquo-delorean, abiquo-emmett, kairosdb, cassandra
  • Check for queued jobs or conversions 
  • Perform a full backup

Known issue: Before the release of version 5.2.0, you must back up the `/etc/nginx/nginx.conf` of each Remote Services server where you have a configuration of the WebMKS feature enabled. The update will replace the content of the nginx.conf file with the default parameters. This issue has been documented in issue 13509.

...

Upgrade packages on ALL servers

...

Check that you have the repository URL and credentials

To upgrade to a version with a patch number of zero, for example, version 5.0.0, version 5.1.0

...

Remove the previous version Abiquo release packages.

...

Install the release package. For Abiquo 5.1.0, the command would be similar to the following

...

Disable the updates repo. See https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/sec-managing_yum_repositories

OR To upgrade to a version with patch number that is not zero, for example, version 5.1.1, version 5.1.2

...

  1. Disable the base repo

  2. Enable the updates repo

See https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/sec-managing_yum_repositories

Optionally add your username and password to the Abiquo repos

Don't forget to use a backslash to escape any shell special characters. For more details, see https://www.oreilly.com/library/view/learning-the-bash/1565923472/ch01s09.html

Update Abiquo packages:

The Abiquo services must run as the tomcat user (not root), so set the required permissions and enforce the use of the package configuration files.
If you have a MONOLITHIC SERVER do all of the following steps on the Monolithic server

On Abiquo Server and Remote Services

On the Remote Services with Appliance Manager and the V2V Server (i.e. servers that mount the NFS repository)

On the V2V server, check the /etc/sysconfig/abiquo/ec2-api-tools file exists.
The file must contain the following configuration. If the file does not exist, create it and add this configuration.

...

Update the Abiquo databases

...

To upgrade the Abiquo API databases, run the command below on the Server appliance:

If the liquibase update fails with a message similar to the following: 

Liquibase update Failed: Validation Failed:
1 change sets check sum
src/X.X.X-XX/kinton-X.X.X.xml::ABICLOUDPREMIUM-XXXX-XxxxxxxxXXxXxxxxxxXxxxxx::XXXXXXXXX is now: 7:ee2fa6e058ec76c7abf801567898917d
For more information, use the --logLevel flag

Do the following steps

Clear the database checksums

...

To upgrade the Abiquo Watchtower database, run the command below on the monitoring appliance:

 

...

Upgrade additional elements

Start with your original version and perform the steps to the final version.

By default, you will find the upgrade scripts (e.g. for Redis definitions) on the Abiquo Server under the folder: /usr/share/doc/abiquo-redis/redis/

For each upgrade step, run the Redis database script to remove old VSM definitions, which can be found in the 4.2.3 subfolder

On Remote Services server:

...

Run additional database scripts

...

This is a new version of the same tool that was run in the 4.2.x to 4.4 upgrade. If you are upgrading from 4.2.x or earlier, you do not need to run this tool twice.

When upgrading from 4.4.x to 4.5, run the following tool that will generate two scripts.

Run the scripts after the database upgrade on the Abiquo kinton database server and the Watchtower database server.

The instructions for running the tool are at the following location:

The tool is located at the following location:

Run tool to update VM naming on vCloud

Please contact Abiquo support.

Run Redis database script

On Remote Services server:

...

Nodecollector and cloud provider proxy changes

  • Discovery manage functions are now performed by the NARS remote service, which replaces the Nodecollector and Cloud Provider Proxy remote services.
  • As part of the upgrade process, administrators can remove the old remote service webapps: nodecollector and cpp.

Run Redis database script

On Remote Services server:

...

Storage changes

  • If you have a custom external storage plugin, contact Abiquo Support to obtain the upgrade procedure: Upgrade a storage plugin to Abiquo 4.7
  • External storage in private cloud and public cloud is now managed using the NARS remote service, which replaces the Storage Manager. As part of the upgrade you can remove the ssm webapp

Run Redis database script

On Remote Services server:

Reporting changes

  • To upgrade the Abiquo Reports database for the upgrade to Abiquo 4.7.x+, contact Abiquo Support for the file and procedure.

Post-upgrade step:

  • For VMs captured in a powered on state with Abiquo 4.6.3+ and vCenter 6.5+, the administrator can manually remove the VNC configuration from the VM definition file on the hypervisor to allow remote access without reconfiguring the VM. When WebMKS is enabled, users will then be able to connect to these VMs using the web console

...

Run Redis database script

On every Remote Services server:

Post-upgrade steps:

  • Change the tutorials' softlinks in the frontend servers: if there is a softlink /var/www/html/ui/config/tutorials pointing to /opt/abiquo/config/tutorials, please change it to point to /opt/abiquo/tutorials instead.
  • If your Apache redirect addresses end in trailing slash characters ("/"), remove the trailing slashes

...

Run script to update job names on Veeam server

When upgrading from 5.0.x or 5.1.x to 5.1.2 or above, if you are using Veeam, run the following application that will update the job names on the Veeam server to allow duplicate VM names.

The instructions for running the tool are in the following file.

To run the tool, do these steps:

Edit the veeam.properties file and set the MySQL jdbc properties. Replace the examples with the values for the Abiquo database

Obtain the Veeam version and credentials to pass as arguments to the script

...

  • veeam95u4 Run for usage with Veeam server 9.5u4 or veeam10 Run for usage with Veeam server 10

  • -ip IP address of Veeam server

  • -u, --user veeamServerUser

  • -p, --password veeamServerPassword

The other argument defines a dry-run mode to test the script

...

  • -no-dry, --no-dry-run If true, update Veeam job names. If false, only show what will the names will look like after the change

Run the tool in dry-run mode (with the argument "--no-dry-run false" and check the Veeam jobs that it will update.

Run the tool in production mode to update the Veeam server

...

Run mandatory database scripts on Redis database and Watchtower SQL database

When upgrading from 5.0.x or 5.1.x to 5.1.2 or above, run the following tool that will generate two scripts to run on the Redis database and Watchtower SQL database. You can run the tool on any server that has an appropriate version of Java and as the script file is on the Abiquo Server, this may be the most convenient place to run it.

These scripts change the use of the Abiquo VM Identifier (name attribute) as the UID to the ID of the VM as the new UID.

The instructions for running the tool are in the following file:

To run the tool and scripts, do these steps:

On the Abiquo Server, run the tool to generate the scripts, supplying the database credentials for the APi

You should find the following scripts in the output directory (by default the current directory)

  • redisdelta, which is Bash script

  • watchtowerdelta.sql

...

For each Remote Services server, copy the redisdelta Bash script to the server.

On every Remote Services server, run the Bash script. Note that this script requires Bash version 4, which is the default version on the Abiquo Servers

...

Copy the SQL script to the Watchtower Monitoring server.

Run the SQL script

Run Redis database script

On every Remote Services server:

...

When upgrading from 5.1.0 or 5.1.1 to 5.1.2 or above, follow the steps from the Upgrade steps from 5.0.x to 5.1.x block.

Configure Abiquo after the upgrade

...

Start Abiquo server and services

Bring up the server and restart the HTTP daemon to refresh the user interface files.

...

First start the cassandra service

...

Start the KairosDB service

...

Wait about 1 minute until the service is up and running

...

an Abiquo 6.2.x version. 

For your convenience, we have also prepared the following concise upgrade document that groups the commands by servers.
However, we encourage you to use the current Upgrade Abiquo document as your main reference:

Please contact Abiquo Support for further information.

Major version upgrade table

From version

To version

Upgrade type

Notes

6.1.x

6.2.x

Major

Follow the process in this document (or at Upgrade Abiquo 6.1.x to 6.2.x distributed by servers

  • Upgrade Abiquo packages

  • Run the guestpasswordmigrator

  • Upgrade mariadb on the main DB and watchtower DB

  • Apply the guestpasswords.sql file to the main DB

  • For Galera clusters, update the cluster details for the database connection

  • To display cost-usage reports, run regenerate billing

Minor version upgrade table

From version

To version

Upgrade type

Notes

6.1.0

6.1.1

Standard

See Standard Abiquo minor or patch version update

6.1.1

6.1.2

Standard + Guacamole

See Standard Abiquo minor or patch version update
and Upgrade Guacamole server

6.1.2

6.1.3

Standard

See Standard Abiquo minor or patch version update

6.1.3

6.1.4

Standard

See Standard Abiquo minor or patch version update


2. Warnings and notices

  • Before you begin, contact Abiquo Platform and Customer Success department to obtain your credentials for Abiquo YUM repositories.

Warning

Major upgrade

The upgrade to Abiquo 6.2.0 is a major upgrade with upgrades of third-party software packages that are critical platform dependencies

You must make snapshots of ALL servers before you start the upgrade

  • The upgrade will overwrite lang_en_US_labels.json. Back up your customized labels or translations before the upgrade, and restore them afterwards.

Note

SAML upgrade

  • The upgrade will overwrite the SAML login configuration for multiple IdPs. Back up the configuration files before the upgrade, and add the multiple IdPs again afterwards. See Restore SAML security beans after upgrade.

  • For Abiquo 6.0.0+, you must configure the SAML maximum authentication age property or SAML will not initialize

3. 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

...

4. Check for operations in progress on the platform

Before you shut down the platform servers, check that no operations are in progress.

  1. Check that the Abiquo RabbitMQ queues are empty on the Abiquo Monolithic Server, Abiquo Server or Datanode server

    The number of messages in all queues must be 0.

    Code Block
    # rabbitmqctl list_queues messages name

    Code Block
    # rabbitmqctl list_queues messages name
Listing queues ...
0	abiquo.am.notifications
0	abiquo.bpm.notifications
0	abiquo.datacenter.requests.ADatacenter.bpm
0	abiquo.datacenter.requests.ADatacenter.virtualfactory
0	abiquo.ha.tasks
0	abiquo.nodecollector.notifications
0	abiquo.pcrsync.messages
0	abiquo.pcrsync.parking-expect-no-consumers
0	abiquo.scheduler.fast.requests
0	abiquo.scheduler.requests
0	abiquo.scheduler.slow.requests
0	abiquo.tracer.traces
0	abiquo.virtualfactory.notifications
0	abiquo.virtualmachines.definitionsyncs
0	abiquo.vsm.eventsynk
...done.

  2. On the V2V Server, check for any active conversions by checking for the V2V or Mechadora processes

    Code Block
    $ ps aux | grep v2v
$ ps aux | grep mechadora

When user VM operations are blocked and all of the above checks show that no tasks are running, it is safe to halt the platform.

...

5. Stop platform services

This section describes how to stop platform services on all servers.

Note

If there are operations in progress, DO NOT STOP the platform services because this can cause serious issues with your platform.
See Check for operations in progress on the platform and wait for all operations to complete

To stop platform services:

  1. Stop the API on the API server or monolithic server

    Code Block
    systemctl stop abiquo-tomcat

  2. Stop the UI on the API server or monolithic server or dedicated UI server

    Code Block
    systemctl stop httpd

  3. Stop RabbitMQ on the API server or dedicated datanode server

    Code Block
    systemctl stop rabbitmq-server

  4. Stop remote services server

    Code Block
    systemctl stop abiquo-tomcat

  5. V2V Server
    You do not need to stop anything because the BPM remote service is run on-demand only

  6. Stop monitoring server

    Code Block
    systemctl stop abiquo-delorean
systemctl stop abiquo-emmett
systemctl stop kairosdb
systemctl stop cassandra

  7. On the monitoring server, check if Cassandra is really dead

    Code Block
    ps auwx | grep cassandra

    Get the process number for Cassandra (the first number in the output of the previous command), and kill it. In this example, Cassandra is process 12345.

    Code Block
    kill -9 12345

All processes on platform servers should now be halted.

...

6. Back up the main platform elements

To perform a basic backup of the platform, run the following backups:

Note

Before you begin, stop platform services, and check you have enough space on your destination systems.

Code Block
languagebash
# On the Abiquo API Server or UI server, back up the UI
tar cvfz /var/www/html/ui.tgz-$(date +%Y%m%d_%H%M%S) /var/www/html/ui

# Copy the api.xml file to back up the database connection details
cp /opt/abiquo/tomcat/conf/Catalina/localhost/api.xml /opt/abiquo/api.xml-$(date +%Y%m%d_%H%M%S)

# On ALL servers, back up the /opt/abiquo folder
tar cvfz /opt/abiquo.tgz-$(date +%Y%m%d_%H%M%S) /opt/abiquo

# On Abiquo Monolithic or API Server, Remote Services, or Datanode, back up Redis
redis-cli save
cp -a /var/lib/redis /var/lib/redis-$(date +%Y%m%d_%H%M%S)

# On DB server, back up the Abiquo MySQL DBs
mysqldump --routines --triggers kinton            > kinton.sql-$(date +%Y%m%d_%H%M%S)
mysqldump --routines --triggers kinton_accounting > kinton_accounting.sql-$(date +%Y%m%d_%H%M%S)

# On the Monitoring server, back up Watchtower DB
mysqldump --routines --triggers watchtower            > watchtower.sql-$(date +%Y%m%d_%H%M%S)

# If you are using SAML authentication with multiple IdPs, on ALL Abiquo API Servers, back up this file
cp /opt/abiquo/tomcat/webapps/api/WEB-INF/classes/springresources/security/saml/security-saml-generated-beans.xml /opt/abiquo/tomcat/webapps/api/WEB-INF/classes/springresources/security/saml/security-saml-generated-beans.xml-$(date
 +%Y%m%d_%H%M%S)

...

7. Make snapshots and backups of all platform servers

This is a major upgrade, so we recommend that you make a snapshot and/or a full backup of your platform servers.

...

8. Remove Docker and unmount shared folders

  1. On your RS server(s) uninstall Docker

    Code Block
    rpm -e --nodeps docker
rpm -e --nodeps docker-client
rpm -e --nodeps docker-common

  2. If you have multiple instances of the NARS Remote Service in your datacenter, check on your RS servers for an NFS shared folder for the NARS results (with the Abiquo configuration property abiquo.nars.async.fileresults.path):

    Code Block
    languagebash
    $ mount | grep -i "nfs\|results" | grep -v sunrpc
10.60.37.87:/abq-pro-nfs on /opt/abiquo/results-nars type nfs4 (rw,nosuid,nodev,noexec,relatime,sync,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.60.37.77,local_lock=none,addr=10.60.37.87,user)

  3. Unmount the shared folder. You will remount it after the upgrade

    Code Block
    languagebash
    sudo umount /opt/abiquo/results-nars

...

9. Prepare yum repositories for 6.2 or 6.2.x

Check that you have the repository URL and credentials

On all Abiquo Servers, such as Abiquo API, Remote Services, Watchtower monitoring.

Install release package

  1. To upgrade to a version with a patch number of zero, for example, version 6.2.0

    1. Remove the previous version Abiquo release packages.

      Code Block
      yum remove 'abiquo-release-*'

    2. Find the abiquo-release-ee package for your version in the list of available versions

    3. Install the release package.
      For Abiquo 6.2.0, the command would be similar to the following:

      Code Block
      yum localinstall http://usr:passwd@mirror.abiquo.com/el7/6.2/os/x86_64/abiquo-release-ee-6.2.0-AAAAAAAA_BBBBBBB.el7.noarch.rpm

      For Abiquo 6.2.1, the release package would be in the format:

      Code Block
      http://usr:passwd@mirror.abiquo.com/el7/6.2/updates/x86_64/abiquo-release-ee-6.2.1-BBBBBBBBBBBB.el7.noarch.rpm

    4. For major versions, disable the updates repo.

      Code Block
      yum-config-manager --disable abiquo-updates

Prepare yum repositories for 6.2.x (minor version)

  1. Check that you have the repository URL and credentials

  2. To upgrade to the latest version with a patch number that is not zero, for example, version 6.2.x, enable both repositories:

    Code Block
    yum-config-manager --enable abiquo-base
yum-config-manager --enable abiquo-updates

  3. Optionally, add your username and password to the Abiquo repos

    Code Block
    yum-config-manager --save --setopt=abiquo-*.username=MYUSERNAME
yum-config-manager --save --setopt=abiquo-*.password=MYPASSWORD

    Don't forget to use a backslash to escape any shell special characters. For more details, see https://www.oreilly.com/library/view/learning-the-bash/1565923472/ch01s09.html

  4. Clean yum and make cache

    Code Block
    yum clean all && yum makecache

  5. If you did not make snapshots of all servers already, then you could do this now.

...

10. Upgrade packages on ALL servers

These instructions are for monolithic, distributed, and HA environments.

  1. Update all packages.

    Code Block
    yum clean all && yum makecache && yum update

    (warning) The MariaDB update requires a manual install. But first download and run the gpmigrator tool

  2. If you earlier unmounted shared folders from your Remote Services server, mount this folder again (and any other folders!)

    Code Block
    languagebash
    sudo mount -a

  3. The Abiquo services must run as the tomcat user (not root), so set the required permissions and enforce the use of the package configuration files.
    If you have a MONOLITHIC SERVER do all of the following steps on the Monolithic server

    1. On Abiquo server and remote services

      Code Block
      chown -R tomcat /opt/abiquo

    2. On the remote services with appliance manager and the V2V server (i.e. servers that mount the NFS repository)

      Code Block
      chown -R tomcat /opt/vm_repository
chmod -R a+r /opt/vm_repository

    3. On the V2V server, check the /etc/sysconfig/abiquo/ec2-api-tools file exists.
      The file must contain the following configuration. If the file does not exist, create it and add this configuration.

      For CentOS 7

      Code Block
      EC2_HOME=/opt/aws

...

11. Run the guest password migrator

  1. Download and install the gpmigrator package

    Code Block
    yum localinstall http://user:passwd@mirror.abiquo.com/el7/6.2/os/x86_64/abiquo-gpmigrator-6.2.0-20240205_155724.el7.noarch.rpm

  2. Run the tool to migrate the guest passwords of the current VMs to a new column that will be added in 6.2.0.

    1. The tool requires access to the kinton database and to the API Redis

    2. Usage:

      Code Block
      --jdbc-url VAL    : Replace VAL with Kinton JDBC URL including user and password
--output-file VAL : Replace VAL with the output file (by default: 'guestpasswords.sql') 
--redis-host VAL  : Redis host to connect
--redis-port N    : Redis port to connect (by default: 6379)

      For example:

      Code Block
      java -jar gpmigrator.jar --jdbc-url="jdbc:mariadb://localhost:3306/kinton?user=root&password=root" --redis-host=localhost

  3. Save the guestpasswords.sql file (or whatever you called it) to run after you update the Abiquo database

...

12. Upgrade MariaDB for Abiquo 6.2.0

  1. On all database servers, including the Watchtower server, upgrade MariaDB

    Code Block
    rpm --nodeps -ev MariaDB-server-10.4.10-1.el7.centos.x86_64
yum install MariaDB-server
service mariadb start
# OR for datanode: galera_new_cluster 
mysql_upgrade

...

13. Update the Abiquo databases

  1. Check that your hostname is in your DNS or in your /etc/hosts file

  2. Upgrade the Abiquo API databases

    Code Block
    abiquo-db [-h DB hostname] [-P DB port] [-u user] [-p password] update

  3. If the database update fails with a message similar to the following: 

    Code Block
    Liquibase update Failed: Validation Failed:
1 change sets check sum
src/X.X.X-XX/kinton-X.X.X.xml::ABICLOUDPREMIUM-XXXX-XxxxxxxxXXxXxxxxxxXxxxxx::XXXXXXXXX is now: 7:ee2fa6e058ec76c7abf801567898917d
For more information, use the --logLevel flag

    Clear the checksums and run the update again

    Code Block
    abiquo-db clearCheckSums
abiquo-db [-h DB hostname] [-P DB port] [-u user] [-p password] update

  4. (warning)For Abiquo 6.2.0, run the gpmigrator SQL file output (with the appropriate user and credentials)

    Code Block
    mysql kinton < guestpasswords.sql

  5. To upgrade the Abiquo Watchtower database, for the monitoring appliance, run the command below:

    Code Block
    watchtower-db [-h DB hostname] [-P DB port] [-u user] [-p password] update

...


14. Upgrade additional elements

For Abiquo 6.2.0+, update the database connector configurations

  1. On the Abiquo API Server, edit /opt/abiquo/tomcat/conf/Catalina/localhost/api.xml

  2. The latest version of the file should contain new options as shown below.
    Update the file and/or variables marked with ${} for your environment.

    Code Block
    <Context>
    <Resource 
        name="jdbc/abiquoDB" 
        auth="Container" 
        type="javax.sql.DataSource" 
        factory="com.zaxxer.hikari.HikariJNDIFactory"
        dataSourceClassName="org.mariadb.jdbc.MariaDbDataSource"
        connectionTimeout="120000"
        maximumPoolSize="100"
        username="${server.database.username}"
        password="${server.database.password}"
        dataSource.url="jdbc:mariadb://${server.database.host}:${server.database.port}/kinton"
        />
</Context>

  3. If you have a DB cluster, change the datasource.url to point to your Galera cluster.
    This will not affect the multi-master configuration of the cluster

    Code Block
    jdbc:mariadb:loadbalance://address=(host=${DBMAIN})(port=3306)(type=master),
        address=(host=${DBR1})(port=3306)(type=slave),
        address=(host=${DBR2})(port=3306)(type=slave)/kinton

  4. On the Watchtower server, edit the emmett.conf and delorean.conf files at:

    Code Block
    /etc/abiquo/watchtower/delorean.conf
/etc/abiquo/watchtower/emmett.conf

    1. From the connection details, remove jdbc:mysql: and replace with jdbc:mariadb:

    2. Add your Galera configuration if your monitoring DB is in a cluster

...

15. Configure Abiquo after the upgrade

  1. Before you start the Abiquo tomcat server, add Abiquo configuration properties to the abiquo.properties file.
    By default the abiquo.properties file is found in the /opt/abiquo/config/ folder.
    See Changes to Abiquo configuration properties

  2. Configure the user interface. The default UI location is /var/www/html/ui.
    Optional: Add custom labels and translations in the lang_xx_XX_custom.json files in the lang folder
    Add custom configuration to client-config-custom.json. See Configure Abiquo UI and Changes to UI configuration
    If your API is not in the same domain as the UI, set the API endpoint pointing to your Abiquo API server:

    Code Block
    {
    "config.endpoint": "http://myAPIserver/api"
}

  3. SAML: If you are using SAML with multiple IDPs, restore the configuration as described at Restore SAML security beans after upgrade.

  4. Abiquo 6.2.0 updates Java and other packages, so restore your certificates. To do this, you can follow the steps at Update certificates in your Abiquo environment.

...

16. Start Abiquo server and services


To start the Abiquo platform servers and services, do these steps:

  • On Abiquo server or datanode, restart RabbitMQ

    Code Block
    systemctl start rabbitmq-server

  • On the Abiquo server, restart the HTTP daemon to refresh the user interface files, and bring up the Tomcat server.

    Code Block
    service httpd start
service abiquo-tomcat start

  • On the Remote services server, start the Tomcat server

    Code Block
    service abiquo-tomcat start

  • On the Monitoring server: start the Cassandra service

    Code Block
    sudo service cassandra start

  • WAIT about 5 minutes until the service is up and running

  • Start the KairosDB service

    Code Block
    sudo service kairosdb start

  • Start the other services in this order

    Code Block
    sudo service abiquo-emmett start
sudo service abiquo-delorean start

  • On the V2V server: restart the Tomcat server:

    Code Block
    service abiquo-tomcat restart

Finally, in Abiquo, UI

  1. Re-enable the physical machines! (smile)

  2. In Abiquo 6.2.0, to activate the cost usage reports, regenerate billing

After the upgrade, to prevent glitches in the UI, clear your browser cache