JRA1 Middleware Development, Evolution and Integration

Work Package Co-leaders: Balazs Konya (25%), Jon Kerr Nilsen (75%)

Work Package Tasks

Work Package Coordination

Compute

JRA1.2 Definition and Implementation of the Compute Area Work Plan

Data

JRA1.3 Definition and Implementation of the Data Area Work Plan (old page)

Security

JRA1.4 Definition and Implementation of the Security Area Work Plan

Infrastructure

JRA1.5 Definition and Implementation of the Infrastructure Area Work Plan

JRA1 Deliverables

Status Title Task Number Task Leader Due Date
DONE DJRA1.1.1 – Compute Area Work Plan and Status Report JRA1.2 Massimo Sgaravatto 3 (July 2010)
DONE DJRA1.2.1 – Data Area Work Plan and Status Report JRA1.3 Patrick Fuhrmann 3 (July 2010)
DONE DJRA1.3.1 – Security Area Work Plan and Status Report JRA1.4 John White 3 (July 2010)
DONE DJRA1.4.1 – Infrastructure Area Work Plan and Status Report JRA1.5 Laurence Field 3 (July 2010)
DONE DJRA1.1.2 - Compute Area Work Plan and Status Report JRA1.2 Marco Cecchi 12 (Apr 2011)
DONE DJRA1.2.2 - Data Area Work Plan and Status Report JRA1.3 Patrick Fuhrmann 12 (Apr 2011)
DONE DJRA1.3.2 – Security Area Work Plan and Status Report JRA1.4 John White 2 (Apr 2011)
DONE DJRA1.4.2 - Infrastructure Area Work Plan and Status Report JRA1.5 Laurence Field 12 (Apr 2011)
  DJRA1.1.3 - Compute Area Work Plan and Status Report JRA1.2 Marco Cecchi 24 (Apr 2012)
  DJRA1.2.3 - Data Area Work Plan and Status Report JRA1.3 Patrick Fuhrmann 24 (Apr 2012)
  DJRA1.3.3 - Security Area Work Plan and Status Report JRA1.4 John White 24 (Apr 2012)
  DJRA1.4.3 - Infrastructure Area Work Plan and Status Report JRA1.5 Laurence Field 24 (Apr 2012)
  DJRA1.1.4 - Compute Area Work Plan and Status Report JRA1.2 Marco Cecchi 36 (Apr 2013)
  DJRA1.2.4 - Data Area Work Plan and Status Report JRA1.3 Patrick Fuhrmann 36 (Apr 2013)
  DJRA1.3.4 - Security Area Work Plan and Status Report JRA1.4 John White 36 (Apr 2013)
  DJRA1.4.4 - Infrastructure Area Work Plan and Status Report JRA1.5 Laurence Field 36 (Apr 2013)

JRA1 Milestones

Status Title Task Number Task Leader Due Date
Yes / Done MJRA1.1 - Security Workshop JRA1.4 John White 2(Jun-10)
DONE MJRA1.13 - Agreement on common information exchange methods JRA1.5 Laurence Field 3(Jul-10)
DONE MJRA1.5 - Agreement on common security methods for data systems JRA1.3 Patrick Fuhrmann 5(Sep-10)
DONE MJRA1.2 - Agreement on common job submission and management methods JRA1.2 Massimo Sgaravatto 6(Oct-10)
Yes / Done MJRA1.9 - AAI requirements of DCIs JRA1.4 John White 7(Nov-10)
DONE MJRA1.14 - EMI Information exchange used in computing JRA1.5 Laurence Field 12(Apr-11)
DONE MJRA1.6 - File Catalogue common front-ends JRA1.3 Patrick Fuhrmann 15(Jul-11)
DONE MJRA1.10 - EMI Security Workshop JRA1.4 John White 17(Sep-11)
  MJRA1.3 - Successful implementation of the common job submission and management methods JRA1.2 Marco Cecchi 21 (Jan-12)
  MJRA1.11 - Easier end-user access capability to EMI components in place JRA1.4 John White 22(Feb-12)
  MJRA1.7 - First implementations of POSIX compliance and HTTP support JRA1.3 Patrick Fuhrmann 24(Apr-12)
  MJRA1.12 - Common Security Architecture Assessment JRA1.4 John White 24(Apr-12)
  MJRA1.15 - Service monitoring and management JRA1.5 Laurence Field 24(Apr-12)
  MJRA1.4 - Successful computational usage of emerging computing models JRA1.2 Marco Cecchi 30(Oct-12)
  MJRA1.8 - Full standard compliance and POSIX support JRA1.3 Patrick Fuhrmann 30(Oct-12)

JRA1 KPIs

Tools/Communication channels

Mailing lists

List name Description
emi-jra1 EMI JRA1 Work Package
emi-jra1-compute EMI JRA1 Compute Area
emi-jra1-data EMI JRA1 Data Area
emi-jra1-data-sar EMI JRA1 Data Area Storage Accounting
emi-jra1-sec EMI JRA1 Security
emi-jra1-infra EMI JRA1 Infrastructure Area

Trackers

Tracker Description
EMI Requirements Tracker This tracks incoming technical requirements on EMI and makes the basis for objectives in the technical development plan.
EMI Development Tracker Tracker containing all high-level objectives from the technical development plan and the corresponding PT-level tasks. All EMI development is tracked here.
EMI Releases Tracker When a development task is done, the product must be released before the task can be closed. When the PT is ready to release the product it must ask for an entry in the release tracker and make sure the URL to the development task is added to the list of RfCs. When the release tracker entry is closed with status 'Released' the corresponding development tracker entry can be closed.
Edit | Attach | Watch | Print version | History: r14 < r13 < r12 < r11 < r10 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r14 - 2012-02-08 - JonKerrNilsen
 
    • 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-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback