1 / 11

Virtual Organisations Building a common support infraestructure

Virtual Organisations Building a common support infraestructure. Virtual Organisations Why a support infrastructure. User. User. Resource. User. Resource. Resource. User. Resource. Resource. Resource. User. Resource. User. Resource. User. User. User. User. User.

ednam
Download Presentation

Virtual Organisations Building a common support infraestructure

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Virtual OrganisationsBuilding a common support infraestructure

  2. Virtual OrganisationsWhy a support infrastructure User User Resource User Resource Resource User Resource Resource Resource User Resource User Resource User User User User User • Users own and require resources • Shared • Collective A infrastructure to support this activities

  3. Virtual Organisations User Resource User Resource User Resource User Resource Resource User User • A set of users • Working in a certain common area • Sharing similar needs • Data processing • Access to data sources • Interaction among them • Pursuing similar goals • Plug-and-play • A set of resources • Operated by specialized teams • Operated by users • Plug-and-be-played

  4. A common support infraestructureThe IRISGrid case • pkIRISGrid • Distributed RAs per organisation/VO • Based on the IRISGrid directory • The IRISGrid AAI • Grid portal toolkits • Collaborative tools • From mailing lists to real-time systems • Resource location • Based on a federated approach • The IRISGrid Directory • VO management: Users, centres, resources, research areas • Web interfaces wherever possible • As integrated as we can

  5. Collaborative toolsThe good old mailing lists • Essential for basic interactions • General coordination lists • Participants, support staff, middleware staff,... • General areas: HEP, biotech, astro-sciences,... • Owned by the IRISGrid admins • A specific list per VO • Connected to the general areas the VO is classified in • Owned by the VO managers • Based on listserv • The current mailing list software at RedIRIS • Plans to migrate to Sympa • Better integration with the supporting infrastructure

  6. Collaborative toolsPresence and instant messaging • Informal and direct interaction • Both P2P and collective • Automatic roster initialisation • People in the VO(s) a user is included • Loose control • Direct management of contacts • Free creation and management of chat rooms • Based on Jabber • Hosted at the RedIRIS server • Experiments with a server mesh • Experimenting with the integration of real-time • AAI-enabled Wiki

  7. Resource location • In the broad sense we have been using so far • From a cluster to a set of related papers • Common directories are the usual answer to this • But they face data partition • Formats, protocols, security (and privacy) considerations • The result is the continuous re-building of central repositories of data • Almost automatically outdated with respect to their once local sources • The federated model comes into play once again • Accessing or collecting data from them using a trusted link • Maintaining total autonomy for the federated repository • Policies, methods, interfaces • Offering a common (possibly particular) view of information

  8. The Searchy architecture • Each source incorporates an agent, available through a SOAP interface • Uses RDF as internal representation • Agents for LDAP, SQL, Harvest, the Google API, and Searchy itself

  9. The IRISGrid Directory User MDS Centre User User VO User MDS User Centre User User VO User MDS Centre User Area classification User IRISGrid Globus Directory The IRISGrid Directory

  10. The IRISGrid DirectoryCOPA coding schema • A coding schema to support (virtual) hierarchical access • Based in creating strings identifiers (URNs, for example) that resemble the hierarchy of a given classification (or ontology) • Identifiers are added to data available for a certain element • Mappings between COPA identifiers and their semantics are kept in a separate repository (directory branch, for example) • Simplifies searches and navigation • Decouples representation from the view offered at each moment • Several views can be offered in parallel • And hot-swap them • More on this athttp://www.rediris.es/ldap/copa/copa-intro.en.pdf

  11. Web interfaces • Navigation and management of the IRISGrid Directory • Navigation and searching by research areas • UNESCO Thesaurus, CATRE, e-Ciencia • VOs related to a certain area • Users participating in an VO • Collaborative resources available to a VO • mapfile generation • Centres related to VOs • Navigation through the computational resources (MDS) • pkIRISGrid • Users • RA operators • Pursuing plug-and-play/be-played

More Related