This page describes the requirements and the procedures that need to be describe in order to start that transition process.
Service hosting and management requirements and current status
A document with the description of the service and how the service operationally works should be redacted.
And example of the structure of the document and the aspects that should be described follows:
Introduction
Generic requirements
The only MDVPN SI instance is deployed on GN QUALAB virtual machine (dual core CPU, 4GB RAM, 36GB HDD, one network card).
Infrastructure hosting requirements
Hardware and network
The only MDVPN SI instance is deployed on GN QUALAB virtual machine (mdvpn-inventory.qalab.geant.net). MDVPN-SI is multitier system with software stack consisting of:
- CentOS Release 6.6 Final
- Apache HTTP server (Apache/2.2.15)
- Fildfly application server (Wildfly/8.1.0.Final) and Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
- Database management system (PostgreSQL server 8.4.20)
High availability - not required
Monitoring - desirable and should be defined
Addressing and naming - static IP address is desirable
System administration requirements
Operating system administration - highly desirable
Disaster recovery and backup - should be defined; daily database backups and weekly VM backups should be sufficient
Log retention
Accessibility of service instances - service instance accessibility is not critical
Operation procedures
Enrol of a new user - to be defined with MDVPN team
Deployment of new customer instances (if applicable)- N/A (there should be only one instance)
Updates of the service instances -
Key Performance indicators - not defined as MDVPN as a service does not have appropriate KPIs
Support
The following list is a complete example of what should be documented.
It might be that some of these points are not applicable to your service. For a more complete list of things that should be documented check the check list attached to this page.