oVirt

Introduction

With the beginning of Next generation of IT, the Cloud is taken a higher place in the IT world. Implementing a cloud is simply laying on virtualization of resource pools over network. It is typically a combination of virtualization and data centers. Pool is constituted with servers, storages, network and etc.

The resources are shared according to the client requirements as applications or services and other requirements to the clients as on demand over network with minimal management effort. Elasticity, flexibility, easy to manage and allocate resources as client pays are some advantages of deploying a cloud. All the operations are done through network. Costs are cut off than fully hardware services by using a cloud. Most of the cloud platforms are open source and they can be deployed and manageable for the requirement, clients meet, even as private, public and hybrid clouds for an organization. Open source software’s typically do similar things, with different installation methods and provides different features. And the service can be accessed through network even using mobile phones, tablets and all accessible devices through network.

Ovirt is an open source, virtualization manageable platform, founded Red Hat. As a community project, centralized management, computing, storages, networking can be done on a web based user interface which provides cloud computing features. It was provides the services as an Infrastructure as a service. oVirt is available in many languages since it has a huge community, and has Apache license 2.0. oVirt virtualization platform is consisted with ovirt engine which stores the data in PostgreSQL database and oVirt node which
is a server with KVM enabled.

Method

A cloud, oVirt was deployed for testing the requirements. oVirt Engine,oVirt nodes and Gluster storage were deployed on three nodes where CentOS 7 was installed. As minimum system requirements for oVirt engine are, a dual core CPU, 25 GB of locally accessible, writable, disk space, 4GB of available system
RAM if data Warehouse is not installed and if memory is not being consumed by existing processes, and 1 Network Interface Card(NIC) with bandwidth of at least 1 Gbps.

l) Ovirt Installation

Figure 2. 1 : oVirt Dashboard

 oVirt version 4.2 was installed. oVirt Engine was deployed on a CentOS 7 installed virtualbox and Gluster storage and two oVirt nodes were installed on two PCs’. Also moVirt was installed on a samsung smart phone. For managing the VMs over a mobile and using moVirt, creating the VM pools, switching off and on the VMs,creating VMs, migrating were tested.


As shown in Figure 2. 1 Dashboard of the oVirt engine displayed as a web interface.

Figure 2. 2 : Operations on Dashboard

As shown Figure 2. 2, data centers, clusters, hosts, networks and etc can be initialized and it has a better flow on creating a datacenter with the facilities, which are going to be virtualized in oVirt.

Figure 2. 3 : Initializing Hosts

As shown in Figure 2. 3 the hosts can be initialized with the web portal by providing the detail of hosts.









 oVirt platform provides a mobile application for remote accessing and handling the cloud. As shown in the Figure 2. 4 and Figure 2. 5, component in a data center can be initialized.

Figure 2. 4 : mOvirt

Figure 2. 5 : Dashboard on mOvirt

Figure 2. 6 : Notifications on mOvirt

 or better network monitoring process, the notifications for the cloud should be processed in a easy way. Current version in mOvirt works with ovirt 4.1 or upper versions. In mOvirt, the notifications on the virtual machines which are created were showed on the mobile application as shown in the below Figure 2. 6.

Figure 2. 7 : Details of a virtual machine

 As shown in Figure 2. 7, detail of a virtual machine which was created can be monitored on mOvirt.

Figure 2. 8 : Migration

 Also as shown in Figure 2. 8, migration over the cluster can be done using web portal and using mOvirt as well. As shown in Figure 2.09, pinging was done to a host from a virtual machine using mOvirt.

Figure 2. 9 : Ping to from the Virtual box in an oVirt node

ll)Installing Storage Services 
 Ceph and Gluster storages were installed in partitions in PCs where oVirt nodes were installed. Gluster installed as a replicate storage on the PC with 180+GB storage

Problems Encountered
As the problems when deploying cloud were, system requirements as they were needed for installing oVirt engine. Because of specified RAM and Network interface cards were needed on the PCs and servers for make. Private networks. And also misconfigurations on the key components such as storages. And some conflicts since the oVirt nodes and storages were installed on same machines. When connecting storage and oVirt engine together, some conflicts were  occurred due to some misconfigurations on Ceph and Gluster .