Skip to content
This repository has been archived by the owner on Oct 14, 2020. It is now read-only.

Upgrade Data Layer #38

Closed
afroDC opened this issue Jun 26, 2018 · 2 comments
Closed

Upgrade Data Layer #38

afroDC opened this issue Jun 26, 2018 · 2 comments

Comments

@afroDC
Copy link
Contributor

afroDC commented Jun 26, 2018

The process of upgrading from old version of Gluu Server to new version of Gluu Server generally require some changes to the data layer. So simply switching the containers from 3.1.2 to 3.1.3 isn't a painless process as sometimes new schema is necessary, or additional attributes are added to certain types of entries.

These examples can all be seen here. For 3.1.* it's mostly schema changes, since changing oxTrust or oxAuth from 3.1.2 to 3.1.3 will handle the war file upgrades.

Going forward, we have to have a process by which customers can relatively easily upgrade the data layer to work with newer versions in the future.

@afroDC afroDC added this to To Do in Docker Gluu Development via automation Jun 26, 2018
@afroDC
Copy link
Contributor Author

afroDC commented Aug 22, 2018

Here is an upgrade script that will automatically upgrade Gluu Server in place. We should take this as an example for upgrading the LDAP data for 3.1.4, as that's the only persistence layer that would impact version swaps.

https://repo.gluu.org/upd/3-1-3-sp1.sh

@afroDC afroDC mentioned this issue Aug 30, 2018
@iromli
Copy link
Contributor

iromli commented Mar 27, 2019

We have gluufederation/upgrade container to migrate data layer in DE.

@iromli iromli closed this as completed Mar 27, 2019
Docker Gluu Development automation moved this from To Do to Done Mar 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Development

No branches or pull requests

2 participants