Grid Computing Research
Grid is a parallel and distributed system in which resources spread across multiple administrative domains are able to select, share and integrate based on common rules they accept. Information about the resources hosted by multiple administrative organizations and other networked users is heterogeneous in machine architecture, software & operating system used and rules that gets integrated in Grid.
Click on the image to enlarge
The word "Grid" is used in comparison with Electrical Grids. There is no proper definition for Grid. Its up to the peoples understanding they call it as a Grid. Each and every organization have their own terminology for calling it as a Grid. Unification of 3 clusters in educational instruction is a Grid and also Unification of 3 clusters in different parts of the country is also Grid and further Unification of clusters across different's parts of the world is also Grid. Grid is a terminology used with respect to unification of resources per say they may not only be the clusters, they might be standalone machines scattered across the globe.
Initially I started my work exploring different Job Management Systems (JMS) and Resource management systems. You can say Job or Resource management systems as one and the same. Different crowd use different terminology but the underlying working is the same. Installed most of the JMS on our machines tested them with some job/task execution. Detailed their characteristics (software built,platform dependent,centralised control, decentralised control and many other characteristics), differentiated their characteristics from each other. Job management systems were Codine(Sun Grid Engine), LSF, PBS etc. Myself and my colleague Brian along with our guides help and suggestion we wrote a survey paper comparing various JMSs with our at home research system/product WebCom (metacomputer) which is currently updated and gridified to call itself as WebCom-G. This was my first paper and its title was "Comparison of WebCom in the context of Job Management Systems" published in Proceedings of the 2nd International Symposium on Parallel and Distributed Computing (ISPDC), Iasi, Romania, July 17-20, 2002.
Effectively after surveying and trying out many JMSs, we found that most of the JMSs were starting to add "G" by the end of their name. For e.g. somename-g. Most of the "g" refers to Globus. Globus toolkit (a bag of services - Please refer Globus website) is a software to build Grid environments. Systems that were suffixed/hypenated were Nimrod-G, Condor-G where "G" refers to Globus. So we researched and came with an idea of interoperating/leveraging existing JMSs (middlwares came into existant) with WebCom, we were able to interoperate with those systems. We wrote a paper regarding this title of the paper was "WebCom-G" (here G refers to Grid)and was published in Proceedings of the International Conference on Parallel and Distributed Processing Techniques and Applications (PDPTA 2003), Las Vegas, Nevada, U.S.A., June 23-26, 2003. Then started the work on core middlewares, user level middlewares, webservices and application development.
I was working on the Information gathering module with respect to grid running Globus and its integration with WebCom information services. WebCom is a core middleware or metacomputer developed by our group Centre for Unified Computing. In a Grid Environment resources such as PC's, clusters, databases , remote instruments owned by multiple domains are distributed across the world and we come to know about them through information services hosted by their respective domains. Everything that is involved in Grid is heterogeneous in architecture therefore real time information gathered by the core middleware's is important. Results of this research was published in the paper titled " The information gathering module of the WebCom-G operating system" and was published in Proceedings of the 2nd International Symposium on Parallel and Distributed Computing (ISPDC) - IEEE Press, Ljubljana, Slovenia., September, 2003
Presently experimenting and investigating with the grid to get collect the information about the resources hosted by multiple administrative domains, check the quality of information, but it has its respective branches depending on time and availability and how up to date is information gathered. Interested to resource forecast on a particular grid which would be similar to weather forecast for the next time scale or interval, this would give us an overall Quality of Service prediction for a particular Grid. This information would be incorporated with the WebCom system.
Grid is an open secure shop for processor cycles, memory or storage space and computation and presently it has been driving force for major players like IBM, HP, SUN etc. I am interested in using WebCom providing economic models built within it and providing quality of service for the end users.
In conjunction with the rest we are looking into modules which will interoperate with various middlewares and various versions of Globus Toolkit in particular. Globus seems to be diversifying itself from command line to web services; our grid group is looking into the interoperability with various layers or levels of Globus architecture with our WebCom system. Globus is the defacto toolkit for building Grid systems, but it just builds us the skeleton for us, rest of the flesh like Fault tolerance, Load Balancing, Scheduling will be exploited using WebCom as middleware