Derived clustered information

From EGI Knowledge Base

Jump to: navigation, search

Contents

[edit] Middleware

[edit] Smooth integration of new components

EGI should be prepared for accepting new MW components, coming from external or internal development, which will co-exist or replace one another eventually.

  • Interoperability is critical. Despite interface standardization is necessary UC-NGI-D-standardization, it does not solve the problem completely UC-NGI-SW-elmroth, UC-NGI-NT-II.
  • Replacable small components with well-defined functionality are prefered to huge monoliths UC-NGI-SW-elmroth
  • Procedures have to be defined to accept new components coming from external development, including roles of EGI and NGI's
  • It is useful to share MW components (and even service instances) among different user groups/communities. How candidates for sharing are identified? UC-NGI-D-tools
  • User communities may reqiure completely new or tailored components. How these are provided, who triggers, decides and is responsible for the development? [UC-CERN-pm-IV,UC-NGI-FR]

[UC-NGI-CZ-III,UC-NGI-CZ-III], [UC-NGI-UK-IX,UC-NGI-UK-IX]

[edit] Component lifecycle

  • contributed components may not arrive in a state ready for production EGI has to define procedures for their "hardening", "experimental services" deployment may be an efficient way UC-NGI-CZ-VII
  • maintenance and production updates of all components is an issue in the large-scale deployment, EGI should define procedures for both fast propagation of security updates to avoid vulnerability risks, as well as gradual deployment of new versions which may introduce backward incompatibility UC-cern-middleware

UC-NGI-CZ-IX, UC-NGI-UK-VIII

[edit] One or more MW stacks

  • Running multiple middeware stacks is perceived unavoidable, at least in mid-term UC-KnowARC, UC-NGI-SW-elmroth
  • Applications tend to build "grid of grids" UC-KnowARC, even defining services at the meta-level UC-VO-ILDG-access; the approach is probably unavoidable when extending outside Europe

UC-NGI-UK-III, UC-NGI-UK-V, UC-NGI-UK-VI, UC-NGI-UK-VII, UC-NGI-PL-infrastructure-I, UC-NGI-UK-XVI

[edit] Support of interactive use

[edit] Security issues

[edit] Large redesign is required

  • "rethinking grids from scratch", taking account of experience, with more strict control UC-NGI-NT-III
  • Introduction of novice users cannot be achieved with the current middeware due to its design, its reconsideration is necessary UC-cern-middleware

[edit] Other specific functionality requests

UC-NGI-CZ-V

[edit] Infrastructure and Operation

[edit] Joining the Grid

Definition of basic elements/subjects for interaction within European grid environment.

UC-NGI-FR-II-VOs-man-software-III, UC-NGI-FR-II-VOs-users-I, UC-NGI-FR-II-VOs-users-II, UC-NGI-FR-II-VOs-users-III, UC-NGI-FR-II-VOs-users-IV, UC-NGI-FR-II-VOs-users-V

UC-IPC-I, UC-NGI-NW-I, UC-NGI-UK-I, UC-VO-ILDG-certificate, UC-NGI-UK-X, UC-NGI-UK-XV

[edit] Working with the Grid

Set of elementar steps required for seamless interaction with grid environment.

[edit] Organization of operations

What approach is the environment built on (best effort? SLAs?). Possibility to require to label resources as "EGI proofed/confirmed" (based od selected requirements).

UC-NGI-UA-centers, UC-NGI-UA-infrastructure, UC-NGI-UA-support, UC-NGI-SK-cell-II, UC-NGI-SK-cell-III, UC-NGI-SK-kwf-infrastructure, UC-VO-ILDG-storage, UC-VO-ILDG-data-management


[edit] Policies

Set of rules to cope with international relations, responsibility to take care of this issue (international partner itself or special EGI group?).

[edit] Commercial related issues

Definition of procedures for handling private sector requirements.

[edit] Training & User Support

Responsibility and way of delivering training/user support for work within the Grid.

[edit] Monitoring and Accounting

Definition of procedures how to evaluate the resources.

[edit] Resource provisioning

UC-bazaar-resources-I, UC-bazaar-resources-II, UC-bazaar-resources-III, UC-NGI-GR-V, UC-NGI-UA-VOs, UC-degree-join, UC-NGI-PL-application-I, UC-NGI-UK-IV, UC-degree-create, UC-NGI-UK-XI, UC-NGI-UK-XII, UC-NGI-UK-XIII, UC-NGI-UK-XIV

[edit] Applications

Majority of application-related use cases have specific requirements. It seems better to match those directly to identified WP3 functionalities. However, several following issues had been identified as critical.

[edit] Commercial software licences

[edit] Parallel job run

[edit] Interactive jobs

[edit] User support for individual application group

UC-SEEGRID-I, UC-SEEGRID-II, UC-SEEGRID-III

[edit] Specific individual applications

UC-bioinfogrid, UC-IPC-IV, UC-NGI-GR-III, UC-NGI-GR-IV, UC-NGI-GR-VI, UC-NGI-GR-VII, UC-NGI-GR-VIII, UC-NGI-GR-IX, UC-NGI-GR-X, UC-NGI-NW-II , UC-NGI-NW-III, UC-NGI-PL-application-II, UC-NGI-SK-astro, UC-NGI-SK-cell-I, UC-NGI-SK-kwf-infrastructure-II, UC-NGI-SK-kwf-infrastructure-III, UC-NGI-SK-kwf-user, UC-NGI-SK-kwf-user-II, UC-NGI-SW-persson, UC-NGI-UA-application, UC-NGI-UK-disaster, UC-VO-ILDG-search, UC-degree-degree, UC-RINGRID

Retrieved from "http://knowledge.eu-egi.eu/index.php/Derived_clustered_information"
Personal tools
hidden pages