Hi,
During Jira issues raised relevant to 4.2.0 QA cycle we (myself, sameera,
kasung, ajith, shameera) observed that there are some design issues on new
CApp atomic deployment and discussed the limitations and problems that it
may produce. Since this may affect the all products related to this release
its better to decide whether we move on with the new implementation or we
keep hold this till we sort out the issues relevant to new implementation.
Here I list some issues we found during the process,
- Artifacts get cleaned up during housekeeping process
- During deployment CApp get extracted to CARBON_HOME/tmp directory.
These extracted artifacts will be needed during service and application
invocations so they need to be available during runtime. But
since this is
extracted inside tmp directory during housekeeping process this extracted
directory may get cleaned.
- As alternative we could use another directory instead of tmp. But
this also need to be cleaned since every time server start-up available
CApps will be extracted and this folder get filled with temp extracted
CApps.
- Probability of SVN conflicts during cluster set-up which has multiple
manager nodes
- In new design CApps get depsynced through cluster. So once it get
extracted on a node it will have a separate service.xml file.
Once multiple
managers try to change service properties this may cause svn
conflicts. (QA
team is testing the possibility of this)
- Tomcat support only one extract directory
- Discussion held last week with (Sameera, Azeez, Srinath, Sagara) it
was found that tomcat only support one extract directory and all webapps
(.war files) need to be placed on repository/webapps directory. The
conclusion of this discussion was to, not support .war files through
webapps. This also a limitation in new design.
Appreciate your suggestions on this,
Thanks,
Best Regards..
Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com
Twitter: http://twitter.com/ManKuma
Mobile: +94713448188
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
