Versions Compared

Old Version 33

changes.mady.by.user MS

Saved on

compared with

New Version 34

changes.mady.by.user MS

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Upgrade steps to remove old VSM definitions for RedisRun Redis database script

(tick) These scripts can always be found on the Abiquo Server.

On each Remote Services server (including Monolithic sever) or Datanode server run the Redis scripts.

Expand
titleClick for Upgrade steps from 5.1.x to 5.2.x for Redis

Include Page
Upgrade steps to remove old VSM definitions for Redis
Code Block
# cd /usr/share/doc/abiquo-redis/redis/
# bash ./4.2.3/00-old-vsm-definitions.sh


Expand
titleClick for Upgrade steps from 5.1.x to 5.2.x for billing dashboards
Include Page
Upgrade steps from 5.1.x to 5.2.x for billing dashboardsUpgrade steps from 5.1.x to 5.2.x for billing dashboards

Upgrade steps for 5.2 versions

...

Remove deprecated billing dashboard scripts

In Abiquo 5.2, the billing dashboard feature has been integrated into the Abiquo platform.
The upgrade process will migrate most of the enterprise properties for billing scripts, which will make the old billing dashboard scripts invalid.

If you were using the billing dashboard in a previous version, do these steps.

  1. To prevent errors, before the upgrade, you should have disabled the old billing dashboard scripts by removing the old cron jobs. If not, disable them now. see Upgrade billing dashboards

  2. In Abiquo, upgrade enterprise properties to ensure valid billing data is displayed. See Upgrade billing dashboards

  3. After you complete the upgrade, remove scripts and data. See /wiki/spaces/doc/pages/311371999


Upgrade steps for 5.2 versions

These steps apply to upgrades starting from version 5.2.0 and above.

Upgrade steps for 5.2 versions

  • Run Redis database script
    (tick) These scripts can always be found on the Abiquo Server.
    On each Remote Services server (including Monolithic sever) or Datanode server run the Redis scripts

Expand
titleClick here to show/hide the steps to upgrade 5.2 versions

Upgrade steps for 5.2 versions

Include Page
Upgrade steps for 5.2 versions
Code Block
# cd /usr/share/doc/abiquo-redis/redis/
# bash ./4.2.3/00-old-vsm-definitions.sh

...

Configure Abiquo after the upgrade

...

Start Abiquo servers and services

Start To start the Abiquo platform servers and services

...

, do these steps:

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

  2. On the Remote services server, start the Tomcat server

    Code Block
    service abiquo-tomcat start

  3. On the Monitoring server do these steps.

    1. Edit the file /opt/kairosdb/conf/kairosdb.properties to update the name of the following variable and to remove the port from it:

      1. Replace the line kairosdb.datastore.cassandra.host_list=192.168.888.999:9160.

      2. With this line kairosdb.datastore.cassandra.cql_host_list=192.168.888.999. Please note the new cql_ prefix for host_list.

    2. Edit the file /etc/cassandra/conf/cassandra.yml OR /etc/cassandra/default.conf/cassandra.yaml (whichever exists) to remove a variable:

      1. Remove the line starting with kairosdb.datastore.cassandra.datapoint_ttl and save and close the file.

    3. Edit the file /opt/kairosdb/conf/kairosdb.properties to add a new variable (ref: Internal JIRA SUP-333):

      1. Add kairosdb.datastore.cassandra.datapoint_ttl = 15768000

  4. On the Monitoring server, start the Cassandra service

    Code Block
    sudo service cassandra start

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

  6. Start the KairosDB service

    Code Block
    sudo service kairosdb start

  7. Start the other services in this order

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

  8. On the V2V server: restart the Tomcat server:

    Code Block
    service abiquo-tomcat restart

  9. In Abiquo, re-enable the physical machines! (smile)

  10. Clear your browser cache to prevent glitches in the UI