Hi Dinesh, Great! Please provide your thoughts on the changes required in registry persistence logic as you progress.
Thanks On Wed, Jun 18, 2014 at 12:27 PM, Dinesh Bandara <[email protected]> wrote: > Hi, > > When I started work on [1] and I thought to persist cartridge > configuration in JSON format in Stratos Manager's registry and observed the > above behavior which does not provide the readability of existing > artifacts. > Will work on [2] > > [1] https://issues.apache.org/jira/browse/STRATOS-568 > [2] https://issues.apache.org/jira/browse/STRATOS-664 > > Thanks > > > On Wed, Jun 4, 2014 at 10:18 AM, Imesh Gunaratne <[email protected]> wrote: > >> Hi All, >> >> In Stratos 4.0.0 Stratos Manager, Cloud Controller and Autoscaler store >> their artifacts in registry in binary format (Java objects are serialized >> and stored). This might cause problems when migrating an existing Stratos >> deployment to a newer version with changes in above artifacts. >> >> Therefore it would be better if we could change this format to JSON or >> something similar which could be easily read and updated if the definitions >> of the artifacts change in a newer Stratos version. >> >> More importantly we might need to create tasks in JIRA to prepare >> migration scripts if we do any modifications to the above artifacts once >> 4.0.0 release is done. >> >> https://issues.apache.org/jira/browse/STRATOS-664 >> >> Thanks >> >> >> -- >> Imesh Gunaratne >> >> Technical Lead, WSO2 >> Committer & PPMC Member, Apache Stratos >> > > > > -- > *Dinesh Bandara* > Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > -- Imesh Gunaratne Technical Lead, WSO2 Committer & PPMC Member, Apache Stratos
