Project

General

Profile

Tâche #27150

Scénario #23922: Fournir un processus d'UpgradeAuto d'un Hapy 2.4.2 vers Hapy 2.6.2

Faire la procédure de mise à jour sur un Hapy EOLE

Added by Daniel Dehennin 7 months ago. Updated 6 months ago.

Status:
Fermé
Priority:
Normal
Assigned To:
Start date:
03/07/2019
Due date:
% Done:

100%

Remaining (hours):
0.0

Associated revisions

Revision 34afc56c (diff)
Added by Daniel Dehennin 6 months ago

Upgrade: switch Hâpy to Eolebase to upgrade to 2.6.2

  • upgrade/Upgrade-Auto (main): execute “pre_download” before
    configuring Ubuntu upgrade tool.
  • upgrade/pre_download/01-hapy: transform the Hâpy to an Eolebase
    before the upgrade.

Revision 9630c816 (diff)
Added by Daniel Dehennin 6 months ago

Upgrade Hâpy: remove more packages to switch to Eolebase

Ref: #27150

Revision 408663da (diff)
Added by Daniel Dehennin 6 months ago

Upgrade Hâpy: VMs data should not have references to cluster name

We will move the resources to the new default cluster in 2.6.2, the
VMs should not have references to the current 2.4.2 cluster.

So we “undeploy” the VMs instead of a simple “poweroff”

Ref: #27150

Revision b4e41e53 (diff)
Added by Daniel Dehennin 6 months ago

Upgrade Hâpy: rename the system datastore to match 2.6.2 naming

In 2.6.2 we named the system datastore with “default” suffix since we
support cluster rename. In 2.4.2 the system datastore was named
regarded to the cluster name.

  • upgrade/pre_download/01-hapy: rename the system datastore before
    switching to Eolebase.

Ref: #27150

Revision 7c794ca1 (diff)
Added by Daniel Dehennin 6 months ago

Upgrade Hâpy: switch from Eolebase during the upgrade

The upgrade from 2.4.2 can be detected with the configuration placed
under “/var/backups/eole/hapy/”.

  • tmpl/eole.cfg: install eole-hapy-all and eole-hapy-module
    meta-packages when detecting Hâpy upgrade from 2.4.2.

Ref: #27150

Revision e7b2a436 (diff)
Added by Daniel Dehennin 6 months ago

Upgrade Hâpy: restore 2.4.2 configuration after switching to 2.6.2

This way the configuration upgarde is properly handled with all the
2.4.2 Hâpy configuration.

Ref: #27150

Revision f2ba0f64 (diff)
Added by Daniel Dehennin 6 months ago

Upgrade Hâpy: rename the current cluster

This way we can have the new 2.6.2 default cluster named as we want
without conflict.

Ref: #27150

Revision 5668a153 (diff)
Added by Daniel Dehennin 6 months ago

Postservice: always declare “AUTH” variable when used

And normalise the casing of the variable.

Ref: #27150

Revision 90798983 (diff)
Added by Daniel Dehennin 6 months ago

Postservice: always declare “AUTH” variable when used

And normalise the casing of the variable.

Ref: #27150

Revision 2dc8e027 (diff)
Added by Daniel Dehennin 6 months ago

Upgrade Hâpy: move 2.4.2 resources to default cluster

  • postservice/30-one-mng (upgrade_from_242): move hosts, datastores
    and vnets to the default cluster and remove the old cluster.

Ref: #27150

Revision 01e72cdb (diff)
Added by Daniel Dehennin 6 months ago

Upgrade Hâpy: override buggy OpenNebula DB upgrade script

  • override/4.11.80_to_4.13.80.rb: fixed script.
  • posttemplate/90-one-db: override OpenNebula files.
  • debsums-ignore.d/eole-hapy.conf: ignore the EOLE modified version of
    the DB upgrade script.
  • eole-one-master.mk: install new files.

Ref: #27150

Revision 53f32c6e (diff)
Added by Daniel Dehennin 6 months ago

Upgrade Hâpy: incorrect variable names

  • posttemplate/90-one-db: the “${override}” variable was renamed
    “${dst}” during a refactor.

Ref: #27150
Ref: #27156

Revision 9f9ef26e (diff)
Added by Daniel Dehennin 6 months ago

Upgrade Hâpy: properly use the exit code of the DB upgrade

The “exit” was done with the return code of the “echo” command and not
the “updateDB” one.

  • posttemplate/90-one-db: use “set -e” to propagate errors.

Ref: #27150
Ref: #27156

History

#1 Updated by Daniel Dehennin 7 months ago

  • Status changed from Nouveau to En cours

#2 Updated by Daniel Dehennin 7 months ago

  • Assigned To set to Daniel Dehennin

#3 Updated by Daniel Dehennin 6 months ago

  • Status changed from En cours to Résolu

#4 Updated by Daniel Dehennin 6 months ago

  • % Done changed from 0 to 100

#5 Updated by Daniel Dehennin 6 months ago

  • Status changed from Résolu to Fermé
  • Remaining (hours) set to 0.0

Also available in: Atom PDF