Topic: test upgrade 10.1 to 11 beta

[logs]

I tested the upgrade with MigrateHelper from a smaller server with 100 users from 10.1 to 11 Beta.
The upgrade apparently worked well. server-manager login OK
I performed a dnf update and installed Contribs:

smeserver-certificate
smeserver-learn
smeserver-migratehelper
smeserver-service_control
smeserver-systemd-control
smeserver-vacation
smeserver-wbl


I tried logging in as a RoundCube users ok,
Install smeserver-qemu-guest-agent <<<- Fail deps

After install smeserver-qmHandle fail all logins on roundcube and not read queue on server-manager.
After remove smeserver-qmHandle logins ok

Tested on virtual machine proxmox:
Host 32 x AMD EPYC 7302P 16-Core Processor (1 Zócalo)
/ - /boot - swap ---> virtio0
/home/e-smith/files ---> virtio1

screenshots of hardware and options

Any suggestions on testing?

[ReetP]

As previously mentioned, most contribs have still to be worked on.

Better to test one at a time, check bugs and src.koozali.org to see what has been worked on etc. Otherwise you won't be able to see the wood for the trees.

If you DM me with your full name & a email address for notifications I can add you to Rocket.Chat so you can help with specific testing and keep up with development.

[ReetP]

Estas en España??

Vivo cerca Valencia pero soy Ingles

[logs]

Name = Jose Maria Garcia Sanchez
Mail - "Not public"

[logs]

 Si en Huesca y Zaragoza, español.

[logs]

I will proceed to test an upgrade of a server with 700 users, using a similar procedure
but changing to different types of processors and activacion vIOMMU and NUMA.
q35/host
x86-64-v2-AES
x86-64-v3
x86-64-v4

[ReetP]

Si en Huesca y Zaragoza, español.

Vale!! Encontado

[ReetP]

Name = Jose Maria Garcia Sanchez
Mail - "Not public"

I have sent your login details. Come and say hello!

[logs]

Upgrade another server
Proxmox 9.0.10
x86-64-v4 does not boot
x86-64-v3 and host, --> boot

Enabling vIOMMU/virtio and NUMA respond more slowly,

I have disabled vIOMMU and IO pressure drops dramatically.
I need to review the case.


Procedure:
Restored production server on another node.
Added vfat small disk to load smeserver.tgz created by migratehelper
Started with sysreccd iso, formatted vfat small disk and transferred smeserver.tgz to vfat disk.
Stop and change the iso to sme-server in the installation, customize the partitioning
vda1 /boot + format
vda2 / + format
vda3 swap
vdb1 /home/e-smit/files (not format contains user data)

On the first reboot, reconfigure the network, remove the vfat disk from /etc/fstab, and add usrquota,grpquota to /home/e-smith/files.
dnf update, reboot, install contribs, and check/disable certain cronjobs.
Only installed contribs:

smeserver-certificate
smeserver-geoip
smeserver-learn
smeserver-migratehelper
smeserver-vacation
smeserver-wbl

I'm reviewing what's in contrib-testing and dev.

I have to see if there is anything that allows me to access user accounts in Roundcube
and bulk export/import users contact books, because that's hell...   

[ReetP]

Regarding your boot issues please ask on Rocket. Lots of us use Proxmox.

That or bug it, but check the Rocky v8 requirements.

Have no idea if any of those contribs work. They may all be broken. Test ONE at a time please and then bug it.

This is still Beta and contribs are slowly being worked on.

Roundcube - no idea as yet. Horde had effectively become unsupported so we had to move on.

[Jean-Philippe Pialasse]

if you manage to write something to import those, we would be happy to integrate it.
As John said we had to make choice with no release from horde for years and php moving on.

[logs]

The migration also doesn't pick up the aliases in Roundcube. The email address for the identities is user@domain.xxx, not the alias.
The set of problems with migrating the email/groupware platform and the remnants of the previous one, in my opinion, don't warrant migrating the production servers.
I think extracting users, passwords, and nicknames and being able to inject them into a clean installation is the appropriate approach, because I see no other solution than restoring a copy of the production servers, changing all passwords to a predefined one, and going user by user, extracting their address books and other groupware applications used, importing them into the clean installation, configuring the identities, etc., and finally applying the exported passwords. Roundcube also doesn't pick up the alias when creating new users.
I'm looking into whether adapting the migratehelper or Lat* script might be the way to go...
In any case, it's a painful operation.

[Jean-Philippe Pialasse]

roundcube needs user to login to create an entry.

issue was with horde previous setting where user preferences where stored in different db entry depending on what  url the user used to log in.  You might end up with multiple profiles for the same horde user.


however looking at your last post i am wondering if you are not in a XY problem.
Would you able to state what your expect and what you observe?
I might save you lote of time rather tha. implementing something first. 

[ReetP]

You do have a Rocket account now.

Much easier discussing there than here.

We don't bite!