As part of my migration to Linux as my primary laptop OS, I needed to revisit my choice of virtualization provider. Long-time readers probably know that I was an early adopter of VMware Fusion, starting way back in 2006 with the very first “friends and family” release (before it was even publicly available). Obviously I can’t use Fusion on Linux, but do I use VMware Workstation for Linux? VirtualBox? Or something else? That’s what I set out to determine, and in this post I’ll share what I selected and the reasoning behind my selection.
So what were the options to consider? While there may be some other solutions, these are the three I primarily assessed:
Since I have been using Vagrant quite a bit over the last few years, whatever solution I selected needed to work reasonably well with Vagrant.
I’m pretty familiar with KVM and Libvirt, so I started there. Given that KVM and Libvirt are “native” to Linux, it felt like it would be a clean solution. While Continue reading
Last fall, I wrote a piece about why I had switched to VirtualBox (from VMware Fusion) for my Vagrant needs. As part of my switch to Fedora Linux as my primary laptop OS, I revisited my choice of virtualization provider. I’ll describe that re-assessment in a separate post; the “TL;DR” for this post is that I settled on VirtualBox. As it turns out, though, installing VirtualBox 5.1 on Fedora 25 isn’t as straightforward as one might expect.
After a number of attempts (using a test VM to iron out the “best” procedure), here’s the process I found to be the most straightforward:
Run dnf check-update
and dnf upgrade
to pick up the latest packages. If a new kernel version is installed, reboot. (I know this sounds contrived, but I’ve run into issues where some kernel-related packages aren’t available for the kernel version you’re actually running.)
Install the RPMFusion repos. You only really need the “free” repository, but you can install the “nonfree” as well if you like (it won’t affect this process). I won’t go through the process for how to do this; it’s really well-documented on the RPMFusion web site and is pretty straightforward.
Next, use Continue reading
Welcome to Technology Short Take #77. I’ve got a new collection of links and articles from around the Web on various data center-focused technologies.
In Episode 69 of Software Gone Wild we discussed ways of increasing visibility into VXLAN transport fabric. Another thing we badly need is visibility into the virtual edge behavior, and to help you get there Iwan Rahabok created a set of vRealize dashboards that include the virtual edge networking components. Hope you’ll find them useful.
Running Linux containers on a single host is relatively easy. Building private multi-tenant networks across multiple hosts immediately creates the usual networking mess.
Fortunately the Socketplane team did a pretty good job; for more details watch the video from Docker Networking Fundamentals webinar or listen to the podcast I did with them a year ago.
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.
oVirt 4.0.6 Release is now available
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 for Speed—Coming Changes in oVirt's CI Standards
Еxtension of iptables Rules on oVirt 4.0 Hosts
KVM/Linux Nested Virtualization Support For ARM
Virtual Machines in Kubernetes? How and what makes sense?
ANNOUNCE: New libvirt project Go XML parser model
Using OVN with KVM and Libvirt
New libvirt project Go language bindings
CI tools testing lab: Making it do useful work
CI tools testing lab: Integrating Jenkins and adding Zuul UI
CI tools testing lab: Adding Zuul Merger
CI tools testing lab: Setting up Zuul Server
Welcome to Technology Short Take #76, the first Technology Short Take of 2017. Normally, I’d publish this on a Friday, but due to extenuating circumstances (my mother-in-law’s funeral is tomorrow) I’m posting it today. Here’s hoping you find something useful!
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 cool new feature from a friend or a web site.
In a software community project, one of the biggest things a community must do is to provide proper onboarding to the project's result. This means:
Explaining what the software is
Providing a clear path to getting the software
Demonstrating how to use the software
All three of these onboarding requirements must be done right in order for onboarding to work successfully. Documenation, then, fulfills the third requirement: showing how software can be used. Not every one will need it, but for those users who do need it, it is very nice Continue reading
Hi folks, as I mentioned earlier in the week, I’ll be in the Northeast next week for the VTUG Winter Warmer event. If you can be there, great.. if not, Stu Miniman of “The Cube” has been gracious enough to invite me to an interview and will be broadcasting it on Thursday, Jan 19th.
Here are the details:
Thursday, January 19th, 2017 @ 1:30 p.m. EST
http://siliconangle.tv/vtug-winter-warmer-2017/
Many thanks to Stu!
Captain KVM
The post Upcoming Interview with “The Cube” appeared first on Captain KVM.
Hi Folks – if any of you are going to be at the VTUG Winter Warmer at Gillette Stadium, come find me, I’ve got a keynote at 10am at “West Side South”. If you’re going to be in the area, it’s an event that’s been going on for several years now and should be fun..
I’ll be talking about Red Hat’s strategy in the Hybrid Cloud and especially how RHV fits into that.
I believe (don’t quote me on this) that the event is free for VTUG members, and that all you need to do is register to become a VTUG member (I believe that is also free) before the event.
Date: January 19, 2017
Location: Gillette Stadium, Patriot Place, Foxboro MA
Hope to see you there,
Captain KVM
The post Boston VTUG Winter Warmer appeared first on Captain KVM.
The featured webinar in January 2017 is the Introduction to Docker webinar, and in the featured video Matt Oswalt explains the basic Docker tasks. Other videos in this webinar cover Docker images, volumes, networking, and Docker Compose and Swarm.
To view the featured video, log into my.ipspace.net, select the webinar from the first page, and watch the video marked with star.
Read more ...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 patch didn't break things is to install oVirt and try running a few basic commands, like 'adding host', 'adding vm', 'creating snapshots', and other tasks you can only do if you have a full oVirt system up and running. Here is where OST comes in!
oVirt system tests is a testing framework written in Python, using 'python-nose' and oVirt Python SDK and runs on auto-generated VMs created by Lago. It is used by the oVirt CI to run post merge end-to-end testing that runs on a fully deployed oVirt environment and has been proven to detect multiple regressions Continue reading
Welcome to Technology Short Take #75, the final Technology Short Take for 2016. Fortunately, it’s not the final Technology Short Take ever, as I’ll be back in 2017 with more content. Until then, here’s some data center-related articles and links for your enjoyment.
Nothing this time around!
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 that a given change will fix some complex issue or to preview a new feature on its early stages of development.
Until now, to build rpms from a patch, a developer needed to use a custom Jenkins job, which was only available to ovirt-engine and only for master branch. Another option was to try and build it locally using standard CI 'mock runner.sh' script which will use the same configuration as in CI. For full documentation on how to use 'mock-runner', checkout the Standard CI page.
To ease Continue reading
© Calico project (http://docs-archive.projectcalico.org/en/1.4.3/addressing.html) |
Hi Folks.. the last time I left off, we had just finished setting up the initial pieces for hosted engine (RHEL configuration) in order to provide HA for RHV-M. Today we’re going to add an additional host and test things out.
Let’s get going!Once hosted engine is setup, adding another RHEL host to the configuration is almost identical to a standard configuration. There is only 1 additional step that involves ensuring that the HA pieces specific to hosted engine get installed along with the RHV packages.
The workflow itself is simple:
As usual, I recorded a walk through so that things are more clear. I sped things up significantly as my home lab is ~very~ slow.. Maybe I’ll get Continue reading