cant edit ISO domain in any way
by Philip Brown
oVirt 4.3: Okay, I found documentation that I cant have more than one "ISO" type storage domain.
I can kinda understand that.
But, I cant even edit or delete the existing one?
Even when logged in to the oVirt GUI as admin@internal?
Is this some kind of bug or something?
3 years, 10 months
Information requested on oVirt + RDO/OpenStack
by Glenn Marcy
I am hoping to try out adding RDO to oVirt after things with CentOS 8.2 settle down. I've done deployments of RDO on KVM before without any issues (TripleO Quickstart), but this would be my first time trying it on oVirt.
Since oVirt recently updated to the openstack-java 3.2.9 packages, is there a specific version of OpenStack (Train or Ussuri) that runs on CentOS 8.x that I need? Are there any issues with the fact that oVirt already uses and/or provides some OpenStack services? Does the fact that OpenStack deployments are now more "containerized" present any issues I should be aware of?
Are there initiatives for further convergence between oVirt, RDO/OpenStack and OKD/OCP that are changing this space where it would make sense to follow and/or participate in those efforts?
I'm starting out with oVirt to get an understanding of the capabilities that it brings to the table, but interested in the convergence of the other technologies that would benefit from having oVirt as, or a part of, the foundation.
Best Regards,
Glenn
3 years, 10 months
Ansible ovirt_disk module: how to attach disk without activation
by Gianluca Cecchi
Hello,
root problem in a 4.3.8 environment is that sometimes when I hot add a
floating disk to a VM in web admin gui, it attaches and also activates it
by default (the flag is checked by default, but you can uncheck it) and
this two-phases action fails as a single step.
What I get is:
VDSM ovhost command HotPlugDiskVDS failed: Requested operation is not
valid: Domain already contains a disk with that address
And then the VM event regarding hot add disk failure.
I'm going to investigate more: it should be a past bug already solved in
theory by my libvirt sw version (I've to crosscheck its id)... but I still
get the error sometimes.
What programmatically works is to attach the disk without activating it
(this step always completes with success) and then activate the disk as a
separate operation (this one typically fails the first time when I have the
"problematic" situation, but then the second time succeeds).
So I would like to use it as a workaround in the mean time.
The problem reflects using the ansible module ovirt_disk, that by default
activates the disk. So I have tried to specify "activate: no" (introduced
in 2.8, readings the docs) when I attach it, but it seems not to work as
expected.
I'm testing using awx and its info says:
AWX 9.0.1.0
Ansible 2.8.5
I tried this on a VM that (as usual when you want to reproduce... ;-)
doesn't show the problem:
ovirt_disk:
auth: "{{ ovirt_auth }}"
state: attached
activate: no
name: "{{ tobe_sw_disk_name }}"
vm_name: "{{ ansible_hostname }}"
size: "{{ current_sw_disk_size }}"
interface: virtio_scsi
delegate_to: localhost
register: disk_attach_info
But going to see registered variable it contains "active: true":
"disk_activate_info": {
"changed": false,
"id": "6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827",
"diskattachment": {
"href":
"/ovirt-engine/api/vms/b5c67c93-bd5d-42b6-a873-05f69cece2f1/diskattachments/6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827",
"id": "6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827",
"active": true,
"bootable": false,
"disk": {
....
In fact I followed with the step to activate the disk:
ovirt_disk:
auth: "{{ ovirt_auth }}"
state: present
activate: yes
name: "{{ tobe_sw_disk_name }}"
vm_name: "{{ ansible_hostname }}"
size: "{{ current_sw_disk_size }}"
interface: virtio_scsi
delegate_to: localhost
register: disk_activate_info
But in playbook run I got:
ok: [target_vm -> localhost]
And inside registered variable "changed: false":
"disk_activate_info": {
"changed": false,
"id": "6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827",
"diskattachment": {
"href":
"/ovirt-engine/api/vms/b5c67c93-bd5d-42b6-a873-05f69cece2f1/diskattachments/6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827",
"id": "6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827",
"active": true,
...
Any tip to realize what needed: task to only attach disk without activating
it and then task to activate the disk?
Thanks in advance,
Gianluca
3 years, 10 months
Re: New VM from Template and Storage size
by Eyal Shenitzky
Hi Erez,
This sounds like a nice RFE.
Can you please submit it to Bugzilla -
https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine ?
In the title add in the beginning - [RFE] ...
Thanks.
On Wed, 17 Jun 2020 at 08:24, Erez Zarum <erezz(a)nanosek.com> wrote:
> It is reasonable flow that you inherit the configuration from the
> template, but you can change most of the settings during the creation of
> the VM, I just don't understand why not to be able to change the disk size
> and name.
> Why disk size? You can say the same thing with any other settings, so just
> make a template for any different setting you need for different VMs based
> on that same OS.
> This flow of changing the disk size is supported in any other platforms
> take a few, OpenStack, VMWare, Xen and any other Cloud providers.
> I don't see a reason why to do this in two API calls, one for VM creation
> and then another one for just expanding the disk size.
> I do understand if you create a VM based on a thin template which is just
> a link that there's no other way.
> Another "issue" is that it creates the new of the new disk for the VM
> based on the template name instead of "vmname_Disk1" etc...
> I have a customer with many different disk sizes, varying from 50GB up to
> 200GB, If I go and create a template for an OS based on that, I will
> probably have 10 templates, it's not scalable if you need to just modify
> something in the template as well.
>
> So the only option right now is to use OpenStack Glance for saving images
> or create a new feature in Foreman/Satelite for that.
>
> On 16/06/2020, 20:53, "Nir Soffer" <nsoffer(a)redhat.com> wrote:
>
> On Tue, Jun 16, 2020 at 5:32 PM Erez Zarum <erezz(a)nanosek.com> wrote:
> >
> > Hey,
> >
> > I have created a template that the disk is a thick (raw) with a size
> of 15GB.
> >
> > I am trying to create a VM from that template but having the disk
> with a much larger size, both template and the VM are set to use thick and
> I create the new VM with the clone option, so there’s no link between the
> new VM and the template.
> >
> > So far the only solution I managed to find is to adjust the size
> after creating the VM.
>
> This looks like reasonable flow. You create the vm from a template, so
> you inherit the
> disk size from the template. Then you modify the disk to the required
> size.
>
> > For example, this situation causes a problematic step when using
> Foreman/Satelite as trying to provision a VM based on a template but with
> different size for the OS disk.
>
> Why is this problematic?
>
> > I assume that one of the ways to solve it is to convert the template
> somehow into an “image”? like using OpenStack Glance as a place to store
> “templates” as images? Any other way besides using Glance?
>
> If you always need to resize the template, why not create another
> templated with the right
> size based on this template?
>
> Nir
>
> _______________________________________________
> 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/46IFRJCTZNZ...
>
--
Regards,
Eyal Shenitzky
3 years, 10 months
Re: New VM from Template and Storage size
by Nir Soffer
On Tue, Jun 16, 2020 at 5:32 PM Erez Zarum <erezz(a)nanosek.com> wrote:
>
> Hey,
>
> I have created a template that the disk is a thick (raw) with a size of 15GB.
>
> I am trying to create a VM from that template but having the disk with a much larger size, both template and the VM are set to use thick and I create the new VM with the clone option, so there’s no link between the new VM and the template.
>
> So far the only solution I managed to find is to adjust the size after creating the VM.
This looks like reasonable flow. You create the vm from a template, so
you inherit the
disk size from the template. Then you modify the disk to the required size.
> For example, this situation causes a problematic step when using Foreman/Satelite as trying to provision a VM based on a template but with different size for the OS disk.
Why is this problematic?
> I assume that one of the ways to solve it is to convert the template somehow into an “image”? like using OpenStack Glance as a place to store “templates” as images? Any other way besides using Glance?
If you always need to resize the template, why not create another
templated with the right
size based on this template?
Nir
3 years, 10 months
Re: oVirt noVNC
by Anton Louw
Hi Paul,
Apologies for the late response.
So we only have a cert bundle on the one that is currently not working. The env that is working still has all the default certs.
Thanks
Anton Louw
Cloud Engineer: Storage and Virtualization
______________________________________
D: 087 805 1572 | M: N/A
A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg
anton.louw(a)voxtelecom.co.za
www.vox.co.za
From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk>
Sent: 12 June 2020 13:13
To: Anton Louw <Anton.Louw(a)voxtelecom.co.za>; users(a)ovirt.org
Subject: Re: oVirt noVNC
Sorry Anton,
I'm trying to get a lot of things sorted before the weekend.
This seems the wrong way round, if you follow the documentation you shouldn't have the symbolic link on the working system unless you replaced the file it was pointing to.
Do you have certificate bundles for both systems?
Regards,
Paul S.
________________________________
From: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>>
Sent: 12 June 2020 11:44
To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>>; users(a)ovirt.org<mailto:users@ovirt.org> <users(a)ovirt.org<mailto:users@ovirt.org>>
Subject: RE: oVirt noVNC
Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
Thanks Paul,
So the symbolic link has then been removed, as per the below. Not quite sure where to go from here.
Anton Louw
Cloud Engineer: Storage and Virtualization at Vox
________________________________
T: 087 805 0000 | D: 087 805 1572
M: N/A
E: anton.louw(a)voxtelecom.co.za<mailto:anton.louw@voxtelecom.co.za>
A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg
www.vox.co.za<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vox....>
[F]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fac...>
[T]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.twi...>
[I]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ins...>
[L]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.lin...>
[Y]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.you...>
From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>>
Sent: 12 June 2020 12:30
To: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>>; users(a)ovirt.org<mailto:users@ovirt.org>
Subject: Re: oVirt noVNC
Yes Anton,
I think it's in the documentation it's
Steps 2 & 3
•
• The Engine has been configured to use /etc/pki/ovirt-engine/apache-ca.pem, which is symbolically linked to /etc/pki/ovirt-engine/ca.pem. Remove the symbolic link.
# rm /etc/pki/ovirt-engine/apache-ca.pem
• Save your CA certificate as /etc/pki/ovirt-engine/apache-ca.pem.
# cp /tmp/3rd-party-ca-cert.pem /etc/pki/ovirt-engine/apache-ca.pem
Regards,
Paul S.
________________________________
From: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>>
Sent: 12 June 2020 11:06
To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>>; users(a)ovirt.org<mailto:users@ovirt.org> <users(a)ovirt.org<mailto:users@ovirt.org>>
Subject: RE: oVirt noVNC
Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
Hi Paul,
Double checked the permissions as well. All seems to be fine. The only thing that does look different between the environments are the below:
ENV1 (Not working)
[cid:image008.png@01D64474.A4312E70]
ENV2 (Working)
[cid:image009.png@01D64474.A4312E70]
It seems that on the working environment, there is a shortcut file (apached-ca.pem) which points to the ca.pem file, but on the environment that is not working, the apache-ca.pem file is not a shortcut. Could this perhaps be an issue?
Thanks
Anton Louw
Cloud Engineer: Storage and Virtualization at Vox
________________________________
T: 087 805 0000 | D: 087 805 1572
M: N/A
E: anton.louw(a)voxtelecom.co.za<mailto:anton.louw@voxtelecom.co.za>
A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg
www.vox.co.za<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vox....>
[F]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fac...>
[T]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.twi...>
[I]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ins...>
[L]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.lin...>
[Y]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.you...>
From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>>
Sent: 12 June 2020 10:44
To: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>>; users(a)ovirt.org<mailto:users@ovirt.org>
Subject: Re: oVirt noVNC
No worries,
If all is pointing to the correct files I would check permissions.
Regards,
Paul S.
________________________________
From: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>>
Sent: 12 June 2020 09:34
To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>>; users(a)ovirt.org<mailto:users@ovirt.org> <users(a)ovirt.org<mailto:users@ovirt.org>>
Subject: RE: oVirt noVNC
Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
Hi Paul,
Thanks for the reply. Apologies, I should have added that I have installed our own certificates. The main problem I am facing is that the noVNC console just refuses to open, I get the attached error with any VM I try and access. I should have perhaps started with this issue in my first mail, apologies 😊
Thanks
Anton Louw
Cloud Engineer: Storage and Virtualization at Vox
________________________________
T: 087 805 0000 | D: 087 805 1572
M: N/A
E: anton.louw(a)voxtelecom.co.za<mailto:anton.louw@voxtelecom.co.za>
A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg
www.vox.co.za<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vox....>
[F]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fac...>
[T]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.twi...>
[I]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ins...>
[L]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.lin...>
[Y]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.you...>
From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>>
Sent: 12 June 2020 10:29
To: users(a)ovirt.org<mailto:users@ovirt.org>; Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>>
Subject: Re: oVirt noVNC
Hello Anton,
if your organisation has it's own CA you can install your own certificates or get certificates from a trusted CA.
https://www.ovirt.org/documentation/admin-guide/appe-oVirt_and_SSL.html<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi...>
Paul S.
________________________________
From: Anton Louw via Users <users(a)ovirt.org<mailto:users@ovirt.org>>
Sent: 12 June 2020 08:56
To: users(a)ovirt.org<mailto:users@ovirt.org> <users(a)ovirt.org<mailto:users@ovirt.org>>
Subject: [ovirt-users] oVirt noVNC
Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.
Hi Everybody,
With regards to noVNC, is it a requirement to install the CA into your local browser? I would like users to access their VM console, but with no additional work from their side, ie. Downloading the CA and importing it.
Thank you
Anton Louw
Cloud Engineer: Storage and Virtualization at Vox
________________________________
T: 087 805 0000 | D: 087 805 1572
M: N/A
E: anton.louw(a)voxtelecom.co.za<mailto:anton.louw@voxtelecom.co.za>
A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg
www.vox.co.za<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vox....>
[F]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fac...>
[T]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.twi...>
[I]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ins...>
[L]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.lin...>
[Y]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.you...>
[#VoxBrand]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.vox...>
Disclaimer
The contents of this email are confidential to the sender and the intended recipient. Unless the contents are clearly and entirely of a personal nature, they are subject to copyright in favour of the holding company of the Vox group of companies. Any recipient who receives this email in error should immediately report the error to the sender and permanently delete this email from all storage devices.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more Click Here<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.vox...>.
To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/<http://leedsbeckett.ac.uk/disclaimer/email/>
To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/<http://leedsbeckett.ac.uk/disclaimer/email/>
To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/<http://leedsbeckett.ac.uk/disclaimer/email/>
To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/<http://leedsbeckett.ac.uk/disclaimer/email/>
3 years, 10 months
help: renamed master volume
by Philip Brown
Im pretty new to ovirt. Trying to upgrade an old install from 4.1 to 4.3
on the way, I browsed into the Storage area, in one of the nodes.
Noticed under the "Volume groups", area that the volumes were named after some loong ID string.
Saw there was a "rename" button.
figured it would be just like renaming a VM. thigns would just get auto adjusted.
but after I renamed to something in english, the cluster is freaking out,
"cant find master domain: u'spUUID=xxxxxxx, msdUUID=xxxxxxx' "
and under Storage: Storage DOmains, the Data(Master) is down.
How can I recover from this ASAP? :-(
3 years, 10 months
New VM from Template and Storage size
by Erez Zarum
Hey,
I have created a template that the disk is a thick (raw) with a size of 15GB.
I am trying to create a VM from that template but having the disk with a much larger size, both template and the VM are set to use thick and I create the new VM with the clone option, so there’s no link between the new VM and the template.
So far the only solution I managed to find is to adjust the size after creating the VM.
For example, this situation causes a problematic step when using Foreman/Satelite as trying to provision a VM based on a template but with different size for the OS disk.
I assume that one of the ways to solve it is to convert the template somehow into an “image”? like using OpenStack Glance as a place to store “templates” as images? Any other way besides using Glance?
Thanks!
3 years, 10 months
oVirt 4.4 Self-hosted Engine and Intel Skylake CPUs
by Erez Zarum
Hey,
I was trying to install oVirt with SE on a node that has Intel Skylake CPU
(Intel Xeon Gold 6238R CPU to be precise) which by Intel supports TSX.
When the SE was provisioned as a local VM all was working well, it was
using a different CPU type for local provisioning.
After the local SE VM was migrated to the shared Storage (iSCSI) and was
configured, it failed to start.
When checking the XML (and vm.conf) that was created and provided to
libvirt I noticed it uses the "Secure Intel Skylake" type CPU
with +tsx-ctrl as a required flag.
My assumption as this is a fresh install of oVirt with SE is that the newly
created Cluster was set to this CPU compatibility.
This specific CPU by Intel does not expose any tsx flags, while it does
indeed support TSX libvirt has no way of knowing it, more strange, some
other CPUs from that same range/models do expose the tsx flag.
I have tried to set the kernel cmdline to tsx=yes|auto|off and none of
those helped.
The quick solution was to start the engine manually by editing the XML file
(hosted-engine --vm-shutdown and then start it with libvirt) and change the
Cluster CPU type and the HostedEngine CPU type as well to "Intel Skylake"
and then start it (hosted-engine --vm-start)
Another solution which i haven't tried is to get the correct string from
the oVirt-Engine API of the non-secure Intel Skylake CPU and hardcode it
into the cpu_model fact in the SE ansible role (task).
At the end i opted not to try any workaround and decided to go on with
oVirt 4.3 which went smooth, it chose "Intel Skylake Server IBRS SSBD MDS
Family" as the Cluster CPU compatibility and installation went without any
errors/issues.
1) What will happen if i decide to upgrade to 4.4? I will first have to
reinstall a node with CentOS 8 and then migrate the HostedEngine to there
as well, will it keep the current cluster CPU type or will it try to
upgrade and these fail the upgrade?
2) Are you aware of this situation? I understand this is a new solution
because you had to update everytime the CPU databases but on the other
hand, Intel is not helping here by not being strict about exposing the tsx
flags, perhaps the best will be to let the user chose which CPU type use on
the first Cluster created by the SE ansible role? (As far as i remember,
this was available in the previous versions of oVirt)
Thanks!
3 years, 10 months
oVirt-4.4 on CetOS 8.2
by Dominik Holler
Hello,
CentOS 8.2 was released before oVirt was prepared for CentOS 8.2 .
Currently oVirt-4.4 fails to install on CentOS 8.2 .
This will be fixed soon.
Dominik
3 years, 10 months
