[ovirt-users] Re: Cluster and datacenter compatibility levels

[Martin Perina]

Hi Colin,

you can take a look at below archived message if you are interested in
features bound to specific cluster level:

https://lists.ovirt.org/archives/list/de...@ovirt.org/message/QJRYA4FKX64DMIF4VPW5VU4APN3KULX5/

Regards,
Martin

On Tue, Feb 15, 2022 at 1:02 AM Colin Coe  wrote:

> 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
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/XFBSQGS6G4J432MQ53SHTD2K4ZCC5IC5/
>


-- 
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/KY6XETEADPLFJBIMNLM2QP4BVFBQJI4Z/

[ovirt-users] Re: Xcp-ng, first impressions as an oVirt HCI alternative

[Glen Jarvis via Users]

On Monday, February 14th, 2022 at 3:03 PM, Nathanaël Blanchet 
 wrote:


> If some beginners read my post, I want to tell them
> they are welcome, and they can be sure to find some
> quality into code, into updates, into innovation, into
> entreprise features, into mailing list support, and
> they are welcome to contribute to make virtualization
> greater and greater!

I'm new and I found this post very helpful. And, thank you for the welcome! :)

Cheers,


Glen
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/Y7XIZ3WOHGTORNUFV7BKUTDI223FYMVG/

[ovirt-users] Cluster and datacenter compatibility levels

[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
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/XFBSQGS6G4J432MQ53SHTD2K4ZCC5IC5/

[ovirt-users] Re: How I'd like to contribute

[Nir Soffer]

On Sat, Feb 12, 2022 at 9:21 AM Glen Jarvis  wrote:

>
> > I would like to know why "vdsm-tool config-lvm-filter" makes
> > you pull your hair out.
> >
> > It was designed to help people configure their system
> > correctly without pulling their hair out trying to
> > understand how lvm filter works, and avoid the many
> > wrong ways it can be used.
>
> Honestly, it is just from a lack of understanding of what is happening
> when it does break (as it is for us when doing a hypervisor install on a
> fresh box). Normally, I can just dig through the stack and figure out what
> is happening. There are enough areas where I don't have some foundations
> that I'm not able to do so here (yet).
>
> For example, I don't quite understand iSCSI, Multipath, etc enough to know
> what is breaking, and why.
>
> I'm accustomed to being able to dig deeper at each level until I can
> generally see what is breaking.
>
> This confusion will go away as I get a bit more experience and have a
> "map" of what is going on on this level.
>
> FWIW, I started reading the Libvirt book previously mentioned and it's
> pretty straight forward. It looks like I just need to get through this
> enough to get a good foothold so that I can figure out how to either fix
> things when they break or point out properly why something is breaking (so
> I can get the appropriate help).
>
> >
> > Do you have some specific areas you would like to improve?
> >
>
> Actually, yes :)  In:
> 1. Learn libvirt more (in progress)

2. Review source for vdsm-tool to have a better sense what is going on
> 3. Setup an iSCSI system so  that I can make luns, build a system, play
> with storage pools this way
>

You may find vdsm/contrib/target tool useful:
https://github.com/oVirt/vdsm/blob/master/contrib/target

This tool makes it simple to create or delete a new iSCSI target for
development purposes.

The best way to add iSCSI server for development, is to create a new VM -
virt-manager is the easier way to do this, and install targetcli and copy
vdsm/contrib/target to the vm.

Then to create a new target you can run:

# ./target create mytarget

Creating target
  target_name:   mytarget
  target_iqn:iqn.2003-01.org.alpine.mytarget
  target_dir:/target/mytarget
  lun_count: 10
  lun_size:  100 GiB
  cache: False
  exists:False

Create target? [N/y]:


You may find the tool source interesting, explaining why we configure
the target in a certain way.

Nir
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/57ASPEVSTKHWBDYEVAKMSZVFYU6XORML/

[ovirt-users] Re: Xcp-ng, first impressions as an oVirt HCI alternative

[Nathanaël Blanchet]

Hello,

I have read several pessimistic posts of you, each time to be against 
the decisions of the ovirt community that you disagree. In general, my 
thoughts are that you want the community to be responsible for the 
Redhat descisions.


Like you I find RHV end of support very sad, but I unlike you I believe 
oVirt is so an incredible software, and also an example of opensource 
success project that, I do believe, will survive thanks to awesome 
people who have been contributing it for 10 years. Other downstream 
projects like OLVM decided to switch from Xen to KVM.


I've been working with ovirt since the very beginning in a large 
production success. Every people in my IT team are convinced that oVit 
makes our IT very stable and flexible (more than 300 VMs), and we 
convinced some partner to adopt it as well. My pain is that the oVirt 
project is underrated in comparison of the quality of the code, but you 
and I are actors of its popularity. I initially was not a developer, but 
thanks to oVirt, I'm now able to write complex playbooks for automatic 
deployments, as well I'm able now to debug python code. What I mean is 
that the project depends on the community members contribution, each one 
with his own capacity. For my own, I can help many beginners on the 
mailing list with simple tips as well as some others can translate into 
other languages.


Yes, I am aware of competitors projects like proxmox, xen and now 
XCP-NG. There is no perfect project. Everybody should be involved into a 
project that corresponds to its expectations.


In reality, I wonder about the goal of your posts, it seems that nothing 
goes into the good direction from your point of view... Did you 
contribute to change that? Did you pay anything to be so demanding?


Thank you to all community for providing such a wonderful software, and 
a specific mention to community leaders (Sandro?) and other 
contributors, we need positive attitudes.


If some beginners read my post, I want to tell them they are welcome, 
and they can be sure to find some quality into code, into updates, into 
innovation, into entreprise features, into mailing list support, and 
they are welcome to contribute to make virtualization greater and greater!


Le 14/02/2022 à 20:28, Thomas Hoberg a écrit :

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 

[ovirt-users] Re: vm seal

[Nathanaël Blanchet]

Le 14 févr. 2022 21:09, Arik Hadas  a écrit :On Mon, Feb 14, 2022 at 8:44 PM Nathanaël Blanchet  wrote:
  

  
  


Le 14/02/2022 à 17:45, Arik Hadas a
  écrit :


  
  




  On Mon, Feb 14, 2022 at 4:52
PM Nathanaël Blanchet 
wrote:
  
  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?
  
  
  
  Yes, we do this in order to produce different LVM IDs and
machine IDs for the provisioned VMs, see: https://gerrit.ovirt.org/c/ovirt-engine/+/115009

  

okay, but, I modified  the
  /usr/lib/python3.6/site-packages/vdsm/virtsysprep.py file like
  following:
args = ['--hostname', 'localhost', ''--selinux-relabel',
  '--update', '--network']"
in order to update packages on  template creation.
The template creation still works and the template is checked as
  sealed and os is updated, but now the vm creation never ends up
  and I have to manually kill the virt-sysprep process to stop the
  infinite process creation.
I believed it was a good workaround to get updated templates, but
  I had to rollback to default virt-sysprep args configuration,
  unless there is trick do to so?If you create the VM from the webadmin, you can uncheck the 'sealed' option in the new-vm dialog to skip the second execution of virt-sysprep on the VMIf you create it from REST-API (or the VM portal), you might want to change the configuration of the template in the database:update vm_static set is_template_sealed='f' where vm_name='';Thanks for this useful tip, but as you said if second seal has been designed it is to produce different VM IDs... So what will happen if I skip this process?Secondly I'd like to know if there is a way to skip the second seal from the template with oVirt VM ansible module( don't seem to be), it is safer than modifying the DB. 


  

  
  
  

-- 
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
blanc...@abes.fr
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/7VSOFV3TFSMKPEZBI2ERRVUCTFGJALQT/
  

  

-- 
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
blanc...@abes.fr
  


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/3BDZO7UUPYFDRBR3DNWH7EWKEV5BMYFE/

[ovirt-users] Re: vm seal

[Arik Hadas]

On Mon, Feb 14, 2022 at 8:44 PM Nathanaël Blanchet  wrote:

>
> Le 14/02/2022 à 17:45, Arik Hadas a écrit :
>
>
>
> On Mon, Feb 14, 2022 at 4:52 PM Nathanaël Blanchet 
> wrote:
>
>> 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?
>>
>
> Yes, we do this in order to produce different LVM IDs and machine IDs for
> the provisioned VMs, see: https://gerrit.ovirt.org/c/ovirt-engine/+/115009
>
> okay, but, I modified  the
> /usr/lib/python3.6/site-packages/vdsm/virtsysprep.py file like following:
>
> args = ['--hostname', 'localhost', ''--selinux-relabel', '--update',
> '--network']"
>
> in order to update packages on  template creation.
>
> The template creation still works and the template is checked as sealed
> and os is updated, but now the vm creation never ends up and I have to
> manually kill the virt-sysprep process to stop the infinite process
> creation.
>
> I believed it was a good workaround to get updated templates, but I had to
> rollback to default virt-sysprep args configuration, unless there is trick
> do to so?
>
If you create the VM from the webadmin, you can uncheck the 'sealed' option
in the new-vm dialog to skip the second execution of virt-sysprep on the VM
If you create it from REST-API (or the VM portal), you might want to change
the configuration of the template in the database:
update vm_static set is_template_sealed='f' where vm_name='';

>
>
>> --
>> 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
>> blanc...@abes.fr
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@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/7VSOFV3TFSMKPEZBI2ERRVUCTFGJALQT/
>>
> --
> 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 14blanc...@abes.fr
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/A5CNQHASI3DHJQ5JJBJUKLCXRSUK3VCJ/

[ovirt-users] Re: Backup prozess

[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 :
>
> 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
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/IPDKXQ747ZNTZPP4WYQCK3FV3TPNKTAQ/

[ovirt-users] Re: Backup prozess

[marcel d'heureuse]

Sure:

https://github.com/vacosta94/VirtBKP


Br
Marcel

Am 14. Februar 2022 20:29:47 MEZ schrieb 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 :
>>
>> 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
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/FMODSHJVW7HFWP6UYKJ5AHIZOVQ4BSMP/

[ovirt-users] Xcp-ng, first impressions as an oVirt HCI alternative

[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 

[ovirt-users] Re: Backup prozess

[Jayme]

vprotect has a decent backup offering for oVirt that would be worth looking
into. It's free for up to 10 VMs to try out.


On Mon, Feb 14, 2022 at 2:53 PM marcel d'heureuse 
wrote:

> 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
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/N2WKXI4VAQFS6S6DJLUHQLZ3LS3I4RUX/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/XF636KSW25ERR5SWDMC75MHLPC7HHBS4/

[ovirt-users] Backup prozess

[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
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/N2WKXI4VAQFS6S6DJLUHQLZ3LS3I4RUX/

[ovirt-users] Re: vm seal

[Nathanaël Blanchet]

Le 14/02/2022 à 17:45, Arik Hadas a écrit :



On Mon, Feb 14, 2022 at 4:52 PM Nathanaël Blanchet  
wrote:


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?


Yes, we do this in order to produce different LVM IDs and machine IDs 
for the provisioned VMs, see: 
https://gerrit.ovirt.org/c/ovirt-engine/+/115009


okay, but, I modified  the 
/usr/lib/python3.6/site-packages/vdsm/virtsysprep.py file like following:


args = ['--hostname', 'localhost', ''--selinux-relabel', '--update', 
'--network']"


in order to update packages on  template creation.

The template creation still works and the template is checked as sealed 
and os is updated, but now the vm creation never ends up and I have to 
manually kill the virt-sysprep process to stop the infinite process 
creation.


I believed it was a good workaround to get updated templates, but I had 
to rollback to default virt-sysprep args configuration, unless there is 
trick do to so?





-- 
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
blanc...@abes.fr
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/7VSOFV3TFSMKPEZBI2ERRVUCTFGJALQT/


--
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
blanc...@abes.fr
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/AHM6OCSBE6DYWRJGUT3ZQLKEMXNQE7S2/

[ovirt-users] Re: How I'd like to contribute

[Strahil Nikolov via Users]

It looks fine, so just ping me if you are still moderated.
Best Regards,Strahil Nikolov
 
 
  On Mon, Feb 14, 2022 at 8:08, Glen Jarvis via Users wrote:   
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/A2DVC5AQCVBE24BZT5YBRDLB67JWZ6ST/
  
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/AGMVY2BXBPQ7KYS2D7DTQCMWLTUPV2QZ/

[ovirt-users] Re: Console - VNC password is 12 characters long, only 8 permitted

[Milan Zamazal]

Francesco Lorenzini  writes:

> Hi Milan,
>
> thank you for your answer.
>
> So there is no other way/workaround? We must wait the fix in the
> engine and then upgrade? Maybe a downgrade of libvirt(?).

I can't think about any other workaround, without modifying sources,
than downgrading libvirt, until the fixed Engine is installed.

> I was looking up some config file in the host under /etc/libvirt and
> found the parameters vnc_password in qemu.conf file. I'm not sure that 
> setting a password per host in this config file works, casue it is
> still passed via xml...

In theory, you could set the default password there and remove passwords
from the domain XMLs using Vdsm hooks.  You would have to do it on all
the hosts or handle migrations accordingly.  Downgrading libvirt looks
much easier.

>> The default VNC password. Only 8 bytes are significant for
>> # VNC passwords. This parameter is only used if the per-domain
>> # XML config does not already provide a password.
>
> Francesco
>
> Il 14/02/2022 12:41, Milan Zamazal ha scritto:
>> francesco--- via Users  writes:
>>
>>> Hi all,
>>>
>>> I'm using websockify + noVNC for expose the vm console via browser getting  
>>> the graphicsconsoles ticket via API. Everything works fine for every other 
>>> host that I have (more than 200), the console works either via oVirt engine 
>>> and via browser) but just for a single host (CentOS Stream release 8, oVirt 
>>> 4.4.9) the console works only via engine but when I try the connection via 
>>> browser I get the following error (vdsm log of the host):
>>>
>>>   ERROR FINISH updateDevice error=unsupported configuration: VNC password 
>>> is 12 characters long, only 8 permitted
>>>   Traceback (most recent call last):
>>> File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 124, 
>>> in method
>>>   ret = func(*args, **kwargs)
>>> File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 372, in 
>>> updateDevice
>>>   return self.vm.updateDevice(params)
>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3389, in 
>>> updateDevice
>>>   return self._updateGraphicsDevice(params)
>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3365, in 
>>> _updateGraphicsDevice
>>>   params['params']
>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5169, in 
>>> _setTicketForGraphicDev
>>>   self._dom.updateDeviceFlags(xmlutils.tostring(graphics), 0)
>>> File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 
>>> 101, in f
>>>   ret = attr(*args, **kwargs)
>>> File 
>>> "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 
>>> 131, in wrapper
>>>   ret = f(*args, **kwargs)
>>> File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 
>>> 94, in wrapper
>>>   return func(inst, *args, **kwargs)
>>> File "/usr/lib64/python3.6/site-packages/libvirt.py", line 3244, in 
>>> updateDeviceFlags
>>>   raise libvirtError('virDomainUpdateDeviceFlags() failed')
>>>   libvirt.libvirtError: unsupported configuration: VNC password is 12 
>>> characters long, only 8 permitted
>>>
>>>
>>> The error is pretty much self explanatory but, I can't manage to
>>> figure out why only on this server
>> Hi,
>>
>> this happens with libvirt 8.0.
>>
>>> and I wonder if I can set the length of the generated vnc password
>>> somewhere.
>> I don't think so, it must be fixed in Engine.  See
>> https://github.com/oVirt/ovirt-engine/commit/a1e7e39348550b575f1f01b701105f9e1066b09f
>> for more details.
>>
>> Regards,
>> Milan
>> ___
>> Users mailing list --users@ovirt.org
>> To unsubscribe send an email tousers-le...@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/XJMULDXFHBYK3GNICAJRASQCSLBIFJV7/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/CE3A2WTEHVE2NPMPYTQS5WAVHEESND4X/

[ovirt-users] VDSM KVM2 command SpmStatusVDS failed: Message timeout which can be caused by communication issues

[Chafik Hammami]

Hello,
Can you please help us to find a solution for this error

VDSM KVM2 command SpmStatusVDS failed: Message timeout which can be caused by 
communication issues

[cid:image001.jpg@01D821CF.F8705D50]


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/GKMYZELLALPIA3FZVJDDFDABXHYYSS4O/

[ovirt-users] Re: Remove obsolete Gluster hyperconverged doc

[Thomas Hoberg]

> Wait a minute.
> 
> Use of GlusterFS as a storage backend is now deperecated and will be
> removed in a future update?
> 
> What are those who's deployments have GlusterFS as their storage
> backend supposed to use as a replacement?
> 
They are to fully understand the opportunities and risks that come from a 
community open source project:
1. Risk: the project can die at any time from lack of support
2. Opportunity: if you help developing a sufficiently great alternative it may 
be taken aboard

> I'm feeling vibes of the SPICE deprecation all over again. but
> moving all of the VM storage data isn't a quick process, and I don't
> want to move it to something else that will also be depercated by a
> future RH whim

If you want to be safe from "a future RH whim" (it's the community, really, and 
your organization is free to invest more than RH), you need to look for or 
create a community where RH is the minority.

In short, it's somewhat unreasonable to expect others to go to unreasonable 
lenghts to support you for free.

But they could have done a much better job at describing just how shaky things 
were.
> 
> -Patrick Hibbs
> 
> On Fri, 2022-02-04 at 08:42 +0100, Sandro Bonazzola wrote:
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/HREYFY7DSVOXTULFUL3KER5BKRYN35XI/

[ovirt-users] VDSM KVM2 command SpmStatusVDS failed: Message timeout which can be caused by communication issues

[c . hammami]

can you please help us. i have 2 KVM with this error
VDSM KVM2 command SpmStatusVDS failed: Message timeout which can be caused by 
communication issues
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/NHLK3WTJL72ERTXIAOPOAZ4KKMF2OVQT/

[ovirt-users] Re: vm seal

[Arik Hadas]

On Mon, Feb 14, 2022 at 4:52 PM Nathanaël Blanchet  wrote:

> 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?
>

Yes, we do this in order to produce different LVM IDs and machine IDs for
the provisioned VMs, see: https://gerrit.ovirt.org/c/ovirt-engine/+/115009


> --
> 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
> blanc...@abes.fr
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/7VSOFV3TFSMKPEZBI2ERRVUCTFGJALQT/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/BPLB4DXKM4L7CYWU4UG47JHKI6BRV35P/

[ovirt-users] Re: oVirt 4.3 - Fibre Channel Data Domain as ISO dump.

[Nir Soffer]

On Mon, Feb 14, 2022 at 4:31 PM Angus Clarke  wrote:
>
> Hello
>
> RE: oVirt 4.3 - Fibre Channel Data Domain as ISO dump.
>
> Thanks for letting me join the list.

Welcome!

> I added a fibre channel Data domain with a view to using it as an ISO dump 
> however I cannot mount CDs to VMs with this error:
>
> "Error while executing action Change CD: Drive image file could not be found"
>
> A bit of reading suggests there is no way around this when using fibre 
> channel data domains - is this the case?

This works since 4.4.6, but was broken in 4.3. You should upgrade to
4.4 at this point.

> I guess I could present the LUN to a VM and run NFS from there as an 
> alternative option.

Yes NFS works for ISO on data domain in 4.3.

Nir
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/EOOGT64SSEMYXDSZAY2SYPTRWX7X4M3H/

[ovirt-users] vm seal

[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
blanc...@abes.fr
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/7VSOFV3TFSMKPEZBI2ERRVUCTFGJALQT/

[ovirt-users] oVirt 4.3 - Fibre Channel Data Domain as ISO dump.

[Angus Clarke]

Hello

RE: oVirt 4.3 - Fibre Channel Data Domain as ISO dump.

Thanks for letting me join the list.

I added a fibre channel Data domain with a view to using it as an ISO dump 
however I cannot mount CDs to VMs with this error:

"Error while executing action Change CD: Drive image file could not be found"

A bit of reading suggests there is no way around this when using fibre channel 
data domains - is this the case?

I guess I could present the LUN to a VM and run NFS from there as an 
alternative option.

Thanks a lot
Angus

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/GS3GJK7JE2STST35TFBHYIEZMMGCCHYU/

[ovirt-users] Centos 8.3 ovirt4.4.5 to Centos Stream 8.6 ovirt 4.4.10 migiration success

[Ismet Sonmez]

Hello everyone
We did a nice update over the weekend. Everything is working fine.
Thank you to the whole team for developing such a project.
Best regards
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/6QM4J7TBCJIDATOIN77KESNALX6JGLQZ/

[ovirt-users] Unable to update self hosted Engine due to missing mirrors

[jonas]

Hi together, 

I already checked the other Threads here :) I know that there was an issue with 
old CentOS 8 repos. 
Currently Im trying so update our self hosted engine as always but I get the 
following error: 

Failed to download metadata for repo 'ovirt-4.4-centos-gluster8': Cannot 
prepare internal mirrorlist: No URLs in mirrorlist

Is there any "official" advise what I have to change in my repo lists? I don't 
want to break something. 

Thank you very much :) 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/JBZQSEJMT2G366RHXGI6LQEJWGNN57C5/

[ovirt-users] Re: Console - VNC password is 12 characters long, only 8 permitted

[Francesco Lorenzini via Users]

Hi Milan,

thank you for your answer.

So there is no other way/workaround? We must wait the fix in the engine 
and then upgrade? Maybe a downgrade of libvirt(?).


I was looking up some config file in the host under /etc/libvirt and 
found the parameters vnc_password in qemu.conf file. I'm not sure that 
setting a password per host in this config file works, casue it is still 
passed via xml...




The default VNC password. Only 8 bytes are significant for
# VNC passwords. This parameter is only used if the per-domain
# XML config does not already provide a password.


Francesco

Il 14/02/2022 12:41, Milan Zamazal ha scritto:

francesco--- via Users  writes:


Hi all,

I'm using websockify + noVNC for expose the vm console via browser getting  the 
graphicsconsoles ticket via API. Everything works fine for every other host 
that I have (more than 200), the console works either via oVirt engine and via 
browser) but just for a single host (CentOS Stream release 8, oVirt 4.4.9) the 
console works only via engine but when I try the connection via browser I get 
the following error (vdsm log of the host):

  ERROR FINISH updateDevice error=unsupported configuration: VNC password is 12 
characters long, only 8 permitted
  Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 124, in 
method
  ret = func(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 372, in 
updateDevice
  return self.vm.updateDevice(params)
File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3389, in 
updateDevice
  return self._updateGraphicsDevice(params)
File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3365, in 
_updateGraphicsDevice
  params['params']
File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5169, in 
_setTicketForGraphicDev
  self._dom.updateDeviceFlags(xmlutils.tostring(graphics), 0)
File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, 
in f
  ret = attr(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", 
line 131, in wrapper
  ret = f(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, 
in wrapper
  return func(inst, *args, **kwargs)
File "/usr/lib64/python3.6/site-packages/libvirt.py", line 3244, in 
updateDeviceFlags
  raise libvirtError('virDomainUpdateDeviceFlags() failed')
  libvirt.libvirtError: unsupported configuration: VNC password is 12 
characters long, only 8 permitted


The error is pretty much self explanatory but, I can't manage to
figure out why only on this server

Hi,

this happens with libvirt 8.0.


and I wonder if I can set the length of the generated vnc password
somewhere.

I don't think so, it must be fixed in Engine.  See
https://github.com/oVirt/ovirt-engine/commit/a1e7e39348550b575f1f01b701105f9e1066b09f
for more details.

Regards,
Milan
___
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-le...@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/XJMULDXFHBYK3GNICAJRASQCSLBIFJV7/


--
--  
Shellrent - Il primo hosting italiano Security First

*Francesco Lorenzini*
/System Administrator & DevOps Engineer/
Shellrent Srl
Via dell'Edilizia, 19 - 36100 Vicenza
Tel. 0444321155  | Fax 04441492177
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/IXZ5I2WT7LHWJYAKA7KWTSKPSBDIX4QK/

[ovirt-users] Re: RHGS and RHV closing down: could you please put that on the home page?

[Thomas Hoberg]

> On Mon, Feb 7, 2022 at 3:04 PM Sandro Bonazzola  wrote:
> 
> 
> The oVirt storage team never worked on HCI and we don't plan to work on
> it in the future. HCI was designed and maintained by Gluster folks. Our
> contribution for HCI was adding 4k support, enabling usage of VDO.
> 
> Improving on the HCI side is unlikely to come from Red Hat, but nothing
> blocks other companies or contributors from working on this.
> 
> Our focus for 4.5 is Managed Block Storage and incremental backup.
> 
> Nir

Hi Nir,

thank you for the clear message and the confirmation of a suspicion that has 
been growing for a while: HCI is an unwanted stepchild, not an equally 
supported option or even a strategic direction.

And it's perhaps not the only one: in the mean-time I can see VDO and the GUIs 
getting neglected, too.

My problem (and that of potentially many others) is that this unbalanced 
attention wasn't communicated or made visible. HCI may have disappeared from 
the oVirt front page today, in fact it's hard to find these days, but it was 
very prominent on 4.3 when I started.

And as a core developer you may not realize this, but the primary first 
exposure to oVirt by many (most?) newcomers isn't the command line. It's the 
Cockpit wizard, where there are two HCI choices next to the one SAN/NAS option 
where evidently 95% of the oVirt teams work went, which doesn't use Gluster, 
HCI, VDO or any of the GUIs.

I was extremely naive to believe you'd only need to click buttons in GUIs to 
run a 3 node HCI VDO cluster, but actually that expectation came from the 
presentation on this site.

And personally I believe that if that had worked, RHV-HCI would be thriving.

But as it turned out, both the setup GUI and the operational GUI rarely ever 
worked, very likely because both were done by yet another team, while you guys 
only worked and tested at the Ansible level and with SAN/NAS storage.

You will say that oVirt is a community project.

I will say that if you advertise oVirt as "designed to manage your entire 
enterprise infrastructure" and put buttons in GUIs, people will take that at 
face value and expect them to work.

I don't know how many oVirt-HCI deployments I did over the years, but for every 
release I've tried since 4.3.5 or so with the Cockpit HCI wizard, none has ever 
just worked. I've had to dig through logfiles all over the place to fix things 
like blacklisted storage, when I was using Gluster. Then there were VDO options 
that weren't supported yet on EL7 in 4.3 ansible scripts, VDO disappearing 
altogether after a kernel upgrade on EL8, Python 2/3 issues and I don't know 
how many other problems, just to get things set up.

I just did a full fresh set of setups with oVirt 4.4.10 when I was testing the 
compatibility of the various downstream EL8 derivatives and it's still the 
same: the Cockpit setup HCI wizard never just works. By now I know where to 
fiddle, but it saps confidence in the product when every release fails the 
basic setup.

I can hear you saying "our CI only tests at script level", can you guess why 
that has an impact on quality?

And it was the same for nearly half of the operations in the oVirt GUI. I went 
through each and every one of them and for startes I often couldn't find out 
what they were supposed to do, while some even looked downright dangerous to 
click (e.g. "reset brick").

Export and import OVA were pure nightmares, because it turned out that the 
exported machines might in fact contain 100GB of zeros instead of the disk 
image. Even once that was fixed, interoperability with other hypervisors 
(that's the purpose of OVA), was zero.

As explanation I was told here that OVA in-/export wasn't really "meant to be 
used", much like HCI I guess.

There is a cluster upgrade button, but I think I only ever hit it once, only to 
notice that it just created more damage and didn't add convenience. In fact 
upgrading any node became an entirely manual job in the end, because it never 
worked. The gluster daemon never started properly after a reboot and resulted 
in ovirt-ha-broker, ovirt-ha-agent and vdsmd sulking, requiring carefully timed 
restarts to get going again.

And then an upgrade procedure for a high-availability HCI from EL7/oVirt 4.3 to 
EL8/oVirt 4.4 that had 40 steps or so, none of which were allowed to fail and 
with no obvious failback just isn't "enterprise".

To my eyes the value proposition of oVirt was "instant on-premise fault 
tolerant cloud", something I could then use to run VMs or indeed OpenShift on.

oVirt never delivered in an enterprise quality and I can't see it getting any 
closer without a downstream product.

Even a community needs a concrete vision, or perhaps at least a few real use 
cases.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 

[ovirt-users] Re: ERROR (mailbox-spm) [storage.MailBox.SpmMailMonitor] mailbox 65 checksum failed, not clearing mailbox, clearing new mail

[Petr Kyselák]

Hi,
thank you for quick reply. It is repeating issue. I file a bug.

https://bugzilla.redhat.com/show_bug.cgi?id=2054209
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/LWT72ISG5NJACF2BMLK4LRKQ3CNUGBIL/

[ovirt-users] Re: Remove obsolete Gluster hyperconverged doc

[less foobar via Users]

I'm currently testing ceph with proxmox. Its taking 50Gb of ram for 21 OSDs so 
yeah lets not compare it to gluster
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/5LPFFWNUFC63QW5UZW36CXGJ2COM7TQ4/

[ovirt-users] Re: Console - VNC password is 12 characters long, only 8 permitted

[Milan Zamazal]

francesco--- via Users  writes:

> Hi all,
>
> I'm using websockify + noVNC for expose the vm console via browser getting  
> the graphicsconsoles ticket via API. Everything works fine for every other 
> host that I have (more than 200), the console works either via oVirt engine 
> and via browser) but just for a single host (CentOS Stream release 8, oVirt 
> 4.4.9) the console works only via engine but when I try the connection via 
> browser I get the following error (vdsm log of the host):
>
>  ERROR FINISH updateDevice error=unsupported configuration: VNC password is 
> 12 characters long, only 8 permitted 
>  Traceback (most recent call last):   
>
>File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 124, in 
> method   
>  ret = func(*args, **kwargs)  
>
>File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 372, in 
> updateDevice
>  return self.vm.updateDevice(params)  
>
>File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3389, in 
> updateDevice   
>  return self._updateGraphicsDevice(params)
>
>File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3365, in 
> _updateGraphicsDevice  
>  params['params'] 
>
>File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5169, in 
> _setTicketForGraphicDev
>  self._dom.updateDeviceFlags(xmlutils.tostring(graphics), 0)  
>
>File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, 
> in f
>  ret = attr(*args, **kwargs)  
>
>File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", 
> line 131, in wrapper
>  ret = f(*args, **kwargs) 
>
>File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, 
> in wrapper  
>  return func(inst, *args, **kwargs)   
>
>File "/usr/lib64/python3.6/site-packages/libvirt.py", line 3244, in 
> updateDeviceFlags 
>  raise libvirtError('virDomainUpdateDeviceFlags() failed')
>
>  libvirt.libvirtError: unsupported configuration: VNC password is 12 
> characters long, only 8 permitted
>
>
> The error is pretty much self explanatory but, I can't manage to
> figure out why only on this server

Hi,

this happens with libvirt 8.0.

> and I wonder if I can set the length of the generated vnc password
> somewhere.

I don't think so, it must be fixed in Engine.  See
https://github.com/oVirt/ovirt-engine/commit/a1e7e39348550b575f1f01b701105f9e1066b09f
for more details.

Regards,
Milan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/XJMULDXFHBYK3GNICAJRASQCSLBIFJV7/

[ovirt-users] Re: ERROR (mailbox-spm) [storage.MailBox.SpmMailMonitor] mailbox 65 checksum failed, not clearing mailbox, clearing new mail

[Nir Soffer]

On Mon, Feb 14, 2022 at 10:51 AM Petr Kyselák  wrote:
>
> Hi,
> I see a lot of errors in vdsm.log
>
> 2022-02-14 08:42:52,086+0100 ERROR (mailbox-spm) 
> [storage.MailBox.SpmMailMonitor] mailbox 65 checksum failed, not clearing 
> mailbox, clearing new mail (data=b'\xff\xff\xff\xff\  \x00\x00', 
> checksum=, expected=b'\xbfG\x00\x00') 
> (mailbox:602)
> 2022-02-14 08:42:52,087+0100 ERROR (mailbox-spm) 
> [storage.MailBox.SpmMailMonitor] mailbox 66 checksum failed, not clearing 
> mailbox, clearing new mail (data=b'\x00\x00\x00\x00\  \xff\xff', 
> checksum=, expected=b'\x04\xf0\x0b\x00') 
> (mailbox:602)

This can be a real checksum error, meaning random failure on storage,
but is more likely a race in ovirt itself. We had lot of these in the past and
I think we fixed them but it is possible that we have more due to the way
this code works.

> We are running latest ovirt engine and hosts:
> Hosts: ovirt-node-ng-installer-4.4.10-2022020214.el8.iso
> engine: ovirt-engine-4.4.10.6-1.el8.noarch
>
> We have 3 hosts and 8 iSCSI domains. I found similar issue from 2018 
> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/FJ6KIEOXEEFFZSJOT2ZF4TRKQ5NCP4OQ/#L7WD2FY25XJCNMB3YMTA4ASKMZGKCDZM
> I am not sure how to determinate which mailbox I should try to "clean". Can 
> anybody help me please?

You don't need to do anything, the mailbox already cleaned up.
This message means that the SPM found bad checksum and drop the
messages in the mailbox.

Processes that sent mail to the SPM will resed dropped mail in 2-3 seconds,
so the issue should be recovered automatically.

I would monitor your logs to check if this is a common issue, or one time
incident. If this error is repeating, please file a vdsm bug and attach complete
log since this host was started.

Nir
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/UJSPPHF4GGFT2JG3QAMWVIVI6XE4LY24/

[ovirt-users] Re: Upgrade CentOS 7 oVirt host to CentOS 8 Stream from backup file - Python error

[Matyi Szabolcs]

The problem is always the same:

[root@ovirt-test ~]# systemctl start ovirt-ha-agent
[root@ovirt-test ~]# systemctl start ovirt-ha-broker
[root@ovirt-test ~]# systemctl stop ovirt-ha-broker
[root@ovirt-test ~]# systemctl stop ovirt-ha-agent
[root@ovirt-test ~]# hosted-engine --reinitialize-lockspace
Traceback (most recent call last):
  File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/reinitialize_lockspace.py",
 line 30, in 
ha_cli.reset_lockspace(force)
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/client/client.py", 
line 286, in reset_lockspace
stats = broker.get_stats_from_storage()
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", 
line 148, in get_stats_from_storage
result = self._proxy.get_stats()
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in __call__
return self.__send(self.__name, args)
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request
verbose=self.__verbose
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1154, in request
return self.single_request(host, handler, request_body, verbose)
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1166, in single_request
http_conn = self.send_request(host, handler, request_body, verbose)
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1279, in send_request
self.send_content(connection, request_body)
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1309, in send_content
connection.endheaders(request_body)
  File "/usr/lib64/python3.6/http/client.py", line 1268, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib64/python3.6/http/client.py", line 1044, in _send_output
self.send(msg)
  File "/usr/lib64/python3.6/http/client.py", line 982, in send
self.connect()
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py", line 
76, in connect
self.sock.connect(base64.b16decode(self.host))
FileNotFoundError: [Errno 2] No such file or directory
[root@ovirt-test ~]# 


[root@ovirt-test ~]# python3 -V
Python 3.6.8



Regards!
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/OTKBLWDHPIGDRXWM2AZLO2T3NTMX7AOY/

[ovirt-users] Console - VNC password is 12 characters long, only 8 permitted

[francesco--- via Users]

Hi all,

I'm using websockify + noVNC for expose the vm console via browser getting  the 
graphicsconsoles ticket via API. Everything works fine for every other host 
that I have (more than 200), the console works either via oVirt engine and via 
browser) but just for a single host (CentOS Stream release 8, oVirt 4.4.9) the 
console works only via engine but when I try the connection via browser I get 
the following error (vdsm log of the host):

 ERROR FINISH updateDevice error=unsupported configuration: VNC password is 12 
characters long, only 8 permitted 
 Traceback (most recent call last): 
 
   File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 124, in 
method   
 ret = func(*args, **kwargs)
 
   File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 372, in 
updateDevice
 return self.vm.updateDevice(params)
 
   File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3389, in 
updateDevice   
 return self._updateGraphicsDevice(params)  
 
   File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 3365, in 
_updateGraphicsDevice  
 params['params']   
 
   File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5169, in 
_setTicketForGraphicDev
 self._dom.updateDeviceFlags(xmlutils.tostring(graphics), 0)
 
   File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, in 
f
 ret = attr(*args, **kwargs)
 
   File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", 
line 131, in wrapper
 ret = f(*args, **kwargs)   
 
   File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in 
wrapper  
 return func(inst, *args, **kwargs) 
 
   File "/usr/lib64/python3.6/site-packages/libvirt.py", line 3244, in 
updateDeviceFlags 
 raise libvirtError('virDomainUpdateDeviceFlags() failed')  
 
 libvirt.libvirtError: unsupported configuration: VNC password is 12 characters 
long, only 8 permitted


The error is pretty much self explanatory but, I can't manage to figure out why 
only on this server and I wonder if I can set the length of the generated vnc 
password somewhere.

Thank you for your time,
Francesco
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/HIBAN3JJHJYRWEN7UVFIRB57URLYWEFJ/

[ovirt-users] ERROR (mailbox-spm) [storage.MailBox.SpmMailMonitor] mailbox 65 checksum failed, not clearing mailbox, clearing new mail

[Petr Kyselák]

Hi, 
I see a lot of errors in vdsm.log

2022-02-14 08:42:52,086+0100 ERROR (mailbox-spm) 
[storage.MailBox.SpmMailMonitor] mailbox 65 checksum failed, not clearing 
mailbox, clearing new mail (data=b'\xff\xff\xff\xff\  \x00\x00', 
checksum=, expected=b'\xbfG\x00\x00') 
(mailbox:602)
2022-02-14 08:42:52,087+0100 ERROR (mailbox-spm) 
[storage.MailBox.SpmMailMonitor] mailbox 66 checksum failed, not clearing 
mailbox, clearing new mail (data=b'\x00\x00\x00\x00\  \xff\xff', 
checksum=, expected=b'\x04\xf0\x0b\x00') 
(mailbox:602)

We are running latest ovirt engine and hosts:
Hosts: ovirt-node-ng-installer-4.4.10-2022020214.el8.iso
engine: ovirt-engine-4.4.10.6-1.el8.noarch

We have 3 hosts and 8 iSCSI domains. I found similar issue from 2018 
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/FJ6KIEOXEEFFZSJOT2ZF4TRKQ5NCP4OQ/#L7WD2FY25XJCNMB3YMTA4ASKMZGKCDZM
I am not sure how to determinate which mailbox I should try to "clean". Can 
anybody help me please?

I observed the issue prior we upgraded to v4.4 (I hoped the upgrade will fix 
it, but it does not)
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/R3WZQRAA26GIGAJ6F2LUPJCKPXVVFVTQ/

[ovirt-users] Re: Remove obsolete Gluster hyperconverged doc

[Leo David]

HCI architectured virtualisation enviroments provide quite a lot of
benefits for different implementation scenarios. From rought point of view,
they combine 3 main components in horizontal scaling out fashion ( compute,
storage, networking)
As a starting point, i think you may want to have a look on this:
https://storpool.com/blog/is-hyper-converged-infrastructure-what-you-need/

Regards,

Leo


On Mon, Feb 14, 2022, 08:00 Pascal DeMilly  wrote:

> What advantages does ovirt in hyperconerge mode offer over using glusterfs
> on a separate stack unrelated to orvirt except as a domain storage? I am
> looking into moving our NFS server to a distributed redundant solution.
> What is the best, most reliable, fastest solution I could build that ovirt
> can use but doesn't manage or is it necessary to let ovirt manage its
> domains as well
>
> TIA
>
> On Sun, Feb 13, 2022 at 3:00 PM Strahil Nikolov via Users 
> wrote:
>
>> I'm not so sure. Usually Gluster is used in Hyperconverged scenarios.
>> CEPH is more damanding and I would calculate my reaources several times
>> before considering it in Hyperconverged.
>>
>> Best Regards,
>> Strahil Nikolov
>>
>> On Mon, Feb 14, 2022 at 0:01, Leo David
>>  wrote:
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@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/KEA2VRL76ELF74SXHDIIG7VMNC5NXJ2I/
>>
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@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/Q3BDSSGI5YUJJVN5UY5XJIG46MQXDU6T/
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/6R3NNBDKIEW5BRRQ7HTSQKFTP5MYWMRN/