You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

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 requirementsBackend Site Metadata servers per site (at least 4 sites). One more site for QA/Testing
Description of usageMDQ Metadata aggregationHA Proxy
Number of VMs with same specification211
Hardware requirements (CPU, RAM, disk space)2 vCPU, 16G, 20G disk2 vCPU, 16G, 20G disk2 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*
Applicable if DNS records maintenance is required (naming scheme and type of records)
*QA/Test may have different naming scheme under thiss.io

Indicate other service specific resource requirements. Add as many columns as necessary, adding the sensible distinguisher for each group that will enable its later identification.
Other resource requirementsthiss.io CDN
Other requirement and its specifics Multiple contracts for commercial CDNs - fastly for Europe provided by GEANT project

Infrastructure Hosting Requirements

Indicate requirements for infrastructure hosting, scoping by the above indicated infrastructure elements as necessary, or introducing the new ones (when hosting black-box components) . 


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

Indicate requirements for system and application maintenance, scoping by the indicated infrastructure elements, as necessary. 


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 hours2extended office hours

Configuration management3

defined in the OLA

1 List the applications installed on a system, and add corresponding licenses where applicable.

Define the appropriate time window for regular maintenance or give some recommendations.

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)
SkillsSame as InAcademia requirements 




  • No labels