When the transition process starts two main documents should be prepared by the development team:
- Infrastructure and Resources Requirements form to be filled and returned to the Operation team
- Service hosting and management requirements and current status.
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 TEMPLATE
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
...
...
...
Infrastructure hosting requirements
Hardware and network
...
...
...
- 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
...
Monitoring
...
...
Addressing and naming
...
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
...
Support
...
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.