የኢትዮጵያ አርቲፊሻል ኢንተለጀንስ ኢኒስቲትዩት

ዳታ ሴንተር ዲቪዥን
EXISTING INFRASTRUCTURE
AND
PRODUCTION ENVIRONMENT
TECHNICAL DOCUMENTATION AND USER MANUAL
 EAII oVirt Open Virtualization Manager
Management For VM’s
Documentation & User manual
Release 2.0

Note
For the safe use of this production environment, before use be sure to know what you doing and
read the documentation and walk through the user manual carefully and in case of additional
information or any difficulties/problems consult the Data center Divisor staffs/admin.
Change History

Date Version Author Description Remarks

May 2023 1.0 EAII Data Center Divisions User Manual for the existing First draft
infrastructure and Virtualized
environment

Aug 2023 2.0 EAII Data Center Divisions User Manual / documentation Second
for the existing infrastructure draft
and Virtualized environment
Table of Contents
1. Introduction .............................................................................................................................................. 6
1.2. Overview............................................................................................................................................ 6
1.3. Objective............................................................................................................................................ 6
1.4. goal .................................................................................................................................................... 6
2. Understanding the Existing Infrastructure .............................................................................................. 7
3. EAII existing Tier-3 Cloud Modular Data Center and its infrastructure .................................................. 7
3.1 Overall Tier-3 Cloud modular Data Center ........................................................................................ 8
3.2 Tier-3 Cloud modular Data Center, Racks and lay outs ..................................................................... 8
3.3 Tier-3 Cloud modular Data Center, SDN Network Architecture ........................................................ 9
3.4 Tier-3 Cloud modular Data Center, IOC Network Topologies ............................................................ 9
3.5 DCF Solution – Fusionmodule200 module ...................................................................................... 10
3.6 Tier-3 Cloud modular Data Center, Total Number of Nodes ........................................................... 10
3.7 Tier-3 Cloud modular Data Center , list of Network Devices .......................................................... 11
3.8 Tier-3 Cloud modular Data Center, Power room ............................................................................. 11
3.9 Tier-3 Cloud Data Center, Outdoor fans for IT & power room ........................................................ 12
4. Existing virtualization production environment .................................................................................... 12
4. How to Access the physical servers ....................................................................................................... 13
5. Installing red hat Virtualization as a Self-hosted engine................................................................... 14
5.1. Installing red hat virtualization hosts ........................................................................................ 15
6. Installing the self-hosted engine deployment ................................................................................... 16
7. How to install OS on the server and install oVirt VM manager ........................................................ 16
8. How to Add hosts in to the oVirt VM manager ................................................................................. 16
9. preparing storage for red hat virtualization ...................................................................................... 16
10 Understand How oVirt open virtualization manager works and its features .............................. 16
11 working on and manage oVirt open virtualization manager ........................................................ 16
12 Downloading and uploading Images to oVirt open virtualization manager ................................ 16
13 How to create and manage Vm’s on oVirt open virtualization manager ..................................... 16
14 How to create template and make VM’s from templates ............................................................. 16
15 What is TRUNAS storage manager and how it works ................................................................... 16
16. Creating the Virtual Machine ......................................................................................................... 19
16.1 For Windows OS ............................................................................................................................. 19
16.1 Step 1: Creating/preparing the critical/skeletons part of the VM ................................................ 19
 16.2 Step 2: Completing the VM installation......................................................................................... 24
16.3 DNS registration ............................................................................................................................. 28
16.4 The AWX Ansible Automation ....................................................................................................... 30
16.5 For Linux OS Installation ................................................................................................................ 32
TO be updated/added with .................................................................................................................... 34
16.x Mapping local IP to Public IP .......................................................................................................... 34
16.x Creating templates ......................................................................................................................... 34
16.x Creating VM’s from templates ....................................................................................................... 34
16.x Adding resources to the created Vm.............................................................................................. 34
16.x Moving or migrating VM’s to another host ................................................................................... 34
16.x Creating GPU enabled VM’s ........................................................................................................... 34
16.x FORMAN ......................................................................................................................................... 34
16.x Help or service request desk .......................................................................................................... 34
16.x Password management (For changing pass) ................................................................................. 34
16.x AI, INSA and NISS Secure Communication platform/ environment.............................................. 34
16.x LDAP ................................................................................................................................................ 34
16.x NLP .................................................................................................................................................. 34
16.x VPN users ........................................................................................................................................ 34
17. Benefits of using Virtualization ...................................................................................................... 35
18. Conclusions ..................................................................................................................................... 35
1. Introduction
A user manual goes by many names. You may hear terms like instruction manual, user guide,
maintenance manual, or technical documentation but they all mean the same thing. A user
manual is designed for an end user to use any product or service properly or to find solutions to
problems that arise through use. This user manual and technical documentation is provided in
both format such as hard copy and digital format. This User manuals and technical documentation
contains detailed, step-by-step instructions for the end user and also allow for support in
troubleshooting, it can also serve as reference for the existing infrastructures and systems used
in EAII, for a quick reference a table of contents is included so that users can easily feel
comfortable beginning to use the manual.

1.2. Overview

This user manual and technical documentation document is prepared to provide what the EAII
existing infrastructure and the production environment looks like.

1.3. Objective

The objective of preparing this user guide/manual and technical documentation is to understand
how the existing infrastructure, production environment, services, Hardware product and
systems are running and also creating a way for existing and specially for new employee who is
joining the DC Division/Team to easily understand, get Familiar and how to interact with the EAII
environment.

1.4. goal

The main goal is to understand the overall existing systems and infrastructure and to do it safely
and efficiently. This user manual and technical documentation is a type of technical
documentation that helps to understand the overall existing infrastructure, production
environment, systems, services and products of EAII ,to use, maintain, and fix/troubleshoot.

Preparing this user manual there can be secondary goals to create a great user experience in
other words, this user manual and technical documentations instructs readers on the overall
existing systems and infrastructure. This user manual we can call it as a comprehensive user
manual consists of both text and visuals (graphics, tables, illustrations, etc.), procedures (detailed
instructions) and concepts.

This user manual is written for all kinds of users, specifically for the EAII Data Center division team
members or for new employee joining the DC division in a simple way. Not only for the datacenter
division team, experienced users sometimes need to refresh their knowledge and look up some
relevant information.
2. Understanding the Existing Infrastructure

The existing infrastructure can be categorized in to two, the new one is, Tier -3 cloud Modular
data center and the old one is implemented not hierarchical, not standard, flat, very open as well
as simple and most importantly very vulnerable to any damages/attacks. We Can say except the
Datacenter 80% of the existing infrastructure is at risk.

For the internet purpose

• There is one HUAWEI firewall called USG6600E, the outside port of this firewall is
connected with internet via fiber and the IP add is https://192.168.1.1:8443/default.html#
• This firewall in the inside it is connected with unmanaged switch then from this
unmanaged switch uplink is goes to each floor.
• In each floor there is a 6u wall mounted Rack which contain a patch panel & switch are
placed inside.
• form this patch panel cables are connected to the rooms wall outlet/in the ground, so
users get internet from wall outlet/in the ground or from the Wi-Fi router.
• In the Datacenter we have two 48 port Huawei Switches their Ip add 192.168.1.253 is

3. EAII existing Tier-3 Cloud Modular Data Center and its infrastructure

The EAII mission critical Tier-3 Cloud modular Data Center is called Fusionmodule2000 and built
following the international standard Data Center specifications and incorporate many features
and capabilities.
3.1 Overall Tier-3 Cloud modular Data Center

3.2 Tier-3 Cloud modular Data Center, Racks and lay outs
3.3 Tier-3 Cloud modular Data Center, SDN Network Architecture

3.4 Tier-3 Cloud modular Data Center, IOC Network Topologies

3.5 DCF Solution – Fusionmodule200 module

3.6 Tier-3 Cloud modular Data Center, Total Number of Nodes

3.7 Tier-3 Cloud modular Data Center , list of Network Devices

3.8 Tier-3 Cloud modular Data Center, Power room

3.9 Tier-3 Cloud Data Center, Outdoor fans for IT & power room

4. Existing virtualization production environment

Computer virtualization is a process that uses software to create a simulated, or virtual,

computing environment that is abstracted from the physical hardware It allows us for more
efficient utilization of hardware resources by dividing them into multiple virtual machines (VMs)
that can run different applications and operating systems. Virtualization is the foundation of cloud
computing and a standard practice in enterprise IT architecture. It uses a hypervisor or other
virtualization technology to allocate resources from a host machine to the virtual machines

Virtualization involves using specialized software to create a virtual or software-created version

of a computing resource rather than the actual version of the same resource. With the help of
Virtualization, multiple operating systems and applications can run on the same machine and its
same hardware at the same time, increasing the utilization and flexibility of hardware.

In other words, one of the main cost-effective, hardware-reducing, and energy-saving techniques
used by cloud providers is Virtualization. Virtualization allows sharing of a single physical instance
of a resource or an application among multiple customers and organizations at one time.
virtualization plays a fundamental role in efficiently delivering Infrastructure-as-a-Service (IaaS)
solutions for cloud computing. Moreover, virtualization technologies provide a virtual
environment for not only executing applications but also for storage, memory, and networking.

4. How to Access the physical servers

Almost all the devices (the Firewall, Switches, Servers, computing storages, fiber & data cables, IP
camera, power PDU, PDF, AC, etc.) in the Data center are Huawei proprietary
The actual servers that we are using for the current virtualization is Huawei FusionServer 2288H
V5

Pic: servers & storages found in DC

The first thing to do before we do the virtualization is to make ready the Servers
Steps
1. Download the OS ISO image that you want to install and make it ready in your laptop or
USB Drive (make it bootable).
2. Connect the server with your laptop/desktop via the management port from at the back
the Server
3. The default IP address of the server is 192.168.2.100 (give the Ip for your laptop/desktop
within this range and make sure your default gateway is the server IP optional)
4. Use the web browser to access the server, The username/password is
Administrator/Admin@9000
5. After you enter the username and password you will face the GUI of the server with
different feature and configurable tabs
(Here we can click and see what is what after that the point is we need to install the OS
5. Installing red hat Virtualization as a Self-hosted engine
In Oracle Linux Virtualization Manager, a self-hosted engine is a virtualized environment where
the engine runs inside a virtual machine on the hosts in the environment. The virtual machine for
the engine is created as part of the host configuration process. And, the engine is installed and
configured in parallel to the host configuration. To install a self-hosted engine environment -
where the Red Hat Virtualization Manager (or "engine") is installed on a virtual machine that runs
on specialized hosts in the same environment it manages.

Since the engine runs as a virtual machine and not on physical hardware, a self-hosted engine
requires fewer physical resources. Additionally, since the engine is configured to be highly
available, if the host running the Engine virtual machine goes into maintenance mode or fails
unexpectedly the virtual machine is migrated automatically to another host in the environment.
A minimum of two KVM hosts are required to support high availability for a single virtual machine
running the self-hosted engine. But in our environment, we have used only one self-hosted
engine but for the resource sharing and redundance we have added some hosts so that if the
host running the virtual machine goes into maintenance mode or fails unexpectedly the virtual
machines will migrate automatically to another host in the environment.

To deploy a self-hosted engine, we perform a fresh installation of Oracle Linux 8.5 (or later) on
the host, we install the Oracle Linux Virtualization Manager Release Version 4.5.0.8-1.el8 package,
and then we run the hosted engine deployment tool to complete configuration.

Self-Hosted Engine and other Prerequisites/ Requirements

before deploying self-hosted engine, there are Requirements which we have satisfied, the
following prerequisites are a must be, to list few

• A fully qualified domain name (FQDN) for our engine and host with forward and
reverse lookup records set in the DNS.
• CPU, Memory, Storage, networking requirements
• Red Hat Virtualization Manager Hardware Requirements
• Client Requirements, Client Operating System SPICE Support
• Operating System, host, Browser Requirements
• Firewall Requirements for DNS, NTP, and IPMI Fencing
• Red Hat Virtualization Manager Firewall, Virtualization Host Firewall Requirements
• Etc.
 5.1. Installing red hat virtualization hosts

Red Hat Virtualization Host (RHVH) is a minimal operating system based on Red Hat Enterprise
Linux that is designed to provide a simple method for setting up a physical machine to act as a
hypervisor in a Red Hat Virtualization environment. The minimal operating system contains only
the packages required for the machine to act as a hypervisor, and features a Cockpit web interface
for monitoring the host and performing administrative tasks

Deploying GlusterFS Storage

Oracle Linux Virtualization Manager has been integrated with GlusterFS, an opensource scale-out
distributed filesystem, to provide a hyperconverged solution where both compute and storage
are provided from the same hosts. Gluster volumes residing on the hosts are used as storage
domains in the Manager to store the virtual machine images. In our scenario, the Manager is run
as a self-hosted engine within a virtual machine on these hosts; although, we can deploy
GlusterFS within a standalone environment.
Note the full process can be found on oVirt documentation https://www.ovirt.org/

Since we download the RHVH ISO image from the oVirt Portal:

1. Start the machine on which you are installing RHVH, booting from the prepared installation media.
2. From the boot menu, select Install RHVH 4.5 and press Enter.

3. Select a language, and click Continue.

4. Select a time zone from the Date & Time screen and click Done.

5. Select a keyboard layout from the Keyboard screen and click Done.

6. Select a network from the Network & Host Name screen and click Configure… to configure the
connection details. Enter a host name in the Host name field, and click Done.

7. Click Begin Installation.

8. Set a root password and, optionally, create an additional user while RHVH installs.
9. Click Reboot to complete the installation.

Note:
For more detail and how to check the status and all the things related with refer to www.ovirt.org/

Once we did the basic configuration physically, after that we can access it remotely via web
browser using the Ip add, Username & Pass, after accessing the server via web we can do the rest
of the configuration on the oVirt manager the next step will be to make the host as a Self-hosted
engine which allow us to manage and control all the resources and the whole environment.

Note: Read and prepare yourself for the following topics

6. Installing the self-hosted engine deployment

7. How to install OS on the server and install oVirt VM manager

8. How to Add hosts in to the oVirt VM manager

9. preparing storage for red hat virtualization

10 Understand How oVirt open virtualization manager works and its

features

11 working on and manage oVirt open virtualization manager

12 Downloading and uploading Images to oVirt open virtualization

manager

13 How to create and manage Vm’s on oVirt open virtualization

manager

14 How to create template and make VM’s from templates

15 What is TRUNAS storage manager and how it works

For the existing production environment among many we have used the virtualization flatform
called “OVIRT OPEN VIRTUALIZATION MANAGER”. OVirt is an open-source data center
virtualization platform developed and promoted by Red Hat. OVirt, which offers large-scale,
centralized management for server and desktop virtualization, was designed as an open-source
alternative to VMware vCenter. OVirt virtualization flatform allow us to managing hosts, virtual
machines, networks and storage etc. so in our production environment we have
1 Data Center,
6 hosts acting as one and managed by the oVirt manager (can also be managed
individually via their IP add)
5 Data Storage Domains
125 + Virtual Machines
Two local IP Add 192.168.1.0/24 and 172.16.1010.0/24 (this IP used for Mappings)
We also use public IP for those who need it 196.189.21.x (the last digit is 16x & 17x)

The Dash board

Compute

Hosts

Network
Storages

16. Creating the Virtual Machine

16.1 For Windows OS
16.1 Step 1: Creating/preparing the critical/skeletons part of the VM

Since everything is ready and good to go now it’s time to create the VM’s

Using this address 192.168.1.246/ovirt-engine/ with the credentials (UserN & Pass) enter to the
oVirt -engine virtualization manager then follows this step.

⁃ from the display screen you will find Dashboard, compute, Network, Storage, Administration
and event from those choice click on the compute tab then click Virtual Machines then on the
right top of the screen click the new tab,
From the appearing New Virtual Machine screen
Note if you can’t see the whole system click on Show Advanced Options: at the left
bottom of the screen click it

➢ General: -
- Cluster: from the dropdown lists choose AII_Cluster (this contain all clusters) or we can also
choose depending on the request or depending on our need
- Template: leave it as it is Blank| (0) this part is used for automatically VM creation since we
are creating a VM fresh/manually. (But if we are using the template everything is ready made
from the dropdown lists, we will choose what we want, it contains all the needed OS) we can
also choose depending on the request or depending on our need) so for now we will leave it
as it is “Blank| (0)”
 - Operating System: the dropdown lists contain all the needed OS, depending on the request
choose the OS type
- Chipset/Firmware Type: from the dropdown lists just choose “Q35 Chipset with UEFI” (we can
also choose depending on the request or depending on our need)
- Optimized for: from the dropdown lists choose “server” since most of the VM’s are created
for server purpose.
- Name: give it a standard name or a name related with the created VM.
- Description: give it a well-defined description for the created VM.
- Comment: write a comment that describes the VM
- Stateless, start in pause mode, Delete Protection, steeled make sure all the check box are
unchecked
- Instantiate VM network interface by picking a vNIC profile: On the bottom of the screen from
the dropdown lists choose oVirtmgmt/ovirtmgmt, here we can add by clicking the + sign to
add vNIC for the outside connection
-
➢ System:
➢ System:
➢ Memory size: fill it based on the request
➢ Maximum Memory: leave it as it defaults
➢ Physical Memory Granted: leave it as it defaults
➢ Total Virtual CPUs: the default is 2 CPU but if it is reasonable, we can allocate 4,8 based on
the request.
➢ Hardware Clock Time Offset: select GMT+03:00) E.Africa Standard Time
➢ Leave the rest as it is
➢

➢ Boot Option:
➢ Boot Option:
Boot Sequence
- First Device: select CD-ROM (after the Vm is completely created you must come
back here & select/chage to Hard Disk this is useful when the VM is start it will not Start
from the CD-ROM)
- Second Device: [None] leave it as it defaults or we can choose Hard Disk
- Attach CD: check the box then from the dropdown menu, choose the type of OS to
install
- Ok

- Create: Then click create tab

From the appearing New Virtual Disk under the New Virtual Machine screen

➢ New Virtual Disk

➢ Size (GiB): fill the amount of HD required
➢ Alias: it will get automatically from the name that you have filled
➢ Description: its optional we can leave it as a default or we can fill it
➢ Interface: choose SATA since we are installing Windows SCSII for Linux
 ➢ Storage Domain: leave it as a default, or we can choose which storage has more
free space than the others storage
➢ Allocation Policy: its optional we can leave it as a default
➢ Disk Profile: leave it as a default (it automatically takes the name from the Storage
Domain
➢ On the right side of the screen make sure to check only Bootable
➢ Ok: click okay
➢ Ok: finally click ok, then the critical part of the VM will be created but not over yet.
Note: At this point you have successfully created the essential part of the VM the next steps
will complete the creation of the VM.

16.2 Step 2: Completing the VM installation

Now go to the oVirt -engine virtualization manager then follows this step

Console: the oVirt -engine virtualization manager allows us to connect to all created VM’s
vis console. (is the way to access the created VM’s just like physically).

➢ Find the VM that you have created and wait for it until it powerup or click run,
when the created VM is power on (up) make sure it is green and the state is good,
for the first time to access the created VM the only option we have is via Console.
➢ Here we need to install the console client on our laptop /pc, At the bottom right
corner of the window click to console client … after that back to the Console
window
➢ On the right top of the oVirt -engine virtualization manager go to Console then
click the dropdown menu from the Console tab and then choose Console Options
then choose SPICE
➢ Ok: finally click ok
Now the Created VM is ready to be accessed via a Console
➢ Find the VM that is created and click it then click Console
➢ The Console client will be downloaded on your machine then click to open it; this
will take you to the created VM but which is not completed yet.
➢ You will face a black screen making you to choose the boot option, ctrl+Alt+delete
then choose to start from the CD ROM then follow the installation steps
➢ Select: Win…. (Window experience) … (this will allow us to you use the GUI)
➢
➢ Choose the operating system to Win …. (Desktop Experience…)
➢ Follow the normal step to install OS, User name, password
➢ Then click Install now.
➢ After everything is finished before you Reboot the created VM
➢ go to oVirt select the created VM then click edit
➢ Boot Options
-First Disk: choose Hard Disk
-Second Device: none
-Attach DC: uncheck the box
-Okay
-Then finally reboot the vm

Accessing the VM via console

➢ By default, the created vm NIC is disabled to activate the network adapter,
➢ go to the created vm, edit, boot option then under the boot sequence
➢ check the attach CD then choose virtio-Win-1.9.24.iso (reboot the vm)
➢ then access the VM via console again then go to the CD Drive (D:) virtio-win-1.9.24 and
open it and then
➢ install the virtio-win-gt-x64 (will activate the NIC) also
➢ install the virtio-win-guest-tool (will activate the IP to appear in the vm dashboard)
➢ Then cmd, ipconfig get the DHCP ip add
➢ Then to make sure the Ip is not occupied go to the oVirt and DNS paste the ip add if not
occupied give it to the created VM manually
➢ Default gateway 192168.1.1
➢ pref dns serv 8.8.8.8
➢ Alternative DNS serv: 192.168.1.150/151
➢ Under the server manager, enable remote desktop manager (RDP) (make sure to disable
firewall) sometimes rdp wont login/work so update the server
 The last thing to do is to create two admin account
➢ 1 for us (usern & Pass) to admin the created VM
➢ 1 for the requested user (usern & Pass) then we delete the default administrator account
so the other user won’t delete our account.
➢
Note: At this point you have successfully completed and installed the OS and created the VM.

16.3 DNS registration

DNS servers translate requests for specific domains into IP addresses, controlling which server
users with access when they enter the domain name into their browser.
Using this address 192.168.1.150/151:10000 with the credentials (UserN & Pass) enter to the DNS
Server Webmin manager then follows this step

➢ Step 1:
➢ Click Server then click BIND DNS Server
➢ Under the Existing DNS Zones click aii.com
➢ Under the Edit Master Zone click Address
Under the address Record
➢ Type the complete name of the created VM with.aii.com optional. and its Ip Address
➢ Tick the Update reverse? Yes, then click Create (you will find it at the bottom of the list)

Now you have done the DNS registration

16.4 The AWX Ansible Automation

AWX is an open-source community project, sponsored by Red Hat, that enables users to better control
community Ansible project use in IT environments. AWX is a modern web UI and API to manage your
organization's Ansible Playbook, Inventories, Vault, and Credentials. It is the Open-Source upstream
project of the Ansible Automation Controller (formerly Ansible Tower). Ansible Towers powers
enterprise automation by adding control, security and delegation capabilities to Ansible
environments
advantages of using AWX

• Increase efficiency & security:

• Provide better operational control and security.
• It will also increase efficiency as a team.
• Centralized logs:
• We can integrate AWX with multiple logging tools available in markets such as ELK & Loggly.
• AWX can Support and integrated with Multiple clouds.

Using this address 192.168.1.159:30080 (http://192.168.1.159:30080/#/login) with the

credentials (UserN & Pass) enter to the oVirt -engine virtualization manager then follows this
step
Note: this AWX works fine for LUNIX but most of the time for Windows it fails

➢
 ➢ go to host –

➢ In the name box, type the ip address of the vm that you created then click search (to make sure the
ip is occupied or not) if this ip is not found Add it
➢ type the ip address of the vm in the name box then click Add
➢ in the name box enter the ip add of the vm again
➢ description type any descriptions that defines the vm
➢ Inventory click the search button then choose AII_Inventory then click select
➢ Click save

On the same page under the Resource

➢ Go to Template
➢ Click copy SSH Key
➢ Click Launch
➢ Click DCAdmin then inter the ip Add of the vm in the name box then click next
➢ SSH password A@...1
➢ Privilege escalation password A@...1
➢ Next
➢ Limit: inter the Ip Add of the vm
➢ Next
➢ Launch (this is point it must be successful if not do it again)

On the same page under the Resource

➢ Go to Template
➢ Deploy Puppet Agent
➢ Launch
➢ Limit: inter the Ip Add of the vm
➢ Next
➢ Launch
 ➢ Deploy Puppet Agent: (if it’s successful it done well, if not do it again
But sometimes Deploying the Puppet Agent from this GUI won’t bring up the ip add so the other
option is to do it from the Command Line do this on the vm as sudo -i / sudo su then run the
following Command as a sudo user (For LINUX only)
➢ apt update && apt -y install qemu-guest-agent = now it will install qemu guest agent wait for it till
100% .... but sometimes if this line of command is not working try this apt install qemu-guest-agent
if successfully insall 100% go to the next command.
➢
➢ systemctl enable qemu-guest-agent
➢ systemctl start qemu-guest-agent
➢ systemctl status qemu-guest-agent

at this pint the qemu-guest-agent.service - QEMU Guest Agent

Active: active (running)

16.5 For Linux OS Installation

Follow the same steps as you followed for the Win installation except few things.
1. Make sure to select the OS type is LINUX
2. Make sure to Attach the OS image is Linux
3. From the general tab
➢ instance Images
➢ Create
➢ Interface select VirtIO-SCSI
➢ Ok, ….
After that access the vm via console and follow the normal Linux OS installation steps. When the
installation complete before you reboot go to the oVirt manager
➢ Boot Option
- Boot Sequence

- First Device select Hard Disk

- Un check the box of Attach CD

 - Ok ….

Now reboot the vm after that console the vm again using the credentials then
Be a sudo user sudo su
sysadmin@pwebserver:~$ sudo su

root@pwebserver:/home/sysadmin# now you are a sudo user

root@pwebserver:/home/sysadmin# apt-get update = to update the server

- Ip a = to see the ip add assigned via the DHCP, get the ip add and go to the
manager/DNS and make sure it’s not occupied then

vi /etc/netplan/00-installer-config.yaml = to change the ip add to manual

press i to edit, ESC to leave from eaditing, q to quit w= to write/save, wq!= save quit
network:
ethernets:
enp1s0:
addresses:
- 192.168.1.X/24
gateway4: 192.168.1.1
enp7s0:
addresses:
- 172.16.101.X/24
gateway4: 172.16.101.1
version: 2
- ESC
- Wq!

after editing or adding the ip

- netplan apply

then ping any IP in the network, including 8. 8.. 8..8

creating users
here we need to create two admin users and we make sure that they both are sudo users to
have privileges to run commands as a root user (“sudoers”)
- adduser sysadmin
- usermod -aG sudo sysadmin = this line of command will make the created user as a sudoer
- sudo su sysadmin

………. CONGRATULATIONS NOW YOU ARE SUCCESSFULLY COMPLETED THE……

TO be updated/added with

16.x Mapping local IP to Public IP

16.x Creating templates
16.x Creating VM’s from templates
16.x Adding resources to the created Vm
16.x Moving or migrating VM’s to another host
16.x Creating GPU enabled VM’s
16.x FORMAN
16.x Help or service request desk
16.x Password management (For changing pass)
16.x AI, INSA and NISS Secure Communication platform/ environment
16.x LDAP
16.x NLP
16.x VPN users
16.1 ……………

……….
 17. Benefits of using Virtualization

The cloud delivers more flexibility and reliability, increased performance and efficiency, and helps
to lower our IT costs. It also improves innovation, allowing EAII to achieve faster time to
stakeholders and incorporate AI and machine learning use cases into the institution strategies.
The benefits that we get from deploying this Virtualized environment are so many, to list few:

• gave us more flexible and efficient allocation of resources.

• Enhance development productivity.
• lower the cost of IT infrastructure.
• Remote access and rapid scalability.
• Allow us to have High availability and disaster recovery.
• Enables us running multiple operating systems.
• Etc.

18. Conclusions

Cloud computing provides advanced computing resources available on-demand, that scale as
needed, with regular updates and without the need to buy and maintain an on-premise
infrastructure. Despite all the advantages, cloud computing is the fastest growing part of network-
based computing and offers a great advantage to customers of all sizes. our cloud still has so much
to improve on with security and ease of integration, but cloud computing will continue to grow
and advance the ability to share and store data in the technological world.
Sooner or later EAII will move to the new Government and Secure cloud service environment until
then we need to, keep monitoring, providing resources & support and keep improving the existing
infrastructure n production environment.