Page 1 of 1

[Resolved] WAPT 1.5.21 to 1.7 but hypervisor change...

Published: March 25, 2019 - 3:08 PM
by Jonattend
Hello,

To resolve some issues and keep my WAPT system up to date, I'd like to migrate from version 1.5.21 to 1.7.

Theproblemis that version 1.5.21 was installed on our old hypervisor (Proxmox).

Version 1.7 will therefore need to be installed on the new hypervisor (Open Nebula).

Here's how I plan the migration:
- I install WAPT 1.7 on Open Nebula independently of the existing WAPT 1.5 installation
- I import my 70 packages from the 1.5 server to the 1.7 server
- I shut down WAPT 1.5
- I uninstall the WAPT 1.5 clients from the workstations
- I install the WAPT 1.7 client on the workstations (push installation)
- I'm happy.

Given that the packages are signed, copying the packages (via scp) and then scanning them (wapt-scanpackages) from the new server won't work? Could I import certificates and keys from a WAPT 1.5 server?

Thanks ;)

Re: WAPT 1.5.21 to 1.7 but hypervisor change...

Published: March 28, 2019 - 10:45 AM
by skoizer
Don't you have a tool in Nebula to extract a VM?
For example, VMware has the converter, which can handle physical to virtual, but also virtual to virtual.

Regards

Re: WAPT 1.5.21 to 1.7 but hypervisor change...

Published: April 2, 2019 - 11:06 AM
by Jonattend
Hello,

Apparently, it's possible to export the VM from Proxmox 3 and import it into Open Nebula.

So I've updated my current server to 1.7.x and I'll import it into Open Nebula when the time comes.

Thanks everyone ;)

! Resolved!

Re: [Resolved] WAPT 1.5.21 to 1.7 but hypervisor change...

Published: April 15, 2019 - 8:59 PM
by sfonteneau
To migrate or back up a WAPT server, you'll find the complete procedure in the documentation:
https://www.wapt.fr/fr/doc/waptserver-b ... r-on-linux