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 Software Component Delivery"

From EGIWiki
Jump to navigation Jump to search
Line 26: Line 26:
<br>  
<br>  


= Initial activities - Joining UMD Release Team<br> =
= Initial activities - Joining UMD Release Team<br> =


To become included in [https://wiki.egi.eu/wiki/UMD_Release_Team UMD Release Team (URT)] Technology provider should provide following information:<br>  
To become included in [https://wiki.egi.eu/wiki/UMD_Release_Team UMD Release Team (URT)] Technology provider should provide following information:<br>  
Line 34: Line 34:
#Name and contact details of the Component Development Team Leader  
#Name and contact details of the Component Development Team Leader  
#Description of the Component/Purpose<br>
#Description of the Component/Purpose<br>
Please read: [[UMD Release Team#How_to_join_URT|How to join]]


<br>  
<br>  
Line 43: Line 45:
#Subscribe to the UMD Release team mailing list
#Subscribe to the UMD Release team mailing list


<br>  
<br>


= Ongoing activities<br>  =
= Ongoing activities<br>  =

Revision as of 10:13, 23 March 2015

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





EGI's UMD Provisioning activity governs and executes two main processes:

  1. Software Provisioning Process: That handles software delivery from software development teams, aka Technology Providers (TP), Quality Assurance and Reporting. 
  2. UMD Release Process: That collects tested Products per Platform and Architecture (PPAs) into UMD Releases


Of Technology Provider interest is the Software Provisioning Process, with its 3 steps:

  1. Software Delivery – Technology Providers submit new software releases
  2. Software Assessment – through Quality Assurance & Staged Rollout
  3. Reporting – inform TP about outcome of the software provisioning process


Small workflow diagram representing status of products through the Software Provisioning Process:

Software Provisioning Process.png



Initial activities - Joining UMD Release Team

To become included in UMD Release Team (URT) Technology provider should provide following information:

  1. Name of the Product team
  2. Contacts (support email address, web site address)
  3. Name and contact details of the Component Development Team Leader
  4. Description of the Component/Purpose

Please read: How to join


With the help of the EGI UMD Release Team (URT), the following steps need to be performed:

  1. Create GGUS Support Unit to receive and handle incidents (define level of quality of support)
  2. Agree on Technical Provider Underpinning Agreement (TP UA) with EGI.eu
  3. Subscribe to the UMD Release team mailing list


Ongoing activities

Once Technology Provider join UMD Release Team following activities should be performed each time new version of product has been released.

Software Deliver

Goal: Submitting new software releases


  1. Communicate information about new update
    • E-mail to URT team
    • Update the information on the URT meeting agendas
  2. Information needed for each update:
    • Product Name & Version
    • Release Notes as:
      • What’s New – bug fixes, new features
      • Installation & Configuration instructions – what needs to be done to correctly update the product (package, service) on production infrastructure
      • List of Packages to be updated
      • Location where the packages are available:


Software Assessment

Goal: Assessment through Quality Assurance & Staged Rollout

  1. Quality Assurance – through
  2. Quality Criteria definition – definition and updates of the Quality Criteria used in the Software Verification step
  3. Quality Criteria Verification
  4. Packages are pulled from the TP into UMD repos (unverified) and the Verification team starts he verification of the info provided by the TP, apply QC, general and specific defined for respective product
  5. A Verification Report is provided (in DocDB) for the Staged Rollout site
  6. TP are informed regarding issues discovered, workarounds needed – through GGUS
  7. Staged Rollout
  8. Successful verified products are deployed on Early Adopters sites for testing in a production environment before the inclusion in the UMD production repositories.
  9. Reports with the results of this testing phase are recorded in DocDB






Incident and Problem management

Goal: To restore normal/agreed service operations within the agreed time after the occurrence of an incident, and to investigate the root causes of (recurring) incidents in order to avoid future recurrence of incidents by resolving the underlying problem, or to ensure workarounds are available.

Incident and requests management

Support should be provided:

  • via the GGUS portal, which is the single point of contact for infrastructure users to access the EGI Service Desk.
  • (for incidents) According to declared level of quality of support (default: Medium) 
  • Support is provided in English
  • Support is available
    • from Monday to Friday
    • 8 h per day
  • All incidents and requests should be(assign to proper Support Unit) and prioritized according to suitable scheme.

Problems management

  1. In case of recurring incidents which cannot be solved by the Provider a GGUS ticket should be created to "Operations"  Support Unit. EGI Operations team will coordinate investigation of  the root causes of (recurring) incidents in order to avoid future recurrence of incidents. 
    • Any existing GGUS tickets which may help investigation should be marked as a child to the created ticket.

=== Planned maintenance windows or interruptions === TBD_NOT_CLEAR IF APPLICABLE TO TP/COMPONENTS

Planned maintenance should be

  • declared in GOCDB in a timely manner i.e. 24 hours before
  • with typical duration up to 24 hours otherwise needs to be justified

Unscheduled interruptions should be managed according to MAN04

Security incidents

All security incidents should be registered according to EGI_CSIRT:Incident_reporting

Monitoring

Provider is responsible for development, maintenance and support of the Component monitoring probes.

Availability and reliability threshold should be defined with EGI Operations team depending on criticality of the service.

Information Security management

Goal: to manage information security effectively through all activities performed to deliver and manage services, so that confidentiality, integrity and accessibility of relevant assets are preserved

The following rules for information security and data protection apply:
•    The Provider must define and abide by an information security and data protection policy related to the service being provided.
•    This must meet all requirements of any relevant EGI policies or procedures and also must be compliant with the relevant national legislation.

Customer relationship management

Goal: Establish and maintain a good relationship with customers receiving service

The Provider interacts with EGI.eu, primarily with OMB, the main customer of the operational tools.

Interactions between EGI.eu TPs are guaranteed through periodic phone conferences and face to face meetings (URT). A dedicated mailing list is available as well: urt-discuss@mailman.egi.eu

Interactions with customers are guaranteed through periodic OMB meetings and (if needed) dedicated Advisory Groups. The AG mandate is to help the Provider in requirement prioritization and releasing process of the Component. AG can provide forums to discuss the Component evolution that meets the expressed needs of the EGI community. It has representation from the all end users groups depending on the Component.