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 2013 Milestones"

From EGIWiki
Jump to navigation Jump to search
Line 106: Line 106:
**
**
* Q4
* Q4
**  
* '''test resources'''. Finish the 2012 task.
**
 
* '''Unknown Issue'''. Nagios probes to generate alarms for the unknown issue.
 
*'''New Role'''. The past followup activities by means of GGUS tickets have shown not to result in any positive effect. We want to shift focus to addressing the persistent issues rather than the incidental ones.


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

Revision as of 15:28, 21 January 2013

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


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

SA1.2 Security

  • SVG plans
    • ...
  • Q1
  • Q2
  • Q3
  • Q4

SA1.3 Staged rollout

  • Q1
  • Q2
  • Q3
  • Q4

SA1.3 Interoperations

  • Q1
  • Q2
  • Q3
  • Q4

SA1.4 Tools

  • Q1
  • Q2
  • Q3
  • Q4

SA1.5 Accounting

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

  • Q1
  • Q2
  • Q3
  • Q4

SA1.6 Helpdesk

  • Q1
    • Restructuring VOMS synchronization
    • Finish fine tuning on Report Generator
  • Q2
    • Integration of operations portal
    • Interface for NGI_IBERGRID
  • Q3
    • Implementation of CMS specific portal and work flows
  • Q4
    • Introduce alternative authentication/authorization processes

SA1.7 support

  • Q1
  • Q2
  • Q3
  • Q4
  • test resources. Finish the 2012 task.
  • Unknown Issue. Nagios probes to generate alarms for the unknown issue.
  • New Role. The past followup activities by means of GGUS tickets have shown not to result in any positive effect. We want to shift focus to addressing the persistent issues rather than the incidental ones.

SA1.8 Availability, core services, documentation

  • Q1
  • Q2
  • Q3
  • Q4