Versions Compared

Old Version 1

changes.mady.by.user Marina Adomeit

Saved on

compared with

New Version 2

changes.mady.by.user Stefan Winter

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

High-Level Architecture Description


View file
nameeduroam Managed SP UML Diagram.vpd(1).svg
height250

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.

...

     
VM requirementsGroup_1_distinguisherGroup_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 requirements1

 



1 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 requirementsGroup_1_distinguisherGroup_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 alerting1

 

Measuring and Reporting2

 

Log retention3

 



Security policy for access and usage4

 

 




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 Group_1_distinguisher

Applying to Group_2_distinguisher

Operating system

 



Applications1

 



Maintenance hours2 

Configuration management3

  

 




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

 



Manpower (in % of FTE)

 



Recommended number of persons (considering backup)  

Skills