JRA1.1 - EMI-1 Development and Test Plans

EMI-1 Component CREAM

This service is a simple, lightweight service for job management operations at the Computing Element (CE) level.

  • EMI Compute Solution
  • Managed by compute area
  • Part of Product Team gLite Job Management [ Details ]
  • Component in ETICS : emi.cream-ce, emi.cream-ui [ Details ]
  • Supported Platforms : Scientific Linux [ 2010-10-29 ]

Integrated Components

  • BLAH 1.16 - Mandatory
    • Software Verification and Validation Plan : [ Details ]
  • CREAM 1.7 and CEMON 1.13 - Mandatory
    • Software Verification and Validation Plan : [ Details ]

Features (ready)

The features in development are considered to be part of the EMI 1 release

Features (required)

  • EMI technical objective Compute Area 1 : Glue 2.0 support in job management services and client tools (M12)
    • Addressed by developers
    • Problems related to information providers (partners did not deliver necessary providers)
    • Potential Risk: EMI 1 release of CREAM might not offer GLUE2 support
    • Investigation of solutions in progress

Features (early adopter)

  • EMI technical objective Cross Area 7 : Integration of the compute area services with the ARGUS authorization framework. (M24)
    • Addressed by developers

Features (planned and/or in development)

Integration of GLUE2 compliant information providers in the CREAM CE

  • Status: In development
  • Verification : Testing Strategy 1 - GLUE2 Information [ More Details ]
  • Milestone 1: 12/2010 - Development in beta quality present
  • Milestone 2: 01/2011 - Tests in place for continous internal JRA1 testings during 02/2011 (JRA1.7, JRA1.8)
  • Feature Deadline : 02/2011
  • Addressing EMI technical objective Compute Area 1 : Glue 2.0 support in job management services and client tools (M12)
  • Development Task Tracker : [ Details ]

Early Year 2 Features (planned and/or in development)

Integration of the CREAM CE with ARGUS authorization service. This will allow to have a single authorization mechanism within the CREAM CE

  • Status: In development
  • Milestone 1: 12/2010 - Development in beta quality present
  • Milestone 2: 01/2011 - Tests in place for continous internal JRA1 testings during 02/2011 (JRA1.7, JRA1.8)
  • Feature Deadline : 02/2011
  • Addressing EMI technical objective: Cross Area 7 : Integration of the compute area services with the ARGUS authorization framework. (M24)
  • Development Task Tracker : [ Details ]
  • Description: For both CREAM and CEMON: At configuration time; site admin can choose:Using ARGUS or existing authorization mechanism (gJAF)

Other Features (planned and/or in development)

Better support for multi-core allocations

  • Status: In development
  • Milestone 1: 12/2010 - Development in beta quality present
  • Milestone 2: 01/2011 - Tests in place for continous internal JRA1 testings during 02/2011 (JRA1.7, JRA1.8)
  • Feature Deadline : 02/2011
  • Addressing EMI Component Improvement
  • Development Task Tracker : [ Details ]
  • Description: support for JDL attributes WholeNodes, HostNumber, SMPGranularity, etc.

Feature Summary for EMI 1

GLUE2 publishing ARGUS Integration Better Multi-Core Allocations
CREAM P P P

P = Production Quality
beta = Pre-Production Quality

Status Update and Tracking

  • [2010-11-16] Morris : Synchronized with final version of DJRA1.1.1 (Compute Area Work Plan)
  • [2011-02-14] Morris : Added Links to Development Tracker Items
  • [2011-02-14] Morris: Made a note about problem related to missing information providers
  • [2011-02-14] Morris: Added feature - support for multi-core allocations
  • [2011-02-14] Morris: Requested status updates and documentation from Massimo/Marco for TO 1 and 7 work

Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r9 - 2011-02-14 - 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