(This message has been automatically imported from the retired mailing list)
since there’s been a lot of changes between 1.1 and 2.0 I’d like to
tackle the migration processes on several layers and would appreciate
your input on the matter - would be great if you could comment on the
ideas below given your practical experience with existing 1.1 environments.
There will be a chapter in the documentation going through the migration
process step by step. This will be added as one of the first chapter in
2.0 docs so early users can give it a try as soon as possible.
A new command line extension is being develop as we speak. Essentially:
$ zato migrate /opt/zato/cluster1/load-balancer/
Migrated /opt/zato/cluster1/load-balancer from 1.1 to 2.0.0pre0.rev-9c9e147b
So one will give it a path and it will figure out what version a given
component is in and migrate everything that can be done automatically,
i.e. it will update server.conf or logging.conf
There’s a whole set of Alembic migrations added so that the ODB,
particincluding schema and new rows, can be migrated to 2.0
$ ./bin/alembic upgrade head
I’m sure there will be still some things to be performed manually - they
will be included in the migration instructions above.
Question is, do you think anything in particular should be given special
attention? What would you like for the migration process to take care of
as a priority?
thanks a lot,