Page Comparison

A virtual server (commonly referred to as a "virtual machine," or "VM") is a group of files and other resources residing on one or more physical hosts and managed by a virtual machine monitor control program to appear as a stand-alone physical computer. A virtual machine, like a physical computer, runs an operating system and applications but unlike a physical computer, a VM only has access to a specific subset of the available physical resources. The virtual machine is defined by a set of specification and configuration files and is backed by the physical resources of a host. VMs allow a single set of physical hosts to run multiple instances of an operating system with the separate VM instances preventing applications from interfering with each other. If one application crashes, it does not affect the programs running in the other VMs.

Like a physical server, a VM can be used for a number of applications, including databases, business applications, network management, email, directory services, etc. The lifecycle outlined here applies to any virtual machine irrespective of its application or underlying control program.

Application

This lifecycle is typical for the following asset classes:

• Virtual Machines used as servers of all classes

Typical Lifecycle for Virtual Servers

Image RemovedImage Added

• Phase 1: Hardware VM Requested & Approved
  During this phase, a need for the server is determined and a decision is made to deploy a physical server VM rather than a VMphysical server. The specifications for the equipment VM are determined, quotes are obtained, approvals are collected from appropriate stakeholders, and a supplier is selected. In some cases, the "supplier" may be internal if, for example, an existing device can be repurposed or one is located in another departmentnew VM is requested from the appropriate OIT team.

• Phase 2: Order Placed & Equipment Acquired
  If the equipment is being acquired from a third party, an order is placed. If the equipment is being transferred internally within OIT or from another department, the required documentation is prepared and executed. This phase ends at the point where the hardware has been delivered and is ready for configuration.Phase 3: Hardware Tested & Installed
  The equipment VM Configured & Tested
  Once configured, the VM must be compared to the original specifications and acquisition documents to confirm that it matches the original requirements. Any required assembly and configuration is done during this phase . This includes including operating system software, application software and services, databases, network connections, user definition and security rules, and arrangements made for backups and disaster recovery. When all configuration steps are complete, a system test is performed on the server in place VM to ensure it meets all client requirements. This phase ends when the server VM is ready to be deployed into production.

• Phase 43: Equipment VM in Service & Maintained
  This phase represents the useful production life of the serverVM. Throughout this phase, the equipment VM will undergo periodic maintenance, upgrades, failures and fixes. At some point, the usefulness of the server VM will come to an end and plans need to be made to take it out of service. (Normally, these plans are made well in advance of the decommissioning of the serverVM.)

• Phase 5: Equipment VM Decommissioned
  When the equipment VM is no longer needed, either because it is being replaced by a newer system or it no longer serves any useful function, it is decommissioned. Decommissioning is usually a fairly complex process when the server VM is being replaced. If the services provided by the server VM are no longer needed then decommissioning can be as simple as powering the system off. Once offline, the server is either deinstalled and disposed of, or made available for other purposesdeinstalling the supporting configuration files. Plans for decommissioning are generally made well in advance of the actual deinstallation of the equipmentVM.

CI Ownership Matrix

Typical Relationships

Configuration items falling into this group of asset classes typically have one or more of the following relationships with other CIs: