oVirt Testing
-
Great job testing @Tim_G
I'll try to do the same this weekend so we can compare notes.
FYI: oVirt is a 1st class citizen within the vProtect Storware backup world.
-
Did you install on CentOS?
-
@fateknollogee said in oVirt Testing:
Did you install on CentOS?
Pretty sure that he mentioned CentOS 7 in a post.
-
I'm excited about how this is looking. Certainly could be a huge deal for moving Hyper-V to the back seat.
-
@scottalanmiller said in oVirt Testing:
I'm excited about how this is looking. Certainly could be a huge deal for moving Hyper-V to the back seat.
Not to thread jack, but maybe we can have a standardized format/layout when we do this types of testing
@Tim_G I like the titleHardware:
Networking:
Management:
BackUp:Something that makes it easy for us to use it as reference material.
Sorry @Tim_G feel free to re-start this if my idea is any good
-
@fateknollogee said in oVirt Testing:
Did you install on CentOS?
Yes I installed manually with the latest release of CentOS NetInstall ISO, I think 1708.
I selected the Hypervisor install on the left, and checked a few related ones on the right such as NFS client.
I am using an NFS4 share on the hypervisor for testing everything. Only had one server so my options were limited. Gonna try to get 2 more for a real production-like test.
-
@tim_g said in oVirt Testing:
I selected the Hypervisor install on the left, and checked a few related ones on the right such as NFS client.
I'm not even sure you need to do that, as the oVirt stuff you install to make it an oVirt node probably installs that stuff anyways. Gonna try just a straight minimal install on the next node.
-
I tried using the "oVirt Node" ISO install, but didn't work. I think that was my fault due to not precreating a DNS record.
I liked doing it manually more anyways.
-
@scottalanmiller said in oVirt Testing:
I'm excited about how this is looking. Certainly could be a huge deal for moving Hyper-V to the back seat.
It's immediately more useful than just Hyper-V.
It's like having SCVMM but on a more reliable platform. At least it feels that way so far, but I haven't pushed it like I have with Hyper-V so I guess I can give it the benefit of the doubt for now.
I've done quite a bit with SCVMM so I know what I'm talking about. I'm not saying SCVMM is bad... but it's not free.
I've yet to test the full HA capabilities in oVirt using local storage. I assume it will go well and as expected because its glusterfs.
Yeah, I'm going to push it hard in a production-like environment.
-
More i look at these the more I want to play with KVM..... Job for Monday sort my one spare server out lol
-
@tim_g
How hard was it to set it up without DNS records and login to it using direct IP ? and are you noticing any weird problems like slow to load or to refresh + disconnecting items and is this the BETA ?
-
@emad-r said in oVirt Testing:
@tim_g
How hard was it to set it up without DNS records and login to it using direct IP ? and are you noticing any weird problems like slow to load or to refresh + disconnecting items and is this the BETA ?
It's easy to set up.
It requires FQDNs, so if you don't have a DNS server, the entry needs to be in the /etc/hosts file prior to setup for the oVirtEngine.
It is not Beta anything. oVirt has been around for a very long time. The interface and everything is production ready.
-
@tim_g said in oVirt Testing:
@emad-r said in oVirt Testing:
@tim_g
How hard was it to set it up without DNS records and login to it using direct IP ? and are you noticing any weird problems like slow to load or to refresh + disconnecting items and is this the BETA ?
It's easy to set up.
It requires FQDNs, so if you don't have a DNS server, the entry needs to be in the /etc/hosts file prior to setup for the oVirtEngine.
It is not Beta anything. oVirt has been around for a very long time. The interface and everything is production ready.
I see, i meant this when I meant BETA:
https://ovirt.org/
https://ovirt.org/blog/2017/09/introducing-ovirt-4.2.0/ -
@emad-r said in oVirt Testing:
@tim_g said in oVirt Testing:
@emad-r said in oVirt Testing:
@tim_g
How hard was it to set it up without DNS records and login to it using direct IP ? and are you noticing any weird problems like slow to load or to refresh + disconnecting items and is this the BETA ?
It's easy to set up.
It requires FQDNs, so if you don't have a DNS server, the entry needs to be in the /etc/hosts file prior to setup for the oVirtEngine.
It is not Beta anything. oVirt has been around for a very long time. The interface and everything is production ready.
I see, i meant this when I meant BETA:
https://ovirt.org/
https://ovirt.org/blog/2017/09/introducing-ovirt-4.2.0/No I'm using 4.1.
-
I’m curious to see how it works. It was slow (compared to bare KVM) the last time I tried it.
-
@stacksofplates said in oVirt Testing:
I’m curious to see how it works. It was slow (compared to bare KVM) the last time I tried it.
I haven't noticed any difference on VMs versus HyperV or straight KVM.
But I've a lot more testing to do, so we'll see. I'll keep that in mind.
-
As soon as my current desktop is migrated to my new machine, I will be spinning it back up as a KVM server. I will give oVirt a go for that.
-
@tim_g said in oVirt Testing:
@stacksofplates said in oVirt Testing:
I’m curious to see how it works. It was slow (compared to bare KVM) the last time I tried it.
I haven't noticed any difference on VMs versus HyperV or straight KVM.
But I've a lot more testing to do, so we'll see. I'll keep that in mind.
It wasn’t VM performance, it was things like cloning and provisioning.
-
@jaredbusch said in oVirt Testing:
As soon as my current desktop is migrated to my new machine, I will be spinning it back up as a KVM server. I will give oVirt a go for that.
You'll be required to have dual nics.
-
@dustinb3403 said in oVirt Testing:
@jaredbusch said in oVirt Testing:
As soon as my current desktop is migrated to my new machine, I will be spinning it back up as a KVM server. I will give oVirt a go for that.
You'll be required to have dual nics.
I'm only using one NIC. I know it works because that test VM in my screenshot was installed via PXE (WDS server)
