WSO2 has some great documentation about upgrading between versions, but we have version 4.5.3, and I don't see in the documents if I can upgrade directly from 4.5.3 to 5.1.0?
Their docs go between levels, like 4.5.3 to 4.6, 4.6 to 5.0, 5.0 to 5.1.
Is there a process to go directly from 4.5.3 to 5.1 (without having to do the interim levels)?
No, We provide steps for migrating to next version from current version. You have to migrate step by step. Or you can combine the steps and migrate.
Providing migration scripts for two not consequent version isn't scalable. Image how many combination of script we have to maintain.
You can't migrate directly from 4.5.3 to 5.1.0, you have to do incremental migration. Other than that recently we released the new G-Reg 5.2.0 which is a much more improved version of 5.1.0, therefore we prefer you to use the latest version possible.
We have tested these migrations scripts in our local environments and it won't take that much time to migrate. lets say you have 500 artifacts in G-Reg 4.5.3 and it will take less than 2 days to do the migrations till G-Reg 5.2.0. By looking at the benefits your getting after the migration I think the time/resource consumed will worth a lot.
Please find the official documentation for Upgrading from a Previous Release. Please download the all new G-Reg 5.2.0 from here.
Related
Will there be any issue in my current notebooks and jobs if i upgrade my Databricks run time version from 9.1 LTS to 10.4 LTS
I didn't tried upgrading the version. If I upgrade it then will I be able to change it back to previous version
It's really a very broad question - exact answer depends on the features and libraries/connectors that you're using in your code. You can refer to the Databricks Runtime 10.x migration guide and Spark 3.2.1 migration guide for more information about upgrade.
Usually, the correct way to do is to try to run your job with new runtime, but using the test environment, where your production data won't be affected.
I've been trying to upgrade my ember app from 2.18 to 3.4.4 and I just want to know if I chose the correct ember version which is 3.4.4? Any response is much appreciated. Also what are the disadvantages or issues I may face if I jump from 2.18 to 3.8.1?
My personal recommendation is to upgrade from one LTS to the next LTS version. There's a great video from Ember Map that discusses a great strategy for upgrading your ember apps which I will summarize here in case the link ever goes stale.
Upgrade all forwards-compatible packages
Upgrade 3rd-party dependencies and addons, one at a time
Upgrade Ember CLI and friends using ember-cli-update
And in my opinion, use ember-cli-update --to next-lts-version-here. Once you upgrade to the LTS, fix deprecations and tests until all green, and then continue. I used this process to go from 2.16 -> 3.8 over the weekend
The latest long term support is 3.8. here is release cycle. You can jump to 3.8 if suits you.
There is a addon named ember-cli-update. It applies changes automatically. Also you can checkout the ember-blog to learn changes.
I am trying to upgrade a Couchbase Community server that is currently running 3.0 to 4.0. I am using the 'Amazon Linux' on AWS, and have used the CentOS 6 build to upgrade from 2.5 to 3.0 - that upgrade was super smooth. According to the documentation, I should be able to go from 3.x to 4.x just fine as well.
http://developer.couchbase.com/documentation/server/4.0/install/upgrade-matrix.html:
Upgrade from the latest version 3.x directly to version 4.x using any supported upgrade strategy.
But I get the message
couchbase-server conflicts with couchbase-server-community-4.0.0-4051.x86_64
I have found that the couchbase-server name is now reserved for the enterprise edition, and couchbase-server-community is now used in 4.0 for the community edition, which would explain the conflict. https://issues.couchbase.com/browse/MB-15716
Is this really an upgrade-breaking change? I cannot find any documentation on how to resolve this change short of uninstalling and reinstalling.
If it were me and since you are on AWS, just spin up new instances, install Couchbase on them and do rebalances where you add one in and remove an old one (1 in, 1 out or 2 in, 2 out, etc.). With the same amount going in and out of the cluster, the cluster will do a swap rebalance which is the most efficient. All of this can be done while up and serving traffic. This is a very standard upgrade path and the recommended approach when in the cloud.
Once upgraded, discard the old instances. Yes you are running more instances at the same time during the upgrade, but for the cost of a few lattes you are upgraded smoothly.
I have experienced the same conflict when trying to upgrade from Community version 3.0.1 to Community 4.0.0.
It is worth mentioning that if you uninstall the 3.0.1 version and then install 4.0.0, all your buckets and their data are kept. Maybe there are some cases where this would fail, always good to take a backup first, but in my case the transformation was smooth.
This was on my developer machine, for a cloud installation I really like the swap in/out which means you can do the upgrade without interruption of the service.
Is there any documentation available that describes the WSO2 svn structure?
It seems that the folder https://svn.wso2.org/repos/wso2/branches/ is deprecated.
Question 1: Should I only be working in the svn folder https://svn.wso2.org/repos/wso2/carbon/?
In the https://svn.wso2.org/repos/wso2/carbon/ folder, I'm managing to piece bits together, for example the difference between Carbon orbit, kernel and platform (see previous stackoverflow question).
In the https://svn.wso2.org/repos/wso2/carbon/platform/branches/ folder, there are 3 sub-folders:
4.0.0
4.0.2AF
4.1.0
Question 2: 4.0.0 and 4.1.0 seem to be for the Carbon Platform, but what is 4.0.2AF - Is this Application Factory?
Question 3: If I want to work on a specific version of Carbon say 4.0.3, it seems that I need to checkout the 4.0.0 branch. What else do I need to do so that mvn clean install will build 4.0.3 for me?
Question: Should I only be working in the svn folder https://svn.wso2.org/repos/wso2/carbon/?
WSO2 is currently doing active development in following svn directory.
https://svn.wso2.org/repos/wso2/carbon/
Question: 4.0.0 and 4.1.0 seem to be for the Carbon Platform, but what is 4.0.2AF - Is this Application Factory?
The branches in https://svn.wso2.org/repos/wso2/carbon/platform/branches/ are for the Carbon platform. The branch 4.0.2AF is for WSO2 App Factory (http://wso2.com/cloud/app-factory/)
Question: If I want to work on a specific version of Carbon say 4.0.3, it seems that I need to checkout the 4.0.0 branch. What else do I need to do so that mvn clean install will build 4.0.3 for me?
You can build Carbon 4.0.3 from following:
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/patch-releases/4.0.3/
You will be able to build products using the branch. That's why branch SVN URL is given in the links.
Each branch has a patch release for minor platform releases. For example: https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/patch-releases/
As mentioned in your answer, you can build from a tagged version also.
You can more details about product version and carbon version from the release matrix: http://wso2.com/products/carbon/release-matrix/
You can also subscribe to WSO2 mailing lists and get more information, if you have not subscribed already.
The answer to question 3 is build a checkout a tagged version (of course!!). Thanks to the answer here for pointing me in the right direction.
I was blindly following the wiki documentation which tells you to checkout a branch.
The release matrix for the wso2 platform is here: http://wso2.com/products/carbon/release-matrix/
If I want to build Identity Server 4.0.0 it seems that I need carbon 4.0.3.
Question 1. Will Identity Server only build on carbon 4.0.3, or will it build on 4.0.3+?
I have checked out the source from:
https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0
However, when I look in the orbit patch-releases folder, I only see:
4.0.1
4.0.2
4.0.5
4.0.6
Question 2. Which version of orbit patch release will I need to build for IS 4.0.0?
Question 01
To build IS 4.0.0 you need to build patch-release 4.0.3
But there can be some components from 4.0.0 up-to 4.0.3 but not 4.0.3+ So its better to build all main branch plus patch-release versions below your required version. As Ratha mentioned if you build online these jars will be downloaded if available.
Question 02
You need to build orbit patch-release 4.0.2 since it was used on IS 4.0.0
The reason for not having patch-release 4.0.3 version is there is no difference from 4.0.2 version. So same version is used during production.
Hope this will help you.
if you don't find particular version, that means product is released with older version of jars..
In your case, you might need to build 4.0.2..
Anyway if you do online build, if jars are available in the repo, they will be downloaded..You don't need to build older versions..
If not, you have to..