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 Marketplace Services Availability and Continuity Plan"
Jump to navigation
Jump to search
| Line 53: | Line 53: | ||
| 1 | | 1 | ||
| Service unavailable / loss of data due to hardware failure | | Service unavailable / loss of data due to hardware failure | ||
| | | MP user GUI, user database, service database, order database | ||
| All services are running on virtual machines. In case of hardware failure of the host machine the virtual machine can be re-instantiated in another hypervisor in the private cloud. Daily backups of the service including database data. | | All services are running on virtual machines. In case of hardware failure of the host machine the virtual machine can be re-instantiated in another hypervisor in the private cloud. Daily backups of the service including database data. | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| Line 61: | Line 61: | ||
| 2 | | 2 | ||
| Service unavailable / loss of data due to software failure | | Service unavailable / loss of data due to software failure | ||
| | | MP user GUI, user database, service database, order database | ||
| Restoring of the codebase via internal source code repositories | | Restoring of the codebase via internal source code repositories | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| Line 69: | Line 69: | ||
| 3 | | 3 | ||
| service unavailable / loss of data due to human error | | service unavailable / loss of data due to human error | ||
| | | MP user GUI, user database, service database, order database | ||
| Restoring of the codebase via internal source code repositories and data from the backup service | | Restoring of the codebase via internal source code repositories and data from the backup service | ||
| style="background: yellow"| Medium | | style="background: yellow"| Medium | ||
| Line 77: | Line 77: | ||
| 4 | | 4 | ||
| 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) | ||
| | | MP user GUI | ||
| University of Athens which acts as an ISP to IASA, has redundant network connectivity. | | University of Athens which acts as an ISP to IASA, has redundant network connectivity. | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| Line 85: | Line 85: | ||
| 5 | | 5 | ||
| Unavailability of key technical and support staff (holidays period, sickness, ...) | | Unavailability of key technical and support staff (holidays period, sickness, ...) | ||
| | | - | ||
| AppDB technical/support staff try not to be on leave at the same time. Even if that happened (typically during August), there is always MOD (manager on duty) and secure remote access is always available. | | AppDB technical/support staff try not to be on leave at the same time. Even if that happened (typically during August), there is always MOD (manager on duty) and secure remote access is always available. | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| Line 93: | Line 93: | ||
| 6 | | 6 | ||
| 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 | ||
| | | MP user GUI, user database, service database, order database | ||
| All virtual machines and data are backuped in a daily basis. In addition critical components like, backup servers, common storage, network devices etc. are supported by a UPS and power generator. | | All virtual machines and data are backuped in a daily basis. In addition critical components like, backup servers, common storage, network devices etc. are supported by a UPS and power generator. | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| Line 101: | Line 101: | ||
| 7 | | 7 | ||
| 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. | ||
| | | MP user GUI, user database, service database, order database | ||
| All virtual machines, data and code are backuped in a daily basis. | | All virtual machines, data and code are backuped in a daily basis. | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| Line 109: | Line 109: | ||
| 8 | | 8 | ||
| (D)DOS attack. The service is unavailable because of a coordinated DDOS. | | (D)DOS attack. The service is unavailable because of a coordinated DDOS. | ||
| | | MP user GUI | ||
| Local network team provides monitoring and protection for DOS attacks, firewall can limit impact of the DDoS | | Local network team provides monitoring and protection for DOS attacks, firewall can limit impact of the DDoS | ||
| style="background: green"| Low | | style="background: green"| Low | ||
Revision as of 15:28, 24 July 2019
| 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
Introduction
This page reports on the Availability and Continuity Plan for the EGI Marketplace Services and it is the result of the risks assessment conducted for this service: a series of risks and treats 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 | |
|---|---|---|
| Risks assessment | 2019-07-24 | |
| Av/Co plan and test |
Performances
The performances reports in terms of Availability and Reliability are produced by ARGO on an almost real time basis and they are also periodically collected into the Documentation Database.
In the OLA it was agreed the following performances targets, on a monthly basis:
- Availability: 95%
- Reliability 95%
Over the past years, the AppDB 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 | MP user GUI, user database, service database, order database | All services are running on virtual machines. In case of hardware failure of the host machine the virtual machine can be re-instantiated in another hypervisor in the private cloud. Daily backups of the service including database data. | Low | up to 8 hours (1 working day) | the measures already in place are considered satisfactory and risk level is acceptable |
| 2 | Service unavailable / loss of data due to software failure | MP user GUI, user database, service database, order database | Restoring of the codebase via internal source code repositories | Low | up to 8 hours (1 working day) | the measures already in place are considered satisfactory and risk level is acceptable |
| 3 | service unavailable / loss of data due to human error | MP user GUI, user database, service database, order database | Restoring of the codebase via internal source code repositories and data from the backup service | Medium | up to 4 hours (half working day) | 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) | MP user GUI | University of Athens which acts as an ISP to IASA, has redundant network connectivity. | Low | up to 4 hours (half working day) | the measures already in place are considered satisfactory and risk level is acceptable |
| 5 | Unavailability of key technical and support staff (holidays period, sickness, ...) | - | AppDB technical/support staff try not to be on leave at the same time. Even if that happened (typically during August), there is always MOD (manager on duty) and secure remote access is always available. | Low | 1 or more working days | 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 | MP user GUI, user database, service database, order database | All virtual machines and data are backuped in a daily basis. In addition critical components like, backup servers, common storage, network devices etc. are supported by a UPS and power generator. | Low | 1 or more working days | 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. | MP user GUI, user database, service database, order database | All virtual machines, data and code are backuped in a daily basis. | Low | up to 8 hours (1 working day) | 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. | MP user GUI | Local network team provides monitoring and protection for DOS attacks, firewall can limit impact of the DDoS | Low | up to 4 hours (half working day) | 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 is supposed to have been disrupted and needs to be reinstalled from scratch. The last backup of the data will be used for restoring the service, verifying how much information will be lost, and the time spent will be measured.
Performing this test will be useful to spot any issue in the recovery procedures of the service.
Test details and outcome
Revision History
| Version | Authors | Date | Comments |
|---|---|---|---|
| Alessandro Paolini | 2019-07-24 | first draft, discussing with the provider | |