l10n.opensuse.org: Weblate migration started

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

l10n.opensuse.org: Weblate migration started

Stanislav Brabec
As it was announced last week, Weblate upgrade process has just started.

I removed all change privileges for all users and guests and left
Weblate running. So it is basically in a read-only mode.

If you are project admin, you can still edit your project. But please
don't do it! Your changes will not be migrated.

--
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                         e-mail: [hidden email]
Křižíkova 148/34 (Corso IIa)                  tel: +49 911 7405384547
186 00 Praha 8-Karlín                          fax:  +420 284 084 001
Czech Republic                                    http://www.suse.cz/
PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: l10n.opensuse.org: Weblate migration started

Stanislav Brabec
Alexander Melentev wrote:

> 2017-06-20 15:09 GMT+03:00 Stanislav Brabec <[hidden email]
> <mailto:[hidden email]>>:
>
>     As it was announced last week, Weblate upgrade process has just started.
>
>     I removed all change privileges for all users and guests and left
>     Weblate running. So it is basically in a read-only mode.
>
>     If you are project admin, you can still edit your project. But please
>     don't do it! Your changes will not be migrated.
>
>
> Great, I'm eagerly waiting for new Weblate. But I have a question about
> read-only mode: I noticed that while I cannot do any changes to
> translations, Weblate itself recieves new "original" strings
> successfully - won't it create consistency problems during migration, if
> some new string arrives during database dump?
>

Good point! These changes were initiated by GitHub Weblate hooks.

Hopefully, I did two dumps to be safe. One before changing taking off
all permissions, and second after that, and compared them. These logs
differ only in auth_group_permissions (expected) and django_admin_log
(not important). So the snapshot is consistent. I took the first dump
for the purpose of the migration.

After starting the new instance, we will have to update all repos. It
will perform all these changes in the migrated database.

Actually, all translations are backed up in the GitHub. The critical
parts are suggestions and comments, which are stored only in the
database. Database also stores detailed log of all changes, check
results and everything else you see in the web interface.


Migration progress report:

Database is now being upgraded from 2.10 to 2.13.1. Now it executes the
most expensive weblate-2.12 migration step:
  Applying trans.0073_auto_20170209_1359...

The complete migration of mysql database to 2.13.1 is expected to finish
in 16 hours.

Then we will start Django migration from mysql to postgresql, which is
the most tricky part.

--
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                         e-mail: [hidden email]
Křižíkova 148/34 (Corso IIa)                  tel: +49 911 7405384547
186 00 Praha 8-Karlín                          fax:  +420 284 084 001
Czech Republic                                    http://www.suse.cz/
PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]