February 2022 - Users - Ovirt List Archives

Xcp-ng, first impressions as an oVirt HCI alternative

by Thomas Hoberg

Comments & motivational stuff were moved to the end... Source/license: Xen the hypervisor is moved to the Linux foundation. Perpetual open source, free to use. Xcp-ng is a distribution of Xen, produced by a small French company based on Xen using (currently) a Linux 4.19 LTS kernel and an EL7 frozen userland from July 2020: they promise open source and free to use forever Mode of operation: You install Xcp-ng on your (bare metal) hardware. You manage nodes via XenOrchestrator, which is a big Node.js application you can run in pretty much any way you want. Business model: You can buy support for Xcp-ng at different levels of quality. XenOrchestrator as AN APPLIANCE exposes different levels of functionality depending on the level of support you buy. But you get the full source code of the appliance and can compile it yourself to support the full set of qualities. There is a script out there, which allows you to auto-generate the appliance with a single command. In short you are never forced to pay, but better help can be purchased. How does it feel to a CentOS/RHEL user? The userland on the nodes is EL7, but you shouldn't touch that. CLI is classic Xen, nothing like KVM or oVirt. I guess libVirt and virsh should be similar, if they live up to their promise at all. Standard user-land on Orchestrator appliance is Debian, but you can build it on pretty much any Linux with that script: all interaction is meant to be done via Web-UI. Installation/setup: There is an image/ISO much like the oVirt node image. Based on a Linux 4.19 LTS kernel and an EL7 frozen userland from July 2020 and a freshly maintained Xen with tools. Installation on bare metal or VMs (e.g. for nested experimentation) is a snap, HCL isn't extraordinary. I'm still fighting to get the 2.5/5GBit USB3 NIC working that I like using for my smallest test systems. A single command on one node will download the "free"-Orchestrator appliance (aka Xoa) and install it as a VM on that node. It's installed as auto-launch and just point your brower to its IP to start with the GUI. There is various other ways to build or run the GUI, which can be run on anything remotely Linux, within the nodes or outside: more on this in the next section. The management appliance (Xoa) will run with only 2GB of RAM and 10GB of disk for a couple of hosts. You grow to dozens of hosts, give a little more RAM and it will be fine. Compare to the oVirt management engine it's very, very light seems to have vastly less parts that can break. And if it does, that doesn't matter, because it is pretty much stateless. E.g. pool membership and configuratoin is on the nodes, so if you connect from another Xoa they will just carry over. Ditto storage, that configuration which oVirt keeps in the management engines Postgres database, is on the nodes in Xcp and can be changed by any connected Xoa. Operation: Xen nodes are much more autonomous then oVirt hosts. The use whatever storage they might have locally, or attached via SAN/NAS/Gluster[!!!] and others.They will operate without a management engine much like "single node HCI oVirt" or they can be joined into a pool, which opens up live migration and HA. A pool is created by telling a node that it's the master now and then adding other nodes to join in. The master can be changed and nodes can be moved to other pools. Adding and removing nodes to a pool is very quick and easy and it's the same for additional storage repositories: Any shared storage added to any node is immediately visible to the pool and disks can be flipped between local and shared storage very easily (I haven't tried live disk moves, but they could work). Having nodes in a pool qualfies them for live migration (CPU architecture caveats apply). If storage is local, it will move with the VM, if storage is shared, only RAM will move. You can also move VMs not sharing a pool and even across different x86 variants (e.g. AMD and Intel), when VMs are down. If you've ever daddled with "Export domains" or "Backup domains" in oVirt, you just can't believe how quick and easy these things are in Xcp-ng. VMs and their disks can be moved, copied, cloned, backed-up and restore with a minimum of fuzz including continuous backups on running machines. You can label machines as "HA" so they'll always be restarted elsewhere, should a host go down. You can define policies for how to balance workloads across hosts and ensure that HA pairs won't share a host, pretty similar to oVirt. The "free" Xoa has plenty of "upgrade!" buttons all over the place. So I went ahead and build an appliance from source, that doesn't have these restrictions, just to see what that would get me. With this script here: https://github.com/ronivay/XenOrchestraInstallerUpdater you can build the Xoa on any machine/VM you happen to be running with one of the many supported Linux variants. I build one variant to run as a VM on Xcp-ng and I used another to run on an external machine: All three Xoas don't step on each others toes more than you make them: very, very cool! The built-in hypervisor interfaces and VIO drivers of almost any modern 64-Bit Linux make VMs very easy. For Windows guests there are drivers available, which make things as easy as with KVM. Unfortunately they don't seem to be exactly the same, so you may do better to remove guest drivers on machines you want to move. BTW good luck on trying to import OVAs exported from oVirt: Those contain tags, no other hypervisor wants to accept, sometimes not even oVirt itself. Articles on the forum suggest running CloneZilla at both ends for a strorage-less migration of VMs. I have not yet tested nested virtualization inside Xcp-ng (Xcp-ng works quite well in a nested environment), nor have I done tests with pass-through devices and GPUs. All of that is officially supported, with the typical caveats in case of older Nvidia drivers. So far every operation was quick and every button did what I expected it to do. When things failed, I didn't have to go through endless log files to find out what was wrong: the error messages were helpful enough to find the issues so far. Caveats: I haven't done extensive failure testing yet, except one: I've been running four host nodes as VMs on VMware workstation, with XCP-ng VMs being nested inside. At one point I managed to run out of storage and I had to shut down all "bare metal VMs" hard. Everything came back clean, only the migration project that had tripped the storage failure had to be restarted, after I created some space. There is no VDO support in the kernel provided. It should be easy enough to add given the sources and build scripts. But the benefit and the future of VDO are increasingly debated. The VMs use the VDI disk format, which is less powerful/flexible as CQOW with regards to thin allocation and trimming. It's on the roadmap, not yet in the product. Hyperconverged Storage: Xcp-ng so far doesn't come with a hyperconvered storage solution built in. Like so many clusters it moves the responsability to your storage layer (could be Gluster...). They are in the process of making LINSTOR a directly supported HCI option, even with such features as dispersed (erasure-coded) volumes to manage the write amplification/resilience as the node numbers increase beyond three. That's not ready today and they seem to take their sweet time about it. They label it "XOASAN" and want to make that a paid option. But again, the full source code is there and in the self-compiled Xoa appliance you should be able to use it for free. The current beta release only supports replicated mode and only up to four nodes. But it seems to work reliably. Write amplification is 4x, so bandwidth drops to 25% and is limited to the network speed, but reads will go to the local node at storage hardware bandwidths. The 2, 3 and 4 node replicated setup works today with the scripts they provide. That's not quite as efficient as the 2R+1A setup in oVirt, but seems rock solid and just works, which was never that easy in oVirt. Hyperconverged is very attractive at 3 nodes, because good fault resilience can't be done any cheaper. But the industry agrees that it tends to lose financial attraction when you grow to dozens of machines and nobody in is right mind would operate a real cloud using HCI. But going from 3 to say two dozen should be doable and easy: it never was for oVirt. XCP-ng or rather LINSTOR won't support any number or storage nodes or easy linear increases like Gluster could (in theory). So far it's only much, much better at getting things going. Forum and community: The documentation is rather good, but can be lighter on things which are "native Xen", as that would repeat a lot of the effort already expended by Citrix. It's good that I've been around the block a couple of times already since VM/370, but there are holes or missing details when you need to ask questions. The community isn't giant, but comfortably big enough. The forum's user interface is vastly better than this one, but then I've never seen something as slow as ovirt.org for a long time. Technical questions are answered extremely quickly and mostly by the staff from the small French company themselves. But mostly it's much easier to find answers to questions already asked, which is the most typical case. The general impression is that there are much fewer moving parts and things things that can go wrong. There is no Ansible, not a single daemon on the nodes, a management engine that seems very light and with minimal state that doesn't need a DBA to hold and manage it. The Xen hypervisor seems much smarter than KVM on its own and the Xoa has both a rich API to do things, but also offers an API to next-level management. It may have less overall features than oVirt, but I haven't found anything that I really missed. It's much easier and quicker to install and operate with nothing but GUI which is a godsent: I want to use the farm, not spend my time managing it. Motivational rant originally at the top... tl;dr My original priorities for chosing oVirt were: 1. CentOS as RHEL downstream -> stable platform, full vendor vulnerability management included, big benefit in compliance 2. Integrated HCI -> Just slap a couple (3/6/9) of leftover servers together for something fault resilient, no other components required, quick start out of the box solution with a few clicks in a GUI 3. Fully open source (& logs), can always read the source to understand what's going on, better than your typical support engineer 4. No support or license contract, unless you want/need it, but the ability to switch that on when it paid for itself The more famous competitors, vSphere and Nutanix didn't offer any of that. (Citrix) Xen I excluded, because a) Xen seemd "old school+niche" compared to KVM b) Citrix reduced "free" to "useless" I fell in love with Gluster from its design: it felt like a really smart solution. I fell out with Gluster from its operation and performance: I can't count how many times I had to restart daemons and issue "gluster heal" commands to resettle things after little more than a node update. I rediscovered Xcp-ng when I discovered that HCI and RHV had ben EOLd.

2 years, 9 months

7
9
1 / 0

Restore from backup, consistent view between ovirt DB and Libvirt/QEMU

by Volenbovskyi, Konstantin

Hi, Let’s say that backup of ovirt engine is done once every day, for example 6 AM using engine-backup tool. Then during the day the changes are made that not only influence the database, but actually influence Libvirt/KVM/QEMU (create/delete VMs,snapshots, disks, ). Now let’s say at 18:00 an engineer restores from the backup. How the ovirt will be ‘synchronized’ to Libvirt (/QEMU)? Of course, it is OK to expect that system is being rolled back, but in that scenario there is nothing that I can imagine that will synchronize Ovirt database state to Libvirt/KVM/QEMU state. And once anything on (migrate/stop/start) – it will just fail in many cases because of inconsistency. In 4.2 documentation https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/... there is sentence like: “If migration is enabled at cluster level, virtual machines are automatically migrated to another host in the cluster; as a result, it is recommended that host reinstalls are performed at a time when the host’s usage is relatively low.“ Let’s say that there are 5 hosts (numbered from 1 to 5), 3 of them are hosted-engine (let’s say 1 to 3). Then first of all, person should find a brand new host (host 6), then install HE on that. OK, I understand that HE can be then reinstalled on hosts 1 to 3. But it when it comes VMs- if really migration of VMs can work, considering inconsistency above? Eg. snapshot that is already in QEMU (done at 11:00) and the volume chain is updated is gone from database (because it is restored to 6 AM) And in general, anything should be done towards non-HE hosts? So far the restore seems to be very intrusive and quite error-prone in two parts: first part is actual handling of VMs. And second part when ovirt-engine gets configured practically from scratch (through that dialog) BR, Konstantin

2 years, 9 months

1
0
0 / 0

Re: vm seal

by Nathanaël Blanchet

2 years, 9 months

2
4
0 / 0

Re: Problems configuring iscsi domain on ovirt 4.4.4.7-1.el8 / centos 8

by David Johnson

Ok. The nfs share with the vdsm group is working. But the intent is to switch to iSCSI. The little bit of documentation about iSCSI mentions nothing about vdsm or group 36. That gives me something to work with at least. Any ideas about how to clean up the mess left by the first attempt? I'm not finding the records for botched domain creation in the engine database, but the GUI shows them and complains that the iSCSI device is registered twice. On Wed, Feb 16, 2022, 2:06 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > To be honest, I just asked from curiosity. > In NFS it's mandatory to use group 36, but this is the linux group. > > I guess in TrueNAS it's something else, as I never configured group in > targetcli. > > The flow is usually: > - Target server listens on multiple IPs > - Client makes discovery on a single ip > - client logs in (lsscsi is the simplest approach to verify it) > - Client discovers and logs on other IPs that the target server uses > - Multipath aggregates the links > > As Multipath has a timeout of 20s while iscsi client uses 120s by default, > I usually change the client to use 15s timeout. > > When a path (for eample 1 switch is dead) is down, multipath will try > another link to reach the target server. > > It's nice there is a vdsm tool to configure those . > > WARNING: Never set clients with the same IQN (defined in a file in > /etc/iscsi...somethig -> see with rpm -ql iscsi-utils) > > Best Regards, > Strahil Nikolov > > On Wed, Feb 16, 2022 at 9:18, David Johnson > <djohnson(a)maxistechnology.com> wrote: > I used group 1 because nothing said what group to use, and googling "ovirt > iSCSI setup" returned nothing useful so I picked a number. If there is > someplace that actually gives detailed instructions I'm going to bookmark > it when I get the link. > > Yes, there is a storage network. There was a miscommunication and the > person attempting to create the connection didn't read instructions, so > they keyed in the main network ip, leaving a small mess for me to clean up. > The old truenas with nfs share is on the storage network and functioning > cleanly, and ovirt is able to see the iSCSI share on the storage network ip > address. > > Thank you. > > On Tue, Feb 15, 2022, 11:45 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> > wrote: > > Did you configure a storage network on oVirt ? > > About the size, why you use group '1' and not group '36' ? > > Best Regards, > Strahil Nikolov > > On Tue, Feb 15, 2022 at 20:47, David Johnson > <djohnson(a)maxistechnology.com> wrote: > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/2X7L3FUWHNP... > >

2 years, 9 months

2
1
0 / 0

Problems configuring iscsi domain on ovirt 4.4.4.7-1.el8 / centos 8

by David Johnson

Since the general recommendation seems to be to use iSCSI over NFS wth ovirt, I expect that I am missing something very obvious. Question: How do I complete the iSCSI storage domain configuration? Hardware configuration: - cluster controller - physical system - compute nodes - 2 - Current file store: NFS on TrueNAS - To-be file store: iSCSI on TrueNAS Problem reproduction: 1. We decided that the problems with NFS (regularly blocking and causing VM's to go into paused instead of IOWait mode) outweighed the benefit of ease of management, so we are preparing to move to iSCSI back end on TrueNAS. 2. We created an iSCSI share on the to-be TrueNAS system and granted access to a "ovirtuser" and group "1", with 30+ TB available storage. 3. We started to add the iscsi share to the ovirt data center using the GUI, under "Storage > Storage Domains" click the "New Domain" button. *Problem 1: *Ovirt immediately found the iSCSI share (yay), but says it has 0 GB and will not allow us to add it to the data center, or edit or remove it, so it is in a limbo state. *Problem 2: *Ovirt shows it on the wrong network (miscommunication). It is finding it on the general network instead of the isolated data network. The TrueNAS will be removed from the general network as soon as configuration is complete. Thank you *David Johnson*

2 years, 9 months

2
2
0 / 0

Cluster and datacenter compatibility levels

by Colin Coe

Hi all I'm looking for a definitive answer on what each compatibility level means. Specifically, I'm looking for: - new features - deprecated features - removed features We're on 4.3 so I'm looking for the info above on 4.4, 4.5 and 4.6 My main motivation is to ensure we don't lose SPICE support. We actually use RHV and I logged a case with Red Hat GSS but couldn't get the info I was after. Thanks

2 years, 9 months

2
1
0 / 0

vm seal

by Nathanaël Blanchet

Hello, I noticed that a vm created from a "sealed" template is initially mount on one host with libguestfs, with a virt-sysprep process, before getting ready to be used. This should be unuseful given that the template is already sealed. Is there a reason to that? -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 years, 9 months

2
3
0 / 0

Re: Backup prozess

by marcel d'heureuse

Sure: https://github.com/vacosta94/VirtBKP Br Marcel Am 14. Februar 2022 20:29:47 MEZ schrieb Jonas Liechti <jonas(a)rabe.ch>: >Would you mind sharing a link to this script? I would be interested in how it works.Am 14.02.2022 19:45 schrieb marcel d'heureuse <marcel(a)deheureu.se>: >> >> Moin, >> >> We have in our Environment 12 servers managed by one self hosted engine. It is ovirt 4.3.9. We are Freizeit on that Version. >> >> How did you make Backups? We use a github Script which generate via api a snapshot and Mount this disk into the vm where the backup Script is running. The backup Script Export this additional Hard disk to a storage and disconnect the disk and remove the snapshot. >> >> This works on Linux vm fine if they have Medium load. If we try this with a Windows 10 vm or Windows Server vm or a Linux vm with high load or with a very big Hard drive this will not work. Disk can't Export and snapshot will not delete. >> >> I have found winchin and bareos but I have not start to check this first I want to have some more possible options. >> >> Thanks >> >> Marcel

2 years, 9 months

1
0
0 / 0

Re: Backup prozess

by Jonas Liechti

Would you mind sharing a link to this script? I would be interested in how it works.Am 14.02.2022 19:45 schrieb marcel d'heureuse <marcel(a)deheureu.se>: > > Moin, > > We have in our Environment 12 servers managed by one self hosted engine. It is ovirt 4.3.9. We are Freizeit on that Version. > > How did you make Backups? We use a github Script which generate via api a snapshot and Mount this disk into the vm where the backup Script is running. The backup Script Export this additional Hard disk to a storage and disconnect the disk and remove the snapshot. > > This works on Linux vm fine if they have Medium load. If we try this with a Windows 10 vm or Windows Server vm or a Linux vm with high load or with a very big Hard drive this will not work. Disk can't Export and snapshot will not delete. > > I have found winchin and bareos but I have not start to check this first I want to have some more possible options. > > Thanks > > Marcel

2 years, 9 months

1
0
0 / 0

Backup prozess

by marcel d'heureuse

Moin, We have in our Environment 12 servers managed by one self hosted engine. It is ovirt 4.3.9. We are Freizeit on that Version. How did you make Backups? We use a github Script which generate via api a snapshot and Mount this disk into the vm where the backup Script is running. The backup Script Export this additional Hard disk to a storage and disconnect the disk and remove the snapshot. This works on Linux vm fine if they have Medium load. If we try this with a Windows 10 vm or Windows Server vm or a Linux vm with high load or with a very big Hard drive this will not work. Disk can't Export and snapshot will not delete. I have found winchin and bareos but I have not start to check this first I want to have some more possible options. Thanks Marcel

2 years, 9 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users February 2022