Page Comparison

Overview

We recommend to use VMs for NMS Prime. This will make life easier in the future, because:

Pros while using VMs:

• full backup possibility (snapshots)
• easy updates and backwards compatibility
• hardware independence
• more flexible while moving towards HA-architecture (High Availability) and Clustering

We use qemu KVM architecture with the virt-manager GUI.

Pros while using KVM:

• completely free / open source
• native linux kernel support
• large community
• fast, stable and worldwide tested

Recommended file format is *.qcow2. This file format will only allocate as much space as required on the real host.

Setting up the real host

We also use CentOS 7 on the real machines. This makes life easier, because we only need to know CentOS config style. Of cause you could use other Linux distribution on the real host.

Required packages:

cat << EOF > /etc/yum.repos.d/qemu-kvm-rhev.repo
[qemu-kvm-rhev]
name=oVirt rebuilds of qemu-kvm-rhev
baseurl=http://resources.ovirt.org/pub/ovirt-3.5/rpm/el7Server/
mirrorlist=http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-3.5-el7Server
enabled=1
skip_if_unavailable=1
gpgcheck=0
EOF

yum install qemu-kvm-rhev libvirt bridge-utils
# qemu-img is not needed

Start libvirt:

systemctl start libvirtd
systemctl enable libvirtd

Networking

We use bridge networking API. Things you need to do is:

1. real host: all IPs must run on the bridge interface and not on the real network
2. real host: assign the bridge device to your real network interface
3. VM: assign the VM to your new bridge device

Update your system

yum update -y