Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI-InSPIRE:Plan 2014 Milestones"

From EGIWiki
Jump to navigation Jump to search
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Template:Op menubar}} {{Template:Inspire_reports_menubar}}  
{{EGI-Inspire_menubar}}
{{TOC_right}}
{{Template:Inspire_reports_menubar}}  
[[Category:EGI-inSPIRE SA1]]
{{TOC_right}}  
Specify the milestones for each quarter of the calendar year of 2014 and each SA1 task.
Specify the milestones for each quarter of the calendar year of 2014 and each SA1 task.


Line 18: Line 18:


* Q1
* Q1
**  
** Complete transition to post EMI/IGE scenario (deprecate bouncer for creating releases)
**  
**  
* Q2  
* Q2  
**  
** Migration task-force from UMD-2 to UMD-3.
**  
** Prepare transition for the end of SA1.3 activities simplifying whenever possible the software provisioning workflow. This will be achieved in collaboration with SA2.


= SA1.3 Interoperations =
= SA1.3 Interoperations =
Line 67: Line 67:
= SA1.7 support =
= SA1.7 support =
* Q1
* Q1
**  
** Continue software support along the established procedures
**  
** Revise the procedures according to expected changes (team participation and scope of work) after May 2014 and plan the transition.
* Q2  
* Q2  
**  
** Move to the revised procedures of software support gradually.
**  
**
 


= SA1.8 Availability, core services, documentation =
= SA1.8 Availability, core services, documentation =

Latest revision as of 18:55, 24 December 2014

EGI Inspire Main page


Inspire reports menu: Home SA1 weekly Reports SA1 Task QR Reports NGI QR Reports NGI QR User support Reports



Specify the milestones for each quarter of the calendar year of 2014 and each SA1 task.

SA1.2 Security

  • SVG plans
    • ...
  • Q1
  • Q2


SA1.3 Staged rollout

  • Q1
    • Complete transition to post EMI/IGE scenario (deprecate bouncer for creating releases)
  • Q2
    • Migration task-force from UMD-2 to UMD-3.
    • Prepare transition for the end of SA1.3 activities simplifying whenever possible the software provisioning workflow. This will be achieved in collaboration with SA2.

SA1.3 Interoperations

  • Q1
  • Q2


SA1.4 Tools

  • Q1
  • Q2

SA1.5 Accounting

Includes the operations of both the accounting portal and the APEL central repository

  • Q1
  • Q2


SA1.6 Helpdesk

  • Q1
    • Implementation of CMS specific portal and work flows
    • Introduce alternative authentication/authorization processes
    • Merge of GGUS and xGUS structures
  • Q2
    • Integration of operations portal
  • Q3
    • Implement interface for PRACE
  • Q4
    • Implement interface for XSEDE

SA1.7 support

  • Q1
    • Continue software support along the established procedures
    • Revise the procedures according to expected changes (team participation and scope of work) after May 2014 and plan the transition.
  • Q2
    • Move to the revised procedures of software support gradually.

SA1.8 Availability, core services, documentation

  • Q1
  • Q2