Versions Compared

Old Version 10

changes.mady.by.user Marina Adomeit

Saved on

compared with

New Version Current

changes.mady.by.user Marina Adomeit

Saved on

Key

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

...

1 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.

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

Budget Requirements

Original Budget

Erik  Bergstöm NORDUnet (SUNET)berra@nordu.netTask 1- RA21eduGAIN RA21 operations 12
Maria  HaideNORDUnet (SUNET)mariah@nordu.net
FresiaPerez ArriagadaNORDUnet (SUNET)fresia@sunet.seTask 1- RA21eduGAIN RA21 product manager 7.2
Elena 

Rakhimova

KTH

(SUNET)

elenara@kth.seTask 1- RA21eduGAIN RA21 front developer 7.2
Leif JohanssonNORDUnet (SUNET)leifj@sunet.seTask 1- RA21eduGAIN 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, 125e per VM (Look at calculation below) = 124x8= 1000e per month, starting January 2019 over 36 months is 36000 eur

    VM cost: https://aws.amazon.com/ec2/pricing/on-demand/Monthly price

    		CPU
    		MemoryDiskPrice in dollar, per hour
    r5.large21016 GiBEBS Only $                                0,15 $           113,09







    Disc cost https://aws.amazon.com/ebs/pricing/


    		Price in dollar, GB-month of provisioned storage
    General Purpose SSD (gp2) Volumes $                                0,12  $               2,38



















    		Total in $ $           115,47





    		Total in euro €           103,92












    		Total in euro with tax 20% €           124,71


New Budget, starting November 2019

Erik  Bergstöm SUNETberra@sunet.se Task 1- Seamless AccessSeamless Access operations 0.5 FTE in total19MM (minus 5.4MM from original)
Maria  Haidermariah@sunet.se 
Leif JohanssonSUNETleifj@sunet.seTask 1- Seamless AccessSeamless Access technical lead ask leif
CDNfastly.com
Task 1- Seamless Access
20Ke( puls 10K from original)
external monitoringpingdom.com, status.io
Task 1- Seamless Access
5,1Ke (plus 5,1K from original)
Virtual machines AWS
Task 1- Seamless Access
36Ke (plus 36K from original)


Total minus: 5.4 MM that is 37Ke

Total plus: 10K + 5.1Ke + 36 Ke = 51.1 Ke 

We are missing 14Ke.