On Mon, Aug 3, 2015 at 2:19 AM, Akila Ravihansa Perera <[email protected]> wrote:
> Hi, > > I've been working on evaluating the effort needed to upgrade Carbon kernel > which is the underlying platform of Stratos to its latest version 4.4.0. > Since this is a major version upgrade there are some API changes in the > kernel hence some components needs to be updated to be compatible with the > new Kernel. Also this means we will have to upgrade all Carbon features > that we use in Stratos. > > Following is a high-level list of Carbon features that we use currently in > Stratos > > OAuth identity feature for metadata service and REST API > CEP event processing features > Siddhi engine features > Webapp management features > Jaggery features > Synapse mediation features (in Stratos LB) > > Following are the tasks that I identified that needs to be done for the > upgrade. > > 1. Uplift kernel dependency version in pom files > 2. Create the p2 profile for Stratos core and LB with new features > 3. Create the distribution for Stratos core and LB with new configuration > files > 4. Update Stratos code base to match the new features and Kernel > 5. Merge all recent changes done in master branch. > 6. Upgrade CEP artifacts; this includes execution plans, window > processors, input/output adaptors, stream definitions > 7. Upgrade Stratos console UI module > 8. Upgrade test framework dependencies and integration tests > 9. Test the functionality (end-to-end testing of all features and > use-cases) > > I've already completed above tasks up to 5. While upgrading the Kernel I > faced many OSGi issues and feature conflicts. Therefore I had to stop the > upgrade process and do a complete refactoring of pom structure. I've > removed duplicate dependencies and cleaned up OSGi package imports/exports. > Also parameterized all the dependency versions and created properties for > every dependency version in the root pom. > This is the correct approach. With 4.4, we have changed the group-id's of each git repo (eg: commons, deployment) to match their names accordingly. And the features coming from these repos will also have the same group-id name changes. You will have change your pom files with correct dependency names (which I think you have already done here). > I'm still facing ClassNotFound issues while deploying Stratos webapps > (oauth2, api). Currently investigating the root cause. Also Stratos console > Jaggery app is broken with new Kernel and Jaggery features. I can view the > login page but it throws some backend exception when logging in. > This could probably be due to multiple exported package versions or missing required packages. Hope you are on the right path in identifying the issues. Any unresolved bundles or unwired packages here? > > You can try it out by building from the source at [1]. I've attached a > screen shot of new Carbon console UI. > > [1] https://github.com/ravihansa3000/stratos/tree/carbon-4.4.0-migration > > Thanks. > > -- > Akila Ravihansa Perera > WSO2 Inc.; http://wso2.com/ > > Blog: http://ravihansa3000.blogspot.com > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Kishanthan Thangarajah* Associate Technical Lead, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
