Center for Development of Advanced Computing. Cloud use case Deployment work flow of the caTissue follows the model which needs installation, configuration.

Center for Development of Advanced Computing

Cloud use case

• Deployment work flow of the caTissue follows the model which needs installation, configuration for every site

• caTissue can leverage the Cloud/Grid environment by hosting it as SaaS over Cloud/Grid infrastructure

• Presently we are refactoring the application to be deployed over GARUDA Grid

• The later stage could be making the tools Cloud aware

Architecture changes• caTissue architecture follows the traditional MVC architecture • Web application hosted in single web container• Needs to be re-factored to identify how parallelism can be brought

in the business layer– The idea is to achieve fail safety and load balancing at web application

level– Through clustering, high performance through parallelizing code in

the business layer and – Fault tolerance, efficient, consistency at the data base level through

replication. – Expected architecture after refinement of the code is shown in Fig.1– The availability of services at each layer namely web application layer,

business layer and Storage Layer is ensured using the Grid resources and platform.

Grid Infrastructure

Issues encountered 1

• Cyclic dependencies between the model and view packages for example package edu.wustl.catissuecore.action and edu.wustl.catissuecore.bizlogic

• Although jar packages were build by build scripts, the deployment does not use lib deployment mechanism, it dumps all compiled classes in container

• Classes with same package and name are present in more than one location but class content are different

• The package structure is not modular but a huge list of classes that sometime appear unrelated

Issues encountered 2• No module level , package level dependency diagram/package

structure is available• Content of dependent project war is directly added in caTissue war

while building instead of using the lib mechanism• The build script has lot of build intelligence and hence using the IDE

just presents huge bunch of multiple web apps and classes• Due to above and such problems, we are having trouble in

modularizing them at binary level for componentizing over load-balanced grid deployment. Also due to lack of clear dependencies and relationships, we have to go through code to understand the class/package hierarchy

• The build script poses serious challenge when runtime or debug is invoked as it is external to the development environment

Information needed• caTissue suite comprises of three applications caTissuecore, caTIES

and CA, What is the relationship between these applications ? How they communicate with each other?, Is it possible to make them available on separate web server and communicate?

• How caTissue handles the security realms for user domain? How it can be updated to have multi-tenant architecture (i.e. supporting security realms of multiple organizations)?

• caTissue makes the use of Dynamic Extensions, what is that? Is it part of caTissue application or of caTIES, CA?

• What is the role of caCORE SDK in caTissue suite?• Is it possible to serialize the session attributes of caTissue to enable

session replication on the clustered web server?