- IT Home
- How Tos
- IT Support
- Office Hours for Staff Support
- Office Hours for Student Support
Service Level Agreement
Name of Service
IRC-IT JIRA Webserver Virtual Server Service, short name "SJIRA01".
The service provides network access and hardware maintenance, as specified below, for a JIRA server.
The virtual server is provided running openSuSE operating system and is hosted on Jacobs' virtual infrastructure. Virtual environment maintenance is performed upon incident or request.
Air condition, power supply, and uninterruptible power supply is provided.
The virtual server has the IP address 126.96.36.199 and can be addressed by the name sjira01.jacobs-university.de.
Network access to the TCP listening ports for SSH, HTTP and HTTPS on the server is provided.
A network CNAME is set up for jira.jacobs-university.de, pointing to sjira01.jacobs-university.de.
SSH service and account credentials to access the service is provided.
Tomcat6 is installed and configured with SSL support. The certificate fingerprint is
de f2 e6 27 16 7d 73 1f c7 d4 44 36 87 1a 94 70 9c a4 c1 b0.
Jira 4.0 is installed and configured. Jira trusts http://teamwork.jacobs-university.de:8080/confluence as 'Trusted Application'. Jira stores the data in a MySQL database and on the local filesystem in /srv/jira.
MySQL is installed and configured for Jira. Daily dumps are stored in /srv/jira/data.
Users must be created localy, only the password check can be done via active directory.
The virtual server is equipped with:
- 2 CPU
- 1024 MB RAM
- 20 GB OS partitions
Jacobs University IRC-IT.
This SLA has been agreed upon on December 3rd, Day 2009.
Jacobs University IRC-IT: Torge Schmidt.
The Service User provides the server administrator.
The service is provided until end of December 2010.
The service is available 24/7. Technical support and incident response is provided as described below.
The server is located in VLAN 3 (public internet).
The server is accessible from the public internet and from Jacobs University's campus network.
ssh root access to the server is provided to the service customer and service users.
The production server is included in IRC-IT's monitoring system, see Key Performance Indicators below.
The service is 99% reliable, calculated per month.
Costs resulting from maintenance or changing hardware, software, or external service contracts are charged to the service customer's cost center.
The server provider is responsible for technical soundness of the server.
The Service User is responsible for the security of the system, employed services, and applications.
The system is pre-configured to install critical security operating system updates automatically (see Service Provider Responsibility).
The following items have to be provided by the Service Customer or Service User as a necessary pre-requisite for IRC-IT to fulfill this service agreement: ssh public keys for root access, a MySQL user and a HTML file in the web server root of the apache-virtual host sgsa.jacobs-university.de for service availability checking an have to be provided to the service provider.
Service Customer Responsibility
The Service Customer is responsible for any content stored on or published by the server. IRC and Jacobs University policies, German and International laws apply.
Service User Responsibility
The Service User prevents abuse of the system by enforcing adequate system, application and data security and integrity.
The Service User configures the system and any applications as necessary for the intended purpose.
Service Provider Responsibility
IRC-IT as service provider will update the operating system and standard applications. Updating is only done, after an update request is received from the Service User (see below).
Updating is done with standard operating system tools (i.e., yast) and includes only those applications included in yast.
The update request should include the list of packages to update. The update request should include a list of exemptions, if any.
The system is pre-configured to install critical security operating system updates automatically.
Backup and Restore
The Service User provides consistent database exports/dumps to the file system, to the directory /srv/jira/data/.
The content of the following directories is backuped once per day each day and retained for 30 days:
Directories in Backup
Restoring data from backup should follow the procedure for incident response. Data will be restored to the original directories, unless requested different.
In case of system breakdown, the Service Provider provides a clean opering system installation. In addition, the last file system copy of the mentioned directories is recovered. The Service User restores all application(s) to a running and available instance. The Service User recreates the server configuration, the application, the database, and data files with the restored data.
Additional VBC Full backups are performed once a week and are stored for 20 days or at least 3 complete backups.
Service support can be reached by employing the Service Desk for Faculty and Staff contact channels.
Incident response is available during business hours.
Configuration and extension requests, and other inquiries should follow the procedures and contact channels for Service Desk for Faculty and Staff.
Incidents include only failures due to defects to the extent of standard installation software as defined this agreement. Incidents do not include failures of additional components or software or applications maintained by the Service User or Service Customer.
Requests and inquiries should follow the procedures and contact channels for Service Desk for Faculty and Staff.
Key Performance Indicators
Monthly availability numbers of the SSH, HTTP, HTTPS, MySQL services as reported by IRC-IT's monitoring system.
Fixing issues with the system, the web server, or the application is the responsibility of the Service User.
Live System Status
For informational purposes and system mangement by the Service Customer, the following links to live system monitoring can be used.
The live status of the server can be seen at this external page.