Preparing and maintaining integration and interoperability in JRA1.7

The EMI work package JRA1.7 is responsible for the continuous verification of interoperability and integration of the EMI services. To request, maintain, visualize, and evaluate all the informations concerning interoperability and integration between EMI services it was decided to use MS EXCEL sheets. These sheets provide usually matrices of EMI services where components are compared against any other relevant component of an appropriate area like computing, security etc. Since matrices with hundreds of rows and columns can become easily unclear, the matrices were structured hierarchically in sub-matrices.

So, on top level there are two total overview matrices each time for the interoperability verification and the integration verification. At second level there are area-sub-matrices for the four main areas computing, data, infrastrucure, and security according to EMI deliverable DNA1.3. Finally, we have for each area further sub-matrices related to the EMI PTs. The latter were used especially for status requests to PT leaders pointing them directly to the parts of the EXCEL sheets they should edit. The top-level and area-level matrices are published periodically below to get an actual status overview of the verification tasks.

EXCEL-tool to get sub-matrices from the total-overview matrices

The tool is an EXCEL-VBA macro which can be started by STRG-Q or calling Modul1.callForm. This tool was designed for the task-leaders of JRA1.7.1 to get an automated process of creating sub-matrices from the top-level matrices. PT leaders don't need it. They will get the appropriate request sheets periodically from the JRA1.7 team.

MatrixMacro

Explanation of the sheets

  • Every sheet is published in Excel 2007 and Excel 97-2003 format. In general both formats should be suitable to OpenOffice users according to the OO version.
  • The status in a cell can be set by using the drop down menu of the cell (seems not to work for Excel 2007 file in OO), or copy and paste.
  • + means fully interoperable/integrated
  • o means partly interoperable/integrated (e.g. only in one direction). Please, describe partly-statuses with a cell-comment.
  • - means not interoperable/integrated, or if you not yet know the answer when editing the matrix.
  • n.a. means not-applicable
  • n.i. is generated automatically by the Excel-VBA-macro and means 'not identified', e.g. data area is not evaluated with security area in terms of interoperability
  • If you want to add a comment to a status in the cell, please use the comment function for a specific cell (available by right clicking the cell).
  • Concerning interoperability, if components consist of client and server, and are not divided explicitly in the matrix, try to understand the rows as client side and the columns as server sides. For integration try to consider both client and server components in one row.
  • If you as PT leader think that an internal component (marked as int in 'type' column) shouldn't be listed in the matrix, just inform the task team.

  • Compared areas for interoperability verification:
    Area Areas Example
    Compute Compute, Data Data-staging with JSDL
    Data Data SRM interface at DPM and STORM
    Infrastructure Infrastructure Glue schema at UNICORE 6 CIP and BDII
    Security Security SAML at UNICORE 6 UVOS and VOMS

  • Compared areas for integration verification:
    Area Areas Example
    Compute Compute, Data, Infrastrucure, Security UNICORE 6 integrates TSI, UVOS, GridFTP, CIP
    Data Data, Infrastrucure, Security DPM integrates GridFTP, VOMS
    Infrastructure Infrastructure, Security ARGUS integrates gLite BDII
    Security Security, Infrastructure CIS integrates CIP

Difference between interoperability and integration

  • interoperation matrix - services being interoperable in general by using standard interfaces (no list available, to the best of PT leader's judgement)
  • integration matrix - EMI services integrating other EMI components

Interoperability verification

Integration verification

  • Status matrices

  • Verification matrices

Feedback from PT leaders

Feedback Shows if and when PT leaders have sent back requested matrices.

Identifying relevant component intersections

Will be defined and performed as soon as the first overview interoperability and integration matrices are completed.

Performing integration and interoperability on EMI Testbed

The identified relevant component intersections from the matrices that point to interoperability and integration aspects in the projects will be analysed in detail. This includes the availability of integration tests and or compliant tests (to check interoperability) in the form of dedicated tests (e.g. unit tests) or specific setups (e.g. simliliar like production applications).

These tests in turn will be carried out during the course of the project in close collaboration between JRA1.7, JRA1.8 and the product teams. The infrastructure that is used for these identified tests will be the EMI testbed.

Deliverables

  • DJRA1.7.1 - coming soon

Other relevant documents

  • EMI1-DevPlans Nice overview which EMI components implement which standards. Useful for interoperability verification

Testing Strategy Meetings

  • 2010-11-18 - Testing Strategy Meeting GLUE2 Adoption
    • Doodle : http://doodle.com/r6d5zgfhxi57khqk
    • 14:00 - 15:00
    • Task: Every involved PT should have a rough idea how this feature can be effectively tested
    • The following testing strategy will be revised : [ More Details ]
    • 2010-11-16 : Meeting announced by Morris

Task Force EMI-UI and EMI-WN

List of EMI meta-packages

Integration Objectives for DJRA1.6.2

-- AndreGiesler - 15-Nov-2010

Topic attachments
I Attachment History Action Size Date Who Comment
Microsoft Word filedoc EMI_Integration_Plan-v0.2.doc r2 r1 manage 294.0 K 2010-12-20 - 03:09 AGieslerExternal draft
Microsoft Word filedoc EMI_Integration_Plan-v0.4.doc r3 r2 r1 manage 657.5 K 2010-12-22 - 17:22 AGieslerExternal Draft version of DJRA1.6.1 (chapter 6+7 incomplete)
Microsoft Word filedoc EMI_Integration_Plan-v0.5.doc r5 r4 r3 r2 r1 manage 1093.0 K 2011-02-07 - 20:10 AGieslerExternal Review Version
Microsoft Word filedoc EMI_Integration_Plan-v1.0.doc r2 r1 manage 1093.5 K 2011-02-08 - 20:26 AGieslerExternal After Review
PDFpdf EMI_JRA1.6.1_v3_PartInteropIntegration_v1.pdf r1 manage 101.8 K 2010-10-06 - 16:39 AGieslerExternal  
Microsoft Excel Spreadsheetxls IntegrationCompute.xls r3 r2 r1 manage 107.5 K 2010-11-19 - 09:56 AGieslerExternal compute integration matrix (.xls)
Unknown file formatxlsx IntegrationCompute.xlsx r5 r4 r3 r2 r1 manage 27.0 K 2010-11-19 - 09:54 AGieslerExternal compute integration matrix
Microsoft Excel Spreadsheetxls IntegrationData.xls r3 r2 r1 manage 98.5 K 2010-11-19 - 09:56 AGieslerExternal data integration matrix (.xls)
Unknown file formatxlsx IntegrationData.xlsx r4 r3 r2 r1 manage 25.5 K 2010-11-19 - 10:30 AGieslerExternal data integration matrix
Microsoft Excel Spreadsheetxls IntegrationInfrastructure.xls r3 r2 r1 manage 109.5 K 2010-11-19 - 10:31 AGieslerExternal infrastructure integration matrix (xls)
Unknown file formatxlsx IntegrationInfrastructure.xlsx r5 r4 r3 r2 r1 manage 28.6 K 2010-11-19 - 10:34 AGieslerExternal infrastrucure integration matrix
Microsoft Excel Spreadsheetxls IntegrationMatrix.xls r4 r3 r2 r1 manage 59.6 K 2010-11-19 - 18:55 AGieslerExternal Total integration matrix (.xls)
Unknown file formatxlsx IntegrationMatrix.xlsx r4 r3 r2 r1 manage 55.9 K 2010-11-19 - 10:58 AGieslerExternal Total integration matrix
Microsoft Excel Spreadsheetxls IntegrationSecurity.xls r3 r2 r1 manage 102.0 K 2010-11-19 - 10:35 AGieslerExternal security integration matrix (.xls)
Unknown file formatxlsx IntegrationSecurity.xlsx r4 r3 r2 r1 manage 26.3 K 2010-11-19 - 10:41 AGieslerExternal security integration matrix
Microsoft Excel Spreadsheetxls IntegrationVerification.xls r1 manage 51.5 K 2010-11-05 - 10:53 AGieslerExternal Verification of the integration statuses (.xls)
Unknown file formatxlsx IntegrationVerification.xlsx r2 r1 manage 19.7 K 2010-11-05 - 11:06 AGieslerExternal Verification of the integration statuses
Microsoft Excel Spreadsheetxls InteropCompute.xls r2 r1 manage 111.0 K 2010-11-15 - 11:14 AGieslerExternal compute interoperability matrix (xls)
Unknown file formatxlsx InteropCompute.xlsx r3 r2 r1 manage 26.1 K 2010-11-15 - 11:14 AGieslerExternal compute interoperability matrix
Microsoft Excel Spreadsheetxls InteropData.xls r2 r1 manage 68.0 K 2010-11-15 - 11:14 AGieslerExternal data interoperability matrix (.xls)
Unknown file formatxlsx InteropData.xlsx r3 r2 r1 manage 19.8 K 2010-11-15 - 11:15 AGieslerExternal data interoperability matrix
Microsoft Excel Spreadsheetxls InteropInfrastructure.xls r2 r1 manage 87.5 K 2010-11-15 - 11:15 AGieslerExternal infrastructure interoperability matrix (.xls)
Unknown file formatxlsx InteropInfrastructure.xlsx r3 r2 r1 manage 25.3 K 2010-11-15 - 11:15 AGieslerExternal infrastrucure interoperability matrix
Microsoft Excel Spreadsheetxls InteropMatrix.xls r2 r1 manage 256.5 K 2010-11-15 - 11:19 AGieslerExternal Total interoperability matrix (.xls)
Unknown file formatxlsx InteropMatrix.xlsx r5 r4 r3 r2 r1 manage 64.2 K 2010-11-19 - 18:55 AGieslerExternal Total interoperability matrix
Unknown file formatxlsm InteropMatrixMakro.xlsm r11 r10 r9 r8 r7 manage 642.8 K 2010-11-19 - 19:04 AGieslerExternal Total Matrices with Makro
Microsoft Excel Spreadsheetxls InteropSecurity.xls r2 r1 manage 75.5 K 2010-11-15 - 11:16 AGieslerExternal security interoperability matrix (xls)
Unknown file formatxlsx InteropSecurity.xlsx r3 r2 r1 manage 22.7 K 2010-11-15 - 11:16 AGieslerExternal security interoperability matrix
Edit | Attach | Watch | Print version | History: r39 < r38 < r37 < r36 < r35 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r39 - 2011-05-06 - AGieslerExternal
 
    • 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