JRA1.1 - EMI Technical Objectives - Infrastructure Area 2

Design a common EMI service registry (M10)

Responsible : Infrastructure Area Leader (Laurence Field)

Technical Objective Details

  • Full description : Design a common EMI service registry that is required in order to discover all the service endpoints of the different middleware components.
  • Objective Version : 2010-10-31 (DNA1.3.1 - v014)
  • Infrastructure Area - Technical Objective 2
  • Due : M10

The following components are affected in the context of this technical objective :

  • EMI registry (new component)

Concrete Results

  • Wiki page or document with the EMI Registry Design
    • Status : In creation by EMI PT EMI Registry [ More Information ]
    • Milestone : 12/2011 - TOC of design document is available
    • Milestone : 01/2011 - draft document is available
    • Deadline : 02/2011

Open Issues

  • When is a first draft of the design available? [Already requested]
    • Auhor : Shiraz
    • End of November
  • Who/which audience will review the draft when available?
    • PTB should look at the draft...
  • When you believe you will start implementation
    • will be provides with the draft

Plans

2010-11-02

  • EMI Registry is relevant to the IIS (Globus-based) - relevant presentation at OGF30 in Brussels (J.P: Navarro)
  • Other ideas have been initially to have EMI Registry GOCDB as an operation database that provides input information to BDII
  • Discussions between Shiraz and Area leader Laurence of there to go

2010-11-23 - AHM Prague Update

  • Survey of fields to work on (query the information, informational aspects, message exchanges, federation, etc.)
  • Registry Requirements Presentation
  • Related Work and approaches based on DNS have been presented (PerfSONAR Lookup Service, TeraGrid's IIS, etc.)
  • List of EMI services to be published / discovered
    • A-REX, WMS, CREAM, UAS, OGSA-BES, SRM, EMI ES, others... (see slides)

2010-11-23 - EMI Registry Discussion

  • Update on the GOCDB discussion
    • How this affect the GOCDB needs to be understood, but EMI Registry will not replace the GOCDB
    • Nevertheless the context of the GOCDB needs to be taken into account
  • No agreements yet on data model and protocol
  • Q (Steve Fisher) : What will be left at information service? Will the registry replace everything?
    • No - but the scope completely is not clear yet
  • Slide 10 discussed how tomorrow looks like
  • Goal : Very light mechanism to find EMI (Info) service - existence of service
  • Projects / VO Support inside the system?
    • the query would be easier - but all in all more complex
  • More work in the document

Events in Context

2010-11-23 - AHM Prague

  • Presentation by Shiraz Memon
  • Title: "EMI Registry: requirements, and early design"
  • TBD (Morris, Shiraz) : Slides of event link, INDICO

Tracking

  • [2010-11-01] Morris : Tech Objective updates from DNA1.3.1; Addressed by EMI Product Team EMI Registry
  • [2010-11-01] Morris : Status Update requested from EMI Registry PT Leader Shiraz Memon
  • [2010-11-02] Shiraz : Update on activities, see plans section
  • [2010-11-23] Morris : Add information about EMI Registry Presentation at EMI AHM Praque

Next Steps

  • TBD (Morris): Status Check @ 2010-12-01
Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2010-11-23 - MorrisRiedelExCern
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback