Applications > Status Classification

Taking into account a single application, five (5) different statuses are considered. In a first moment, driven by the dissemination activities performed by NA2, an application may request to be integrated into the EELA-2 Grid infrastructure. To do so, institutions wanting to propose new applications should answer the on-line survey available at http://applications.eu-eela.eu/survey/

Then, NA3 will evaluate such request and will attribute an appropriate status to the application according to its degree of maturity. Applications still under development (either on a local machine or on a computing cluster) will be considered as not mature (status S1) 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 ready for standalone use, i.e., it is either running on local clusters or using other Grid middleware but gLite or OurGrid. Usually this is the initial status of all new applications supported by EELA-2.

S3 - Application interfaced with gLite middleware. At this stage, the application proved to be able to run in the GILDA test-bed and is considered as "gridified"(**).

S4 - Application ready to be tested and validated. During this stage, the application is being migrated to the EELA-2 Infrastructure. The application is configured to use the EELA-2 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, composed by four (4) EELA-2 Grid sites.

When status S5 is reached, it means that the application is regularly submitting jobs on the EELA-2 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 EELA-2 community. This can be done by means of developing a Web portal interface or replicating the application packages across the Worker Nodes. Some applications may also have a submission machine configured to control large data challenges.

The figure below depicts the EELA-2 application life-cycle.

Life cycle schema
PLEASE NOTE:
(*) Only applications proposed by partner/member institutions are eligible to be supported. List of members. Here, "Support" means free technical support and access to the EELA-2 Grid infrastructure in order to have your application deployed either on OurGrid or gLite middleware.
(**) In EELA-2, 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 EELA-2 (e.g., the GILDA test-bed, OurGrid) and use at least one of the services of the middleware they are interfaced to (e.g., Job submission, Storage Elements, Catalogues, etc.)