Fresh installation 6.6.0

Community Support
1

Hello,

I would like to upgrade my OpenNebula Cluster because, now, it’s running CentOS-7. My idea is running a fresh installation of OpenNebula 6.6.0 in a AlmaLinux-9.1

In this point, I have two questions:

  1. Because of new installation will be a “fresh installation”, is there any way to backup all data and, after installing 6.6.0, restore it? I think all data (configuration) is in database (in my scenario, a sqlite db) but, could anyone confirm that? In the database, are saved all users, quotes, templates, virtual networks and so on? Or… how could restore them if new installation comes with a new version of SQLite? In other words, after fresh installation of 6.6.0, would it be secure to restore a database from 6.4.0???

  2. My first test with 6.6.0 and AlmaLinux-9.1 has finished BEFORE I could install “opennebula” packages:

[root@servidor ~]# yum install opennebula opennebula-sunstone opennebula-fireedge opennebula-gate opennebula-flow opennebula-provision
Última comprobación de caducidad de metadatos hecha hace 0:09:05, el jue 19 ene 2023 14:57:35.
Error: 
 Problema 1: conflicting requests
  - nothing provides libmysqlclient.so.21()(64bit) needed by opennebula-6.6.0-1.el9.x86_64
  - nothing provides libmysqlclient.so.21(libmysqlclient_21.0)(64bit) needed by opennebula-6.6.0-1.el9.x86_64
 Problema 2: package opennebula-sunstone-6.6.0-1.el9.noarch requires opennebula-rubygems = 6.6.0, but none of the providers can be installed
  - conflicting requests
  - nothing provides libmysqlclient.so.21()(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
  - nothing provides libmysqlclient.so.21(libmysqlclient_21.0)(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
 Problema 3: package opennebula-provision-6.6.0-1.el9.noarch requires opennebula-rubygems = 6.6.0, but none of the providers can be installed
  - conflicting requests
  - nothing provides libmysqlclient.so.21()(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
  - nothing provides libmysqlclient.so.21(libmysqlclient_21.0)(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
 Problema 4: package opennebula-gate-6.6.0-1.el9.noarch requires opennebula-rubygems = 6.6.0, but none of the providers can be installed
  - conflicting requests
  - nothing provides libmysqlclient.so.21()(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
  - nothing provides libmysqlclient.so.21(libmysqlclient_21.0)(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
 Problema 5: package opennebula-flow-6.6.0-1.el9.noarch requires opennebula-rubygems = 6.6.0, but none of the providers can be installed
  - conflicting requests
  - nothing provides libmysqlclient.so.21()(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
  - nothing provides libmysqlclient.so.21(libmysqlclient_21.0)(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
(pruebe a añadir '--skip-broken' para descartar los paquetes que no se pueden instalar o '--nobest' para no tener en cuenta sólo los mejores candidatos)

Thanks.

2

To get past the mysql issue you need to install the following:

First download rpm
mysql80-community-release-el9-1.noarch.rpm

Install using the following commands:
sudo rpm -Uvh mysql80-community-release*rpm
dnf --enablerepo=mysql80-community install mysql80-community-release
sudo dnf --enablerepo=mysql80-community install mysql80-community-release
sudo dnf update

Opennebula should now install
sudo yum -y install opennebula opennebula-sunstone opennebula-fireedge opennebula-gate opennebula-flow opennebula-provision

3

Ad 1) It’s possible for EE version of OpenNebula or for non-profit organization, which can get the latest CE migrators
The procedure is:

  • At old installation:
    • stop OpenNebula
    • run onedb backup <file_name>
  • At new installation
    • start OpenNebula to create DB
    • stop OpenNebula
    • run onedb restore <file_name>
    • run onedb upgrade
    • start OpenNebula
1 Like
4

I forget to note that not everything is stored in DB. You need to manually transfer /var/lib/one/datastores. Few others steps may be needed, depending on your configuration. I recommend you to read the upgrade procedure

5

Hi,

I’m going to test this procedure to check if all users, templates, quotes and so on are restored in the new fresh installation.

Thanks!

6

But, in my case, I’m not doing a upgrade but a fresh installation, so if I format all filesystems, previously I need to backup my datastores (to save images) and, then, I supose I need to copy that to a folder (like /var/tmp) and, then, I will have to add each new image from Sunstone or from CLI. Am I OK or wrong?

My datastore “1 → IMAGE” contains 25 images with a total of 400 GB (because of my scenario, I have images too big :frowning: )

Thanks, @pczerny

7

As part of the bootstrap opennebula populates some auth files in ~oneadmin/.one/*… so at the new installation these files should be transferred manually too…