This page is holding information about requirements for RA21 Discovery operations, in terms of required infrastructure and resources. RESPONSIBLE: Information provided in this page is initially provided by the development team, and revised based on the need or in a periodic service check in responsibility of the Service Owner. |
Infrastructure Requirements
Indicate requirements for servers, VMs or containers, grouping the requirements for multiple VMs in one column. Add as many columns as necessary, adding the sensible distinguisher for each group that will enable its later identification.
VM requirements | Backend Site Metadata servers per site (at least 4 sites). One more site for QA/Testing | ||
---|---|---|---|
Description of usage | MDQ | Metadata aggregation | HA Proxy |
Number of VMs with same specification | 2 | 1 | 1 |
Hardware requirements (CPU, RAM, disk space) | 2 vCPU, 16G, 20G disk | 2 vCPU, 16G, 20G disk | 2 vCPU, 16G, 20G disk |
Network connection requirements | Public IPV4 | Public IPV4 | Public IPV4 |
IP addressing requirements (IPv4, IPv6, public route) | IPv4 or IPv6 or both - will be fronted by CDNs | IPv4 or IPv6 or both - will be fronted by CDNs | IPv4 or IPv6 or both - will be fronted by CDNs |
Naming requirements1 | md-[NN].[SITE].[PROVIDER].[REGION].seamlessacccess.org* | a.[SITE].[PROVIDER].[REGION].seamlessacccess.org* | md.[SITE].[PROVIDER].[REGION].seamlessacccess.org* |
Other resource requirements | thiss.io CDN |
---|---|
Other requirement and its specifics | Multiple contracts for commercial CDNs - fastly for Europe provided by GEANT project |
Infrastructure Hosting Requirements
Hosting requirements | Applying to Backend Site Metadata servers per site (at least 4 sites) |
---|---|
Availability | 247 |
Backup (what, frequency, retention period) | none |
Monitoring and alerting1 | Nagios instance provided by SUNET for monitoring of the VMs Status.io for creating public status pages Pingdome.org for monitoring of webpages from various locations |
Measuring and Reporting2 | Usage can be measured by looking at traffic from CDN. |
Log retention3 | No logs are kept. |
Security policy for access and usage4 | Security groups (openstack or equivalent) or external FW. Rules will be defined. |
1As the minimum, network accessibility (outside of LAN) and hardware resource usage must be monitored. Indicate if some of these resources can be deemed critical so that adequate thresholds for alerting are implemented. Additional, indicate which specific applications uptime and operational health must be monitored and alerting implemented.
2Define what should be measured, how and with what period in order to deliver appropriate reporting relating to KPIs, usage, etc.
3Define which logs should be kept in order to have debugging data and data in case of misuse of the service, and how long logs should be retained.
4Define the policy for limiting access to the piece of the infrastructure and where it should be implemented (system level, network level etc.)
System and Application Maintenance Requirements
System and application requirements | Applying to Backend Site Metadata servers per site (at least 4 sites) |
---|---|
Operating system | Ubuntu |
Applications1 | defined in the OLA |
Maintenance hours2 | extended office hours |
Configuration management3 | defined in the OLA |
1List the applications installed on a system, and add corresponding licenses where applicable.
2 Define the appropriate time window for regular maintenance or give some recommendations.
3 Applies to automatised configuration management. Describe the system used.
Human Resources Requirements
Indicate requirements both in skills and manpower needed, for personnel needed for the DevOps team (that maintains service specific applications) and for L2 support.
Human resources requirements | Applying to Backend Site Metadata servers per site (at least 2 sites) |
---|---|
Description | SRE/NOC |
Manpower (in % of FTE) | 50% |
Recommended number of persons (considering backup) | 2 |
Skills | Same as InAcademia requirements |
Budget Requirements
Original Budget
Erik | Bergstöm | NORDUnet (SUNET) | berra@nordu.net | Task 1- RA21 | eduGAIN RA21 operations | 12 |
Maria | Haide | NORDUnet (SUNET) | mariah@nordu.net | |||
Fresia | Perez Arriagada | NORDUnet (SUNET) | fresia@sunet.se | Task 1- RA21 | eduGAIN RA21 product manager | 7.2 |
Elena | Rakhimova | KTH (SUNET) | elenara@kth.se | Task 1- RA21 | eduGAIN RA21 front developer | 7.2 |
Leif | Johansson | NORDUnet (SUNET) | leifj@sunet.se | Task 1- RA21 | eduGAIN RA21 | Using up the underspent of sunet - for first 5 months there was already 2.65 MM underspent |
Total budget:
- Manpower: 12 + 14,4 = 26.4MM
- CDN: 10Ke
Used till November 2019
CDN parked 10K
Used in first 10 months in 2019, hours: Fresia 80, Maria 84, Leif 136 = Total is 300h, which is 2MM
Left over: 26.4-2=24.4MM
- This leaves 5.4 MM, that is 37KE = 10KE goes to CDN and
Need budget, starting November 2019:
- For remaining time needed 50% FTE, over 38MM, that is 19MM.
- CDN, estimate at 20Ke
- pingdom 69e per month = starting January 2019 over 36 months total is 2484 eur
- status.io 79 dollar per month = starting January 2019 over 36 months is 2559 eur
- VMs, 200e per month ?? = starting January 2019 over 36 months is 7200 eur
New Budget, starting November 2019
Erik | Bergstöm | NORDUnet (SUNET) | berra@nordu.net | Task 1- Seamless Access | Seamless Access operations | 19MM (minus 5.4MM from original) |
Maria | Haide | mariah@nordu.net | ||||
Fresia | Perez Arriagada | fresia@sunet.se | Task 1- Seamless Access | eduGAIN RA21 product manager ?? | ||
Leif | Johansson | leifj@sunet.se | Task 1- Seamless Access | Seamless Access technical lead | ||
CDN | fastly.com | Task 1- Seamless Access | 20Ke( puls 10K from original) | |||
external monitoring | pingdom.com, status.io | Task 1- Seamless Access | 5.,1Ke (plus 5,1K from original) | |||
Virtual machines | AWS | Task 1- Seamless Access | 7,2Ke (plus 7,2K from original) |
Total minus: 5.4 MM that is 37Ke
Total plus: 10K + 5.1Ke + 7.2 Ke = 22.3 Ke
Total leftover: 14,7Ke