General Information

LRZ-vSphere virtual servers can be used to operate specialized services that the LRZ does not offer directly. These are offered in the "Attended Hosting" operating model. This means that the LRZ installs a supported version of Linux or Windows and provides updates. Before end of support, whole installation must be upgraded or replaced by a new version. The customer receives full administrative access.
These "Managed Servers" are housed on LRZ's own hardware in air-conditioned security areas of the data center with uninterruptible power supply, access protection systems, fire detection and extinguishing systems as well as 24-hour surveillance.

Description of services

• Setup of the virtual server in the LRZ-vSphere within the defined service parameters according to the customer's requirements
• Operational provision of the desired operating system

• Network connection with its own IP address

  • By default, virtual servers are operated either in one of two subnets

    • MWN-wide: private IP address that is available within the Munich Science Network

    • Worldwide: public IP address 

  • For configurations with several servers, it is optionally possible (at an additional cost) to provide a separate VLAN with its own subnet and firewall
  • Provisioning of a technical DNS entry in the srv.mwn.de zone. The customer can use this freely, but the creation of certificates in this zone is not possible. Own DNS zones must be used for this purpose.
• Operation and troubleshooting of the virtual server
  • Faults are rectified according to the "best effort" principle, i.e. The aim is to resolve the problem quickly, but a fixed solution time cannot be guaranteed.
• Automatic security updates for operating system components
• Snapshots (backup) of the entire disks of the virtual machine (VM)
  • every 24 hours and saving for a period of 14 days
  • every 4 hours and saving for a period of 24 hours
  • Restoration of the respective disks possible
• Optional Veeam backup of the entire disks of the virtual machine (VM)
  
  • every 24 hours and saving for a period of 90 days
  • Restoration of the respective hard disks or individual files possible
• Administrative access for customers
  
  • The customer receives an ID with administrator rights on the virtual server
  • The customer receives access to a management platform for the following administrative activities
    
    • Remote maintenance of the installed operating system via the VM console (Only to be used as “emergency access”!)
    • (Re) start and stop the VMs
• Update of operating system before end of support, i.e. upgrade of version or, if not possible, replace operating system by a new virtual server

Administrative requirements

The use of virtual servers requires knowledge available at all times for installing, configuring and regularly updating the desired services or service software. Only if software of the so-called standard installation sources is being used, regular automatic updating is performed by the LRZ. If this is not possible or desired, the service administrator, i.e. customer, is responsible for regular software updates by himself. Security updates must be applied within 7 days.

An upgrade to the next higher version will be done before the operating system support period expires. If the update of the existing VM is no longer supported, the LRZ will provide a new virtual server with an up-to-date operating system after consultation. After an appropriate migration phase, the obsolete server is shut down. If possible, the OS upgrade should be done by customer based on the documentation provided by the LRZ. The customer must plan for sufficient experience to reactivate the desired services when the operating system is renewed.

Please also note the above linked or in the left column available FAQs zu virtuellen Maschinen am LRZ, especially both parts: Was ist bei Linux-VMs zu beachten? and Was ist bei Windows-VMs zu beachten? 

Available operating systems

Configuration limits

Prices

The cost rates differ according to user class. Class 1 includes TUM, LMU and BAdW, class 2 includes all other state Bavarian universities. Class 3 is made up of all state institutions with a scientific mandate in the StMWFK division – see also DLK, chap. 14 user classes and service matrix.

With a valid LRZ account you can view the current prices with login to the VM Customer Center (VMCC). By means of 'VM Calculator' the calculation of sample configurations is possible.

Project binding

To manage and bill the fee-based service, you need to be bound by a so-called LRZ project with a billing address. The activation of a new LRZ project is described as option 1. If you already have an LRZ project, for example to use the LRZ service "Backup and Archive", you can use this for your purpose; see option 2.

• Option 1: If you do not yet have a (suitable) LRZ project, a corresponding application must be made by the chair holder or the institute management.
  The LRZ service "Managed Server" must be checked in the project application, called "Antrag auf ein LRZ-Projekt", which can be downloaded from this site. The completed project application will be sent by mail, by e-mail or via LRZ Servicedesk to the LRZ supervisor responsible for your facility.
  
  
• Option 2: With an existing project, the project leader or Master-User must apply for a permission for the "LRZ-vSphere", formerly "VM-Management-Portal". 
  This is done in the IDM portal by opening the "[ Permissions/Quotas ]" section in the respective project. In the "Number of permissions:" table, the "LRZ-vSphere" row is also listed. Here, a 1 is entered in the right cell, i.e. in the "requested:" column. Alternatively, the free text field at the bottom of the page can be used to enter an individual request text to the LRZ advisor responsible for the project. Click on the "Send E-mail ..." button to submit the request.

Result: As soon as the responsible LRZ supervisor initiates the project with option 1 and has set up the permission for the LRZ-vSphere for both options the project leader and Master-User are authorized to order and manage VMs.

The Master-User manages the access authorizations to the LRZ-vSphere via a SIM group (IFS_<project name>) assigned to the project, which can be edited via the IDM-Portal 2. For more information, see the article LRZ-vSphere Berechtigungen – Anleitung für Master User.

Service requests

For service requests regarding "Managed Server" use the following link, please:

This will take you to the "Selfservice area". Please log in there with your Master-User account and password and describe your request in the "Details" field. By clicking on the blue "Save" button, your request will be sent.

Note: By using the LRZ Servicedesk, all requests are documented and can be traced later in the event of queries, e.g. about billing details. All other communication channels - telephone, e-mail, etc. - are not suitable!

VM order

If the above-mentioned project binding is given, the Master-User can order the desired Windows and/or Linux VMs by logging into the VM Customer Center (VMCC) and entering the necessary and optional data. At the end of the ordering process, there is an 'Order New VM' button for automatic data transfer to the LRZ Servicedesk.

Note: So-called "Unattended VMs" are not supported.

VM change

A project leader or Master-User is authorized to request adjustments, i.e. more or less resources of an existing VM. To do this, please use the LRZ Servicedesk. The naming of the respective VM host name is important. Subsequently, it is sufficient to enter the desired information..

VM deletion

A project leader or Master-User is authorized to request deletion of VMs. If you no longer need a VM, again use the the LRZ Servicedesk, please. Please inform us of the associated VM host name. We will then take the VM out of service and stop calculating the resources used from the day of your notification.

Note: Please keep this point in mind already when ordering the VM. Without official deprovisioning, services will be billed even if they are no longer used.