Status Classification Status Classification

Taking into account a single application, six (6) different statuses are considered. An application may request to be integrated into the EUMEDGRID Support Grid infrastructure. To do so, institutions wanting to propose new applications should answer the on-line survey available at

Then, WP3 will evaluate such request and will attribute an appropriate status to the application according to its degree of maturity.

S1 - The application can run only in a stand alone environment, i.e., it is either running on local clusters or using other Grid middleware but gLite. Usually this is the initial status of all new applications supported by the project. During this phase the application will be considered as not mature and will not be accepted at this time. Otherwise, the application will be supported by the Project(*) and its gridification process will start from one of the following statuses:

S2 - Application interfaced with gLite middleware. At this stage, the application proved to be able to run in the either  into a  testbed infrastructure like GILDA or directly into to the EUMEDGRID-Support  infrastructure. In both cases the application is considered as "gridified"(**).

S3 -The application execution is now interfaced inside a web portal or any high level front end.

S4 - Application ready to be tested and validated. During this stage, the application is being migrated to the EUMEDGRID Support Infrastructure. The application is configured to use the EUMEDGRID Support central services. In some cases, in order to avoid any disruption in the production infrastructure while testing and configuring the application, users will be authorized to use only a subset of the current Infrastructure.

S5 When this status is reached, it means that the application is regularly submitting jobs on the EUMEDGRID Support production infrastructure and generating the expected results. At this stage, the group in charge of developing the application will be encouraged to make it available for all EUMEDGRID Support community.

S6 The applications reaching this status are ment to be in production status and application packages being installed across the Worker Nodes. Some applications may also have a submission machine configured to control large data challenges (see the Service Challenge service). 

The figure below depicts the EUMEDGRID Support application life-cycle:

Life cycle schema
(*) Only applications proposed by partner/member institutions are eligible to be supported.
(**) In EUMEDGRID Support, an application to be classified as "gridified", must be able to run successfully on the production infrastructure or in one of the infrastructures supported by EUMEDGRID Support (e.g., the GILDA test-bed) and use at least one of the services of the middleware they are interfaced to (e.g., Job submission, Storage Elements, Catalogues, etc.)