oVirt Blog
On March 22, the oVirt project released version 4.1.1, available for Red Hat Enterprise Linux 7.3, CentOS Linux 7.3, or similar.
oVirt is the open source virtualization solution that provides an awesome KVM management interface for multi-node virtualization. This maintenance version is super stable and there are some nice new features.
So what’s new in oVirt 4.1.1?
Storage Team
LUNs can be removed from a block data domain, provided that there is enough free space on the other domain devices to contain the data stored on the LUNs being removed.
Support for NFS […]
Gamification is the concept of applying game mechanics and game design techniques to engage and motivate people to achieve their goals.
It taps into the basic desires and needs of the users impulses which revolve around the idea of Status and Achievement.
To put it in other words, it is turning day-to-day tasks, the kind you might do at home or work, into a game which you can earn points, badges and compete with other people that are doing the same things.
oVirt & Gamification
You probably didn’t know, but this isn’t the first time […]
Introducing oVirt virtual machine management via Vagrant.
In this short tutorial I’m going to give a brief introduction on how to use vagrant to manage oVirt with the new community developed oVirt v4 Vagrant provider.
Background
Vagrant is a way to tool to create portable and reproducible environments. We can use it to provision and manage virtual machines in oVirt by managing a base box (small enough to fit in github as an artifact) and a Vagrantfile. The Vagrantfile is the piece of configuration that defines everything about the virtual machines: memory, cpu, base image, and […]
It’s a new year with new opportunities for oVirt to show up its virtualization features! We’re getting ready for DevConf.CZ in Brno next week, and FOSDEM in Brussels the week after that! We look forward to meeting European developers and sysadmins to share your experiences!
Here’s what happened in December of 2016.
Software Releases
oVirt 4.0.6 Release is now available
In the Community
Happy New Documentation!
oVirt System Tests to the Rescue!—How to Run End-to-End oVirt Tests on Your Patch
CI Please Build—How to build your oVirt project on-demand
The Need […]
The oVirt Project is pleased to announce the availability of all-new principal documentation for the oVirt 4.0 branch.
There are many people out there who are content to use software without documentation, preferring to muddle through the software based on past experience with similar software or just the desire to put the software through its paces.
We all do this; I could not tell you the last time I looked at documentation for Firefox or Chrome, because I’ve been using browsers for over 20 years and seriously, what else is there to learn? Until I learn about a […]
Today, when an oVirt developer pushes a patch to review on oVirt Gerrit, various validations are triggered in CI via the ‘check-patch’ job, as defined by the project maintainers. Usually these jobs includes ‘unit-tests’, ‘db tests’, static analysis checks, and even an occasional ‘functional test’. While it might seem that it covers alot and gives a good indication that the patch is good to be merged, unfortunately it is not always the case.
The reason it’s not enough lies in oVirt’s complexity and the fact it’s a Virtualization project, which means the only real way to know if your […]
All projects in oVirt CI are built today post merge, using the ‘build-artifacts’ stage from oVirt’s CI standards.
This ensures that all oVirt projects are built and deployed to oVirt repositories and can be consumed by CI jobs, developers or oVirt users.
However, on some occasions a developer might need to build his project from an open patch.
Developers need this capability in order to to examine the effects of their changes on a full oVirt installation before merging those changes.
On some cases developers may even want to hand over packages based on un-merged patches to the QE team to verify […]
oVirt’s CI standards have been in use for a while in most oVirt projects and have largely been a success.
These standards have put the control of what the CI system does in the hands of the developers without them
having to learn about Jenkins and the tooling around it. The way the standards were implemented, with the mock_runner.sh script, also enabled developers to easily emulate the CI system on their own machines to debug and diagnose issues.
From the oVirt infra team’s point of view, the CI standards have removed the need to constantly maintain build dependencies […]
In one of my last articles I described the example of installing HP System Management Tools to the physical server HP ProLiant DL360 G5 with CentOS Linux 7.2. After a while, the same exact server was used as a virtualization host and the oVirt Hosted Engine components were deployed on it. The host was put into maintenance mode recently, all packages were upgraded from the online repository, including the HP tool pack installed on it.
After the installation, I decided to check the workability of the upgraded tools. I also tried to open the web page of HP System […]
As oVirt continues to grow, the many projects within the broader oVirt community are thriving as well. Today, the oVirt community is pleased to announce the addition of a new incubator subproject, Vagrant Provider, as well as the graduation of another subproject, moVirt, from incubator to full project status!
According to maintainer Marc Young, Vagrant Provider is a provider plugin for the Vagrant suite that enables command-line ease of virtual machine provisioning and lifecycle management.
More on Vagrant Provider
The Vagrant provider plugin will interface with the oVirt REST API (version 4 and higher) using the […]
