Log in

Previous 10

Oct. 13th, 2016

ovirt-node-ng: checking the differences between current squashfs and new available squashfs

In case you are wondering how to check what's new shipped inside a released ovirt-node-ng squashfs from ovirt-node-ng jenkins jobs:

First install required python module, python-libguestfs:

# dnf/yum install python-libguestfs -y

* NOTE: At the date of this post, if you are using CentOS7 or RHEL7 please update the libguestfs with tech preview url available here due a bug in libguestfs.

Now clone the tree where the tool is available:

$ git clone http://gerrit.ovirt.org/p/ovirt-node-ng
$ python ovirt-node-ng/scripts/generate-manifest.py ovirt-node-ng-image.squashfs-4.1-999.20160902.0.el7.img ovirt-node-ng-image.squashfs.4.1-999.20160928.0.el7.img
Key packages from ovirt-node-ng-image.squashfs.4.1-999.20160928.0.el7.img
* cockpit-ovirt-dashboard-0.10.6-1.3.6.el7.centos.noarch
* kernel-3.10.0-327.36.1.el7.x86_64
* vdsm-4.18.999-629.git0e539de.el7.centos.x86_64
* ovirt-hosted-engine-setup-2.1.0-0.0.master.20160927160934.gitce201e3.el7.centos.noarch
* ovirt-release-master-4.1.0-0.1.master.20160928000105.gitf36a206.noarch
Diff between images:
--- ovirt-node-ng-image.squashfs-4.1-999.20160902.0.el7.img

+++ ovirt-node-ng-image.squashfs.4.1-999.20160928.0.el7.img

@@ -1,8 +1,8 @@

@@ -43,14 +43,14 @@

@@ -74,20 +74,20 @@

@@ -103,37 +103,37 @@

@@ -163,15 +163,15 @@

@@ -201,11 +201,11 @@

@@ -241,15 +241,15 @@

@@ -302,7 +302,7 @@

@@ -355,7 +355,7 @@

@@ -413,7 +413,7 @@

@@ -441,7 +441,7 @@

@@ -451,16 +451,17 @@

@@ -552,7 +553,7 @@

@@ -566,15 +567,15 @@

@@ -615,8 +616,8 @@

@@ -630,7 +631,7 @@

@@ -640,21 +641,21 @@

@@ -663,18 +664,18 @@


Jun. 22nd, 2016

Step by Step: oVirt Node 4.0 Beta setup and Hosted Engine via Cockpit

oVirt Node 4.0 is the new generation of oVirt hypervisor created by ovirt-node team. In this post, I am going to describe how to do the setup of oVirt Node 4.0 and Hosted Engine via Cockpit.

Before we start, let's do a quick recap in a few words..

What's oVirt Node?
It's a minimal OS that contains all requirements to become an oVirt hypervisor.

What's Hosted Engine?
It's the ability of having the oVirt Node and oVirt Engine in the same machine. Basically, the oVirt Engine will be a virtual machine in the hypervisor. In case you are wondering, Hosted Engine has high availability.

Why we have a new generation of oVirt Node?
It's has been while since the ovirt-node creation, approximately +8 years and ovirt-node requires an update to make users and developers easier.

Some examples of improvements:
- Installation now is based on CentOs/Fedora
- RHEL/Fedora OS like
- New user interface (integrated with Cockpit)
- It's possible to use tools like yum and rpm
- nodectl command line tool
- No need to persist conf files anymore
- Filesystem layout as LVM making possible snapshot, rollback operations
and much more...

Although, we provide via jenkins job several formats of ovirt-node 4.0, like: .iso, .qcow2, .squashfs for this post we will use the .iso. For the oVirt Engine side, we will use the appliance image that already contains the ovirt-engine ready to use.

What's the requirements for this example?
- NFS storage
- ovirt-node-ng iso
- ovirt-engine-appliance

Step by Step::

#1 - Files to download
ovirt-node-ng iso

#2 - Copy the .iso to USB, DVD
# dd if=ovirt-node-ng-installer-ovirt-4.0-snapshot-2016061710.iso of=/dev/sdX

#3 - Boot the image

#4 - Select the language

#5 - Adjust the date, keyboard, network and press Begin Installation

Tip: if you configure network in the installer, keep the ip address in mind

#6 - Set root password, optionally create a non root user and reboot the system after installation is complete

#7 - In case, you didn't configure the network in the installer it's time to setup an IP address (via dhclient) or set an ip address

#8 - Install the ovirt appliance rpm in the hypervisor
# yum install ovirt-engine-appliance-4.0-20160610.1.el7.centos.noarch.rpm

#9 - Use a web-browser and connect into the hypervisor via cockpit using the port 9090. To continue check the generated certificate and accept it.

#10 - Login into the cockpit with your root account.

#11 - Select virtualization tab, Hosted Engine and click start

#12 - Answer yes as we want to use the machine as hypervisor and create the engine as virtual machine

#13 - Select the supported storage, in our example nfs3

#14 - Specify the nfs path

#15 - Select the nic the host agent will use for the bridge

#16 - Answer yes for automatic configure iptables

#17 - Set the gateway

#18 - Select the device to boot the vm, in this example disk

#19 - Specify the console type (vnc or spice)

#20 - Specify the path of OVA file

#21 - Answer yes to use cloud-init to customize the appliance

#22 - Answer Generate to generate cloud init ISO

#23 - Specify the engine FQDN

In this step, you can use internal DNS or set in /etc/hosts the node.localdomain and engine.localdomain as resolvable names. It's not only important for this initial setup but for later when adding a second host into the hosted engine setup.

Example (in the hypervisor):

# vi /etc/hosts node.localdomain engine.localdomain

Tip: You can also setup hostname of hypervisor via Cockpit in case it's not set yet.

#24 - Automatic execute engine-setup in the appliance, in this example, yes.

#25 - Yes for automatic restart engine vm as monitored service

#26 - Set the domain

#27 - Set or skip the password for the engine appliance

#28 - Confirm the CPU family

#29 - Set number of virtual CPUs of vm

#30 - Set or accept generated MAC for the vm

#31 - Set memory size of VM

#32 - Set VM network

#33 - In this example, answer yes to copy /etc/hosts from hypervisor to engine vm for name resolution in the setup

#34 - Set engine admin password

#35 - Complete the questionnaire with the name to identify the host in engine, smtp, answer the final engine settings

#36 - Confirm settings to start the setup

Wait a litte bit and you will see the conclusion of process and your engine vm will be available soon as well.

Jul. 14th, 2015

oVirt in the 16th edition of the International Free Software Forum (FISL)

Last week I have participated of FISL conference from 8th to 11th July in Porto Alegre/Brazil. This year we completed 4 years of oVirt participating in FISL.
One of benefits to be in FISL and others similar events is the face-to-face contact between oVirt community/developers and users. We have used all time we could in the booth/talks to explain how new features will be integrated to oVirt 3.6 and answering general questions around oVirt.


oVirt Community Update

We have started with the annual oVirt Community update. The goal for the community update slot in FISL is to share user experience with the current release of oVirt and share what's coming in oVirt 3.6.

Gluster and oVirt

We also had a talk about Gluster and oVirt by Marcelo Barbosa, he showed
how oVirt + Gluster is running in the development company that he works.
In the end, people asked questions how he integrated FreeIPA with oVirt
and how well is running Jenkins and Gerrit servers on top of oVirt.
Next year Marcelo should take 2 slots for a similar talks, people are very interested in Gluster with oVirt and real use cases as demonstrated.

Case Study VDI TR Odonto

Candido Raphael is a consult guy that brings to Open Source events use cases of
oVirt deployment. This year, he brought an example of migration of Terminal Service and Windows solution to a oVirt VDI solution. The crowd got excited and several questions were made to Candido about the implementation and hardware he used. Candido please keep bringing more use cases ;-)

Virtualization CPU SLA

Amador gave a talk about CPU SLA. I must say it was awesome talk. It went from
how it works in behind the scenes, like, setting CPU SLA manually via xml/virsh
and finally how we set it via oVirt Engine. As he mentioned in the talk, some features were added in oVirt 3.3 and now for oVirt 3.6 we have much more. He also explained the balloon schema via MoM to the crowd. Well done Amador.

Generic Registration

This year I brought a talk about the Generic Registration that oVirt 3.6 will provide via ovirt-register tool. Basically, now users can register their hypervisors running ovirt-register --engine-fqdn myengine.fqdn instead of going into oVirt Engine admin portal. This tool supports Fedora, CentOS 7, oVirt Node 3.6 and Debian.
We got feedback from the people in the room and a volunteer for packaging the tool in Debian. 8-)

If would like to test the tool in Fedora 22 (python3), use:
$ sudo dnf install python3-ovirt-register

We called the tool 'python'-ovirt-register as it provides a python library too.

Integration: oVirt Docker

Amador started explaining topics and concepts involved in Atomic, Docker, Kubernetes to everyone be in the same page. Later the showed how oVirt can be integrated with such topics. Was an amazing topic, crowd made several questions related to the subject.

Top questions/answers in this event:

* How can I convert my VMWare to oVirt? Can I use the Graphical interface?
oVirt 3.6 provides in oVirt Engine the possibility to migrate the VMWare guests.
See: https://www.youtube.com/watch?v=QSss__Nl5rU

* Which distro oVirt 3.6 supports at moment as Hypervisor?
Fedora, CentOS 7, Debian

* When the oVirt 3.6 final release will be launch?
Plase see: http://www.ovirt.org/OVirt_3.6_Release_Management

* Could you please share the oVirt 3.6 testing repo?
Please see:

* Where can I download ovirt-node 3.6 iso ?
We provide it via jenkins job at moment for testing:

* Can I use oVirt Node, Hosted-Engine and Gluster or ISCSI together?
oVirt Node support all features that oVirt provides, in short answer,
yes oVirt 3.6 should support it.

* How can I upgrade between the releases of oVirt?
Use engine-setup tool. It will detect you have oVirt Engine running and
will upgrade it. For oVirt Node you can boot the new image or install the rpm
of iso in oVirt Engine and later trigger the upgrade via oVirt Engine.

* Can I have 3rd party backup vendor tool integrated to Graphical interface of oVirt?
I recommend you contact your favorite backup vendor and check it.
The oVirt community is open for new patches, improvements or suggestions for
better integration.

Finally, I would like to thanks Amador, Candido and Marcelo again for the great work we made in the oVirt booth. Next year would be awesome to see the companies that contact us in the event for information how to migrate their current virtualization solution to oVirt giving a talk about their use case.


All slides available at:

For general questions, please use our mailing list:

Feb. 9th, 2015

Fosdem and oVirt

This year I had opportunity to go to FOSDEM conference as part of oVirt team, to show to users our bits and exchange knowledge about several topics that users raised like:

How to install oVirt?
How to migrate to oVirt from Vmware or Xen platforms?
Will virt-v2v be integrated to oVirt Engine?

and many others questions such: upgrade ovirt, third backup solutions, ovirt-node, openstack, gluster etc. It was a great experience for sure, without mention that I could talk with others oVirt contributors from community during fosdem and in the ovirt social event.

Two things in this event that got my attention during my booth time:

First: when I approach people going to our booth with:
'Have you heard about ovirt?' a lot of people just answered: 'Yes, I am using it'. Pretty awesome feedback.

Second: "Do you have support for debian as hypervisor?". In fact, there are people in our team working in the support and we are looking for new contributors to speed up this support. At least, 3 people shared that will join the effort to make it happen. (if you are interested, join ovirt devel mailing list)

During the event we also had talks related to oVirt:

Utilizing NUMA architecture in oVirt

Moving your Virtual Machines to oVirt with ease

oVirt and Gluster Hyperconvergence

Docker Integration in oVirt and IaaS

Smart VM scheduling in oVirt cluster

Validate your gerrit patches automaticly using magic hooks

Fabricate your automated devops environment using python

If you never been in FOSDEM, I really recommend this technical event.
Hope to see you with the ovirt guys next year!

Oct. 24th, 2014

oVirt node: hosted engine support

oVirt Node 3.5.0 contains ovirt-node-plugin-hosted-engine, which allows setting up hosted engine to run oVirt Engine as virtual machine on the node (support HA, requires at least two hosts).

To start the setup you must inform in the Text User Interface (TUI) how to proceed the installation of oVirt Engine virtual machine:

.ISO file, booting as cdrom, so you proceed the installation as normal operational system, later setting oVirt Engine and hosted-engine will connect to it and make all changed needed to configure your environment. The iso will be downloaded via http.

Pre-configured image with oVirt setup, after install required to run: engine-setup --offline --config-append=ovirt-engine-answers

Install the virtual machine booting via PXE.

Below example will be based on ISO (CentOS 6.5).

Step1: Providing .ISO

Step 2: The engine-hosted-engine-setup will start in screen...

Step 3: The engine-hosted-engine-setup will start in screen...

Step 4: Initial setup
For this step, please keep in mind:
- The storage supported at moment for the virtual machine of hosted-engine are:
    iscsi, nfs3, nfs4
- Admin portal password and FQDN are required to later hosted-engine connect to oVirt Engine and add the changes.
- The default path that the ISO is uploaded in oVirt Node is:

Step 5: Time to install the Operational System
The virtual machine is started to be installed the OS. Connect to VM via remote-viewer with the temp. password provided in the console and conclude the installation. AFTER the successfully OS installation, press 1 and continue.

$ remote-viewer vnc://IP_ADDRESS:5900

Step 6: Setup oVirt Engine
Connect again into the VM, update the system and setup oVirt Engine, AFTER the engine-setup is complete press 1 and the hosted-engine will finish the setup.

# yum update
# yum localinstall http://resources.ovirt.org/pub/yum-repo/ovirt-release35.rpm
# yum install ovirt-engine
# engine-setup

Oct. 20th, 2014

Latinoware2014 - oVirt Report

Last week I have participated of Latinoware conference from 15th to 17th Oct in Foz do Iguacu/Brazil with 4.532 attendees. We (as Red Hat) went with a huge number of Red Hatters and Fedora people to promote the Open Source. As I went there to promote oVirt project, below my view of talks.

oVirt Overview

Amador gave a talk explaining the oVirt components and architecture, from oVirt Node until the new features available in 3.5 version. The crowd made general questions and as usual how to migrate their datacenter from Vmware to oVirt. Congrats Amador!

Slides: http://www.ovirt.org/images/e/eb/Ovirt-overview-latinoware2014.odp

virt-v2v professional uncomplicated migration

Laercio works at Itaipu Technological Park (PTI) where creation and sharing of knowledge are the standouts. Established in 2003 by Itaipu Binacional – world's largest hydroelectric generation plant in energy generation - the PTI's position as a science and technology hub in Brazil and Paraguay is consolidated. He demonstrated how they migrated from libvirt/kvm to oVirt and encourage people to do the same. We had cases from crowed asking how to migrate from Xen using the same tool, pretty cool talk.

Slides (in pt_BR): http://www.ovirt.org/images/0/00/Virt-v2v-latinoware2014.odp

oVirt and Spice as VDI Solution

Candido Raphael is a consultant which showed in his talk how he used oVirt and Spice in two customers as VDI solution. One of customers was software house which had issues with their employees not creating virtual machines centralized and the other solution was to a car reseller. Well done!

Slides: http://www.ovirt.org/images/a/a2/OVirt-Spice_Protocol_V01.pdf

oVirt Node Project

Despite of few months working officially as oVirt Node engineer, I have been contributing with several patches which made me brave enough (wearing my hat) to talk about it. I have shared what's the ovirt-node project, how to install/update, how to contribute with it and even showed hosted-engine feature which is available in 3.5 version. During the talk I was interrupted several times for questions, which was good and in the end I had a student looking for help in his final work at college.

Slides: http://www.ovirt.org/images/a/af/Ovirt-node-latinoware2014.odp


Besides the oVirt team we also had many other Red Hatters attending the conference and presenting talks, such as Amador Pahim (oVirt), Leonardo Vaz (XFS and Gluster), Daniel Bristot (Realtime), Marcelo Leitner and Flavio Leitner (OpenVSwitch), Herton (Kernel), Carlos Maiolino (XFS), Ricardo Martinelli (OpenShift), Mauricio Leal, Pedro Ganen. I would like to thank them for their presence. Finally, I would like to thank Fedora folks and specially the Latinoware organization team for making the greatest FOSS conference in Latin America.

Jun. 12th, 2014

Generating oVirt node iso with modified packages

This post is about generate an oVirt Node image with updated packages, in
the below example we will update VDSM (node agent) and oVirt Node Plugin VDSM (TUI plugin for node registration).

Iso that will be updated: ovirt-node-iso-3.0.4-1.0.201401291204.vdsm34.el6.iso

Packages versions that will be updated in the above iso:

Note: CentOS 6.5 (CentOS-6.5-x86_64-minimal.iso) will be used in this demo as specific virtual machine to build oVirt Node iso.

Required tool to edit the node:
edit-node is the tool used to edit the node image and include a new package.
Please note that it must be run on the same OS which is used within the image.
So an CentOS image must be edited on a CentOS host.

Repos for edit-node:
1.el6: http://resources.ovirt.org/releases/node-base/edit-node-el6.repo
2.fedora: http://resources.ovirt.org/releases/node-base/edit-node.repo

Step by step:
# cat /etc/centos-release
CentOS release 6.5 (Final)

# yum install wget createrepo
# wget -O /etc/yum.repos.d/edit-node-el6.repo http://resources.ovirt.org/releases/node-base/edit-node-el6.repo

# yum install ovirt-node-tools (download stable edit-node and pre-requirements)

Install required packages for build:
# yum install make autoconf automake pyflakes logrotate gcc python-pep8 libvirt-python python-devel python-nose rpm-build sanlock-python genisoimage python-ordereddict python-pthreading libselinux-python python-ethtool m2crypto python-dmidecode python-netaddr python-inotify python-argparse git python-cpopen bridge-utils libguestfs-tools-c pyparted openssl libnl libtool gettext-devel

Update pep8:
# yum install http://danken.fedorapeople.org/python-pep8-1.4.5-2.el6.noarch.rpm

Install Apache to be your local repo
# yum install httpd
# chkconfig --levels 235 httpd on
# mkdir -p /var/www/html/nodebuild

Build vdsm and ovirt-node-plugin-vdsm:
# git clone git://gerrit.ovirt.org/vdsm && cd vdsm
# git checkout remotes/origin/ovirt-3.4 -b 3.4 (3.4 is current stable branch)
make your changes
# ./autogen.sh --system && make && make rpm && cd ..
* To ignore tests and other tips: http://www.ovirt.org/Vdsm_Developers#Building_a_Vdsm_RPM

# git clone git://gerrit.ovirt.org/ovirt-node-plugin-vdsm && cd ovirt-node-plugin-vdsm
# git checkout remotes/origin/node-3.0 -b 3.0 (3.0 is the current stable branch)
make your changes
# ./autogen.sh && make && make rpms && cd ..

Copy rpms generated to /var/www/html/nodebuild/ and create a local repo
# cp ~/rpmbuild/RPMS/noarch/* ~/rpmbuild/RPMS/x86_64/* /var/www/html/nodebuild/
# createrepo /var/www/html/nodebuild/

Add the additional repo:
# vi /etc/yum.repos.d/edit-node-el6.repo
name=Local node build

Download the iso that will be changed:
# wget http://resources.ovirt.org/releases/3.4/iso/ovirt-node-iso-3.0.4-1.0.201401291204.vdsm34.el6.iso

Download the last edit-node and execute it:
# git clone git://gerrit.ovirt.org/ovirt-node
# ovirt-node/tools/edit-node --repo /etc/yum.repos.d/edit-node-el6.repo --update vdsm,ovirt-node-plugin-vdsm* ovirt-node-iso-3.0.4-1.0.201401291204.vdsm34.el6.iso --name mynewovirtbuild

Note: It's not required to store edit-node repo into /etc/yum.repos.d. You can use it in any directory to avoid cluttering up normal system operation.

Others related links:

Jun. 8th, 2014

Setting up a TFTP server, PXE boot server with libvirt and virt-manager for ovirt-node

This post is about setup virt-manager to autoinstall oVirt Node as virtual machine via libvirt/PXE. Additionaly, TFTP server will be installed in the host machine which runs the virt-manager.

I have created the post based on Fedora 20, fell free to post comments about your experience in others versions or distros.

Installing and Setting packages
# yum install virt-manager tftp tftp-server libvirt livecd-tools -y

Reload libvirtd to create virbr0
# /bin/systemctl restart libvirtd.service

Notice that now you will have the virbr0 interface:
# ip addr
3: virbr0: NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 56:14:04:78:c4:f7 brd ff:ff:ff:ff:ff:ff
inet brd scope global virbr0
valid_lft forever preferred_lft forever

1) Configure the XML of the default libvirt network to include the PXE settings:
bootp file='pxelinux.0' server=''

# virsh net-destroy default
# virsh net-edit default
# virsh net-start default

2) Enable tftp-server
# vi /etc/xinet.d/tftp
disable = yes
disable = no

# /bin/systemctl restart xinetd.service

3) Download ovirt-node image and setup tftpboot
Download the last oVirt Node stable available:
# wget http://resources.ovirt.org/releases/3.4.0-ga/iso/ovirt-node-iso-3.0.4-1.0.201401291204.vdsm34.el6.iso

Convert livecd to pxeboot image:
# livecd-iso-to-pxeboot ./ovirt-node-iso-3.0.4-1.0.201401291204.vdsm34.el6.iso

Copy the files generated to tftp directory:
# cp -Rpv tftpboot/* /var/lib/tftpboot/

Edit default file and include ovirt node settings
# vi /var/lib/tftpboot/pxelinux.cfg/default

DEFAULT pxeboot
LABEL pxeboot
    KERNEL vmlinuz0
    APPEND rootflags=loop initrd=initrd0.img root=live:/ovirt-node-iso-3.0.4-1.0.201401291204.vdsm34.el6.iso rootfstype=auto ro liveimg check RD_NO_LVM rd_NO_MULTIPATH rootflags=ro crashkernel=128M elevator=deadline install quiet max_loop=256 rhgb rd_NO_LUKS rd_NO_MD rd_NO_DM firstboot storage_init=/dev/vda ssh_pwauth=1 adminpw=ovonFQQPIAM9o management_server= BOOTIF=link

- firstboot: first boot
- adminpw: Sets an encrypted, temporary password for admin (ovonFQQPIAM9o is ovirt encrypted)
- management_server: Specifies - the management server to be used.
- storage_init: Initialize a local storage device. (Depending can be vda/sda)
- ssh_pwauth: Enable ssh
- BOOTIF: specify network for bridge (link = autodetect)

Setting Firewalld
firewall-cmd --permanent --add-service=tftp
firewall-cmd --reload

First, check if your host has enabled the nested-kvm, if not, enable it and via virt-manager interface copy the Processor flags to the virtual-machine. After that, create your new virtual machine for oVirt Node based on PXE boot.

Links related to this topic

May. 12th, 2014

FISL15 - oVirt report

Last week I participated of FISL conference from 7th to 10th May in Porto
Alegre/Brazil with Red Hat team and Fedora community to promote oVirt
and cloud technologies, below my view of these days.

For those who never heard about FISL, it is the largest FOSS events in
LATAM and one of the largest in the world, this year they had 6.017
participants according with official report. The registered audience
includes community, developers, companies,
students, colleges and government institutions.

oVirt Community update

This year we had a special guest Brian Proffitt, the Technical
Community Manager of oVirt. He joined our troop which contained
Amador Pahim (Red Hat), Marcelo Barbosa (Community member) and myself
(Red Hat) to demostrate and talk about oVirt.

Below the talks during our community update:

- oVirt Overview - Amador Pahim

- The Road Ahead for the oVirt Community - Brian Proffitt

- Installation Process - Marcelo Barbosa

- Hot Features in current version - Amador Pahim

- v2v Migrating virtual machines to oVirt - Douglas Landgraf

The feedback was very positive, people often raised hands to make
questions during all presentations. As expected, we knew some
faces in the crowd from previous years of community update and
we are glad to have such people year after year sharing
their thoughts and needs.

Some highlights that I would like to point are:

- New users from VMWare want to migrate to oVirt. Year after year we
always have people asking how to migrate from VMWare environment to oVirt.
Two special cases this time, one from Brazilian government and other from private
company which are looking for a open source solution to a
possible migration of 400 VMware guests.

- Questions about ipv6 support

- A developer from community want to make oVirt run in Slackware and
will join forces to us.

- A teacher from Brazillian Computer Science college shared that he
has a student doing his Conclusion work about oVirt and asked if
we are interested about it. I replied instantly that we are and can
help him with any information that he needs.

- User reporting that he has oVirt and RHEV running in their
environment. RHEV as main platform to their customers and oVirt
for the development phase of their product.

To close the oVirt participation in the event with the gold key we had
Brian Proffitt in: oVirt: How to Connect with a Really Mature Open Source Project.

A brillant talk showing the history of oVirt and RHEV from the early days as commercial and closed
solution to acquisition of Qumranet by Red hat. For me it was very cool to remember these
early days which I was part of it.

All slides will be available here: http://www.ovirt.org/OVirt_Slide_Decks

Thanks again to all oVirt troop guys which spend 3 full days sharing
the knowledge to oVirt users and to Leonardo Vaz to make the booth happen.
See you there next year!

Jul. 9th, 2013

FISL14 - oVirt and Cloud EcoSystem

Last week I participated of FISL conference from 3th to 6th July in Porto
Alegre/Brazil with Red Hat team and Fedora community to promote oVirt
and cloud technologies, below my view of these days.

For those who never heard about FISL, it is the largest FOSS events in LATAM and one of the largest in the world, having around 8.000
participants. The registered audience includes community, developers, companies,
students, universities and government institutions.

oVirt activities during FISL

This year we had a lot of people interested about oVirt (yes, the
project is growing pretty fast here in LATAM) visiting our booth and
we learning about the project, the features and hearing what they can
expect in the upcoming releases.

We also had talks about oVirt and Virtualization ecosystem in
conference program:

oVirt Community update

Speakers: Amador Pahim (left), Marcelo Barbosa (Fedora Ambassador and local oVirt community), Douglas Landgraf (right)

At the beggining we had only Red Hatters involved in this talk, but we
invited Marcelo since he is a oVirt/Fedora passionated contributor
which has been promoting and testing it in his free time.

The audience was a mixed between people that want to learn about oVirt
and people that already uses oVirt, some of attending includes
computer science students, HP Brazil, Brazilian govern institute,
Brazilian Colleges and so on.

We started the talk introducing oVirt, telling what is it about,
explaining the architecture, features, supported components (storage,
domain controllers, etc.) etc. We also described supported
installation process and we used the remaining time for a demo and to
answer audience questions.

In the end, people started asking how to migrate from a Vmware/Vshere
scenario (Yes, we do. See v2v tool). Mental note for upcoming events:
Work in a talk to explain this tools in depth.

Ovirt + Gluster
Speaker: Theron Conrey (Red Hat)

One of the greatest talks in our opinion, because Theron provived an
excellent overview of Cloud Computing and explained how to build one
using oVirt/Gluster.

Spacewalk & oVirt

Speakers: Marcelo Mello and Amador Pahim (from Red Hat)

Another great talk, where Marcelo and Amador made Spacewalk/oVirt work
together in a demo for provisioning a environment capable to scale
based on the demand.

KVM - Ademar Reis

Ademar provided an excellent report about KVM/libvirt/qemu recent
enhancements and what the can be expected in Virtualization field for
upcoming years.

Additionally, Theron (left), Ademar (center) and John Mark Walker talked about virtualization in a booth.

oVirt Features 3.1 -> 3.2

Speakers: Douglas, Amador Pahim (from Red Hat), Marcelo Barbosa
(Fedora Ambassador and local oVirt community)

We used this talk to present a list of features from oVirt to 3.1 to
3.2, including some demos.


Fabiano Franz talked about OpenShift in the main track/booth a lot of people interested about openshift. Diane Mueller provided a demo in our booth.

Besides the talks above, we also presented small quick version of the
talks at the booth for those ones which were interested on attending
it. There were also many other talks about virtualization projects
sponsored by Red Hat in main conference program, presented by other
people and companies.

I'd like to thank all people involved on it (too many names to list here) but specially Leonardo Menezes Vaz and Leslie Hawthorn which worked hard to have our space/booth and all stuff ready for this event.

See you there next year!

Previous 10

October 2016




RSS Atom
Powered by LiveJournal.com