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 "Service for AAI: PERUN Availability and Continuity plan"
| Line 62: | Line 62: | ||
| Service unavailable / loss of data due to hardware failure | | Service unavailable / loss of data due to hardware failure | ||
| database, GUI, provisioning engine | | database, GUI, provisioning engine | ||
| All | | All components and host machines are regularly backed-up on OS and application level. Host is running in redundant virtual environment. | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| In case an instance must be instantiated from backups can take up to two-three working hours. | | In case an instance must be instantiated from backups can take up to two-three working hours. | ||
| Line 71: | Line 71: | ||
| Service unavailable / loss of data due to software failure | | Service unavailable / loss of data due to software failure | ||
| database, GUI, provisioning engine | | database, GUI, provisioning engine | ||
| | | All components and host machines are regularly backed-up on OS and application level. | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| One to two working hours | | One to two working hours | ||
| Line 79: | Line 79: | ||
| service unavailable / loss of data due to human error | | service unavailable / loss of data due to human error | ||
| database, GUI, provisioning engine, LDAP | | database, GUI, provisioning engine, LDAP | ||
| | | All components and host machines are regularly backed-up on OS and application level. Only trained personel has an access to the machines. | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| Two to Three working hours. | | Two to Three working hours. | ||
| Line 87: | Line 87: | ||
| service unavailable for network failure (Network outage with causes external of the site) | | service unavailable for network failure (Network outage with causes external of the site) | ||
| GUI, LDAP | | GUI, LDAP | ||
| | | Data centers has redundant network connections and LDAP servers are located in two different data centers. | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| Close to zero, less than one hour. | | Close to zero, less than one hour. | ||
| Line 95: | Line 95: | ||
| Unavailability of key technical and support staff (holidays period, sickness, ...) | | Unavailability of key technical and support staff (holidays period, sickness, ...) | ||
| database, GUI, provisioning engine, LDAP | | database, GUI, provisioning engine, LDAP | ||
| | | At least one person from the core team (5 team members) is still available. | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| Within the OLA targets for operational actions | | Within the OLA targets for operational actions | ||
| Line 104: | Line 104: | ||
| Major disruption in the data centre. Fire, flood or electric failure for example | | Major disruption in the data centre. Fire, flood or electric failure for example | ||
| database, GUI, provisioning engine | | database, GUI, provisioning engine | ||
| | | All components and host machines are regularly backed-up on OS and application level. Machines are located in well maintained and secured data centres. LDAP is located in two different data centres. | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| 1-2 weeks, the time to deploy recover operational status at CESGA or the service to another resource centre partner of the NGI | | 1-2 weeks, the time to deploy recover operational status at CESGA or the service to another resource centre partner of the NGI | ||
| Line 112: | Line 112: | ||
| Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored. | | Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored. | ||
| database, GUI, engine, LDAP | | database, GUI, engine, LDAP | ||
| | | All the components has network security monitoring in place and is under CSIRT team supervision. All the components are backed-up in backup system which cannot be accessible from host machine. Perun software and its components are regularly checked by penetration testing. | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| 1-2 work hours. In case new host certificates are required, up to 2 days. | | 1-2 work hours. In case new host certificates are required, up to 2 days. | ||
| Line 120: | Line 120: | ||
| (D)DOS attack. The service is unavailable because of a coordinated DDOS. | | (D)DOS attack. The service is unavailable because of a coordinated DDOS. | ||
| GUI, LDAP | | GUI, LDAP | ||
| | | Network monitoring is in place and active network elemetns deployed at CESNET network are able to lower the risk of DDOS attacks. | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| | | | ||
| the measures already in place are considered satisfactory and risk level is acceptable | | the measures already in place are considered satisfactory and risk level is acceptable | ||
|} | |} | ||
Revision as of 11:34, 7 May 2018
| Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
| Documentation menu: | Home • | Manuals • | Procedures • | Training • | Other • | Contact ► | For: | VO managers • | Administrators |
Back to main page: Services Availability Continuity Plans
work in progress
Service Availability and continuty plan structure
- Performances (A/R targets agreed in the OLA, comment about the past behaviour and any particular issue)
- summary of the risks assessment
- Av.Co. tests and results
Introduction
This page reports on the Availability and Continuity Plan for Perun and it is the result of the risk assessment conducted for this service: a series of risks and threats has been identified and analysed, along with the correspondent countermeasures currently in place. Whenever a countermeasure is not considered satisfactory for either avoiding or reducing the likelihood of the occurrence of a risk, or its impact, it is agreed with the service provider a new treatment for improving the availability and continuity of the service. The process is concluded with an availability and continuity test.
| Last | Next | |
|---|---|---|
| Risk assessment | 2018-05-05 | 2019 May |
| Av/Co plan and test | in progress | -- |
Performances
The performances reports in terms of Availability and Reliability are produced by ARGO on an almost real time basis and they are also collected every 6 months into the Documentation Database (last period July 2017 - December 2017.
In the OLA it was agreed the following performances targets, on a monthly basis:
- Availability: 99%
- Reliability 99%
Over the past years, PERUN hadn't particular Av/Co issues highlighted by the performances that need to be further investigated.
Risks assessment and management
For more details, please look at the google spreadsheet. We will report here a summary of the assessment.
Risks analysis
| Risk id | Risk description | Affected components | Established measures | Risk level | Expected duration of downtime / time for recovery | Comment |
|---|---|---|---|---|---|---|
| 1 | Service unavailable / loss of data due to hardware failure | database, GUI, provisioning engine | All components and host machines are regularly backed-up on OS and application level. Host is running in redundant virtual environment. | Low | In case an instance must be instantiated from backups can take up to two-three working hours.
In case latest backups are not available some data must be re-generate from the central accounting repositories and this may take up to two hours. |
the measures already in place are considered satisfactory and risk level is acceptable |
| 2 | Service unavailable / loss of data due to software failure | database, GUI, provisioning engine | All components and host machines are regularly backed-up on OS and application level. | Low | One to two working hours | the measures already in place are considered satisfactory and risk level is acceptable |
| 3 | service unavailable / loss of data due to human error | database, GUI, provisioning engine, LDAP | All components and host machines are regularly backed-up on OS and application level. Only trained personel has an access to the machines. | Low | Two to Three working hours. | the measures already in place are considered satisfactory and risk level is acceptable |
| 4 | service unavailable for network failure (Network outage with causes external of the site) | GUI, LDAP | Data centers has redundant network connections and LDAP servers are located in two different data centers. | Low | Close to zero, less than one hour. | the measures already in place are considered satisfactory and risk level is acceptable |
| 5 | Unavailability of key technical and support staff (holidays period, sickness, ...) | database, GUI, provisioning engine, LDAP | At least one person from the core team (5 team members) is still available. | Low | Within the OLA targets for operational actions
Longer periods in case of bugs or maintenance (one week) because not all the personnel can develop patches to the code. |
the measures already in place are considered satisfactory and risk level is acceptable |
| 6 | Major disruption in the data centre. Fire, flood or electric failure for example | database, GUI, provisioning engine | All components and host machines are regularly backed-up on OS and application level. Machines are located in well maintained and secured data centres. LDAP is located in two different data centres. | Low | 1-2 weeks, the time to deploy recover operational status at CESGA or the service to another resource centre partner of the NGI | the measures already in place are considered satisfactory and risk level is acceptable |
| 7 | Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored. | database, GUI, engine, LDAP | All the components has network security monitoring in place and is under CSIRT team supervision. All the components are backed-up in backup system which cannot be accessible from host machine. Perun software and its components are regularly checked by penetration testing. | Low | 1-2 work hours. In case new host certificates are required, up to 2 days. | the measures already in place are considered satisfactory and risk level is acceptable |
| 8 | (D)DOS attack. The service is unavailable because of a coordinated DDOS. | GUI, LDAP | Network monitoring is in place and active network elemetns deployed at CESNET network are able to lower the risk of DDOS attacks. | Low | the measures already in place are considered satisfactory and risk level is acceptable |
Outcome
The level of all the identified risks is acceptable and the countermeasures already adopted are considered satisfactory
Availability and Continuity test
The proposed A/C test will focus on a recovery scenario: the service has been disrupted and needs to be reinstalled from scratch. The time spent for restoring the service will be measured, using the last backup of the data stored in it (how much information would be lost?)(risks 1,2, and 6?)(how many other operational tool would be affected?).
Performing this test will be useful to spot any issue in the recovery procedures of the service.
Revision History
| Version | Authors | Date | Comments |
|---|---|---|---|
| Alessandro Paolini | 2018-05-07 | first draft, discussing with the provider | |