...
This page is holding information about requirements for service_nameRA21 Discovery operations, in terms of required infrastructure and resources. RESPONSIBLE: Information provided here is initially populated by the development team (during the transition phase), and revised based on the need or in a yearly service check by service_name Service Manager. |
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 | Group_1_distinguisher | Group_2_distinguisherBackend Site Metadata servers per site (at least 2 sites) | |
|---|---|---|---|
| Description of usage | Metadata aggregation, MDQ and JSON discovery processing | ||
| Number of VMs with same specification | 2 | ||
| Hardware requirements (CPU, RAM, disk space) | 2 vCPU, 16G, 20G disk | ||
| Network connection requirements |
| Public IPV4 | |
| IP addressing requirements (IPv4, IPv6, public route) | IPv4 or IPv6 or both - will be fronted by CDNs | ||
Naming requirements1 | md-[NN].[SITE].thiss.io |
| Other resource requirements | Group_1_distinguisher | thiss.io CDN | Elastic cloudGroup_2_distinguisher |
|---|---|---|---|
| Other requirement and its specifics | Multiple contracts for commercial CDNs - minimally fastly and cloudflare | A contract for an elastic cloud instance |
Infrastructure Hosting Requirements
Hosting requirements | Applying to Group_1_distinguisher Applying to Group_2_distinguisherBackend Site Metadata servers per site (at least 2 sites) | |
|---|---|---|
Availability | 247 | |
Backup (what, frequency, retention period) | none | |
Monitoring and alerting1 | handled by project | |
Measuring and Reporting2 | handled by project | |
Log retention3 | handled by project | |
Security policy for access and usage4 | Security groups (openstack or equivalent) or external FW |
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 Group_1_distinguisher Applying to Group_2_distinguisherBackend Site Metadata servers per site (at least 2 sites) | |
|---|---|---|
Operating system | Ubuntu | |
Applications1 | handled by project | |
| Maintenance hours2 | extended office hours | |
Configuration management3 | handled by project |
1 List 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 Group_1_distinguisher | Applying to Group_2_distinguisher |
|---|---|---|
Description | ||
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 |
Applying to Backend Site Metadata servers per site (at least 2 sites)