eduroam managed SP Operational Requirements

High-Level Architecture Description

eduroam Managed SP UML Diagram.vpd(1).svg

This page is holding information about requirements for service_name 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_distinguisher
Description of usage
Number of VMs with same specification
Hardware requirements (CPU, RAM, disk space)
Network connection requirements
IP addressing requirements (IPv4, IPv6, public route)
Naming requirements¹

^₁Applicable if DNS records maintenance is required (naming scheme and type of records)

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 requirements	Group_1_distinguisher	Group_2_distinguisher
Other requirement and its specifics

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 Group_1_distinguisher	Applying to Group_2_distinguisher
Availability
Backup (what, frequency, retention period)
Monitoring and alerting¹
Measuring and Reporting²
Log retention³
Security policy for access and usage⁴

¹As 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.

²Define what should be measured, how and with what period in order to deliver appropriate reporting relating to KPIs, usage, etc.

³Define 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.

⁴Define 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 Group_1_distinguisher	Applying to Group_2_distinguisher
Operating system
Applications¹
Maintenance hours²
Configuration management³

¹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 Group_1_distinguisher	Applying to Group_2_distinguisher
Description
Manpower (in % of FTE)
Recommended number of persons (considering backup)
Skills

Page tree