By: Colt McCormack user 13 Jul 2020 at 1:09 p.m. CDT

4 Responses
Colt McCormack gravatar
We have an existing 3.1.2 Gluu instance running directly on Ubuntu 16.04. We are in the process of testing out the upgrade on a separate server by exporting from production, importing to a fresh 3.1.2 install on a test server, and then upgrading from there. We have successfully completed this upgrade on the test server, but would like to move over to a docker version of the software to match all the other software on the server. I have been unable to locate any good information on how one makes the jump from a running the original Gluu 3.x installs to the Docker versions. Is there any documentation or guidance on that? Should the migration be made after upgrading the standalone version all the way to 4.1 or at an earlier version and then follow the Docker upgrade instructions?

By Michael Schwartz staff 13 Jul 2020 at 1:17 p.m. CDT

Michael Schwartz gravatar
It's not something we really recommend. We provide the Docker install mostly for demo purposes (i.e. run on your laptop). For container deployment in production, we recommend Kubernetes. You can see the old "Docker Edition (DE)" docs: [https://gluu.org/docs/de/](https://gluu.org/docs/de/) or check out the [Kubernetes section](https://gluu.org/docs/gluu-server/4.1/installation-guide/install-kubernetes/) in the current docs. Migrating from Community Edition (CE) to Cloud Native (CN) is not something for which we have automated scripts. It's a project we normally hand to one of our professional services partners who understands how to move the required files and underlying databases. Migrations like this are out of scope of Community Support, as there may be some one-off stuff you need to do.

By Colt McCormack user 13 Jul 2020 at 1:31 p.m. CDT

Colt McCormack gravatar
Understood. Kubernetes isn't a problem as we use that extensively as well. Is there someone I could speak to about pricing this to determine if we want to go that route? We aren't really looking to manage a large cluster, but I don't see any import/export scripts for 4.x so I'm a bit leery of being able to easily move our instance around in the event of hardware failure, need to move to a different host, etc. Gluu runs all of our products' identity management and authentication so losing it even for a day could be catastrophic.

By Michael Schwartz staff 13 Jul 2020 at 2:34 p.m. CDT

Michael Schwartz gravatar
There are upgrade notes here: [https://gluu.org/docs/gluu-server/4.0/upgrade/](https://gluu.org/docs/gluu-server/4.0/upgrade/) You can setup a time to chat at [https://gluu.org/booking](https://gluu.org/booking) My gut feeling is that we're probably not going to have a great support option for your organization, because our pricing is skewed towards large enterprise customers. But happy to chat.

By Colt McCormack user 13 Jul 2020 at 3:27 p.m. CDT

Colt McCormack gravatar
Thanks Michael. I'll setup a time soon, though I suspect you're correct on pricing based on our past experience. I've followed the guide you mentioned successfully and posted at least one [pull request](https://github.com/GluuFederation/community-edition-setup/issues/692) and found [another issue](https://support.gluu.org/customization/8577/static-resources-return-404/#at61929) in the upgrade script that I believe will need to be addressed (which I fixed manually). My concern is once the upgrade is complete and we need to migrate our Gluu instance to another machine down the road there doesn't appear to be any scripts for that process like there is with the 3.X versions, unless I'm completely missing something in the docs. Do you know if there are plans to implement that in the future? We have automated backups of the container via the Tarball method mentioned in the backup section. Would restoring one of those to a new server and then going through the change IP address docs be an acceptable way of migrating over?