Testing oVirt...
-
@dyasny said in Testing oVirt...:
@scottalanmiller said in Testing oVirt...:
@dyasny said in Testing oVirt...:
NT is what killed it.
Yeah, Netware on DR-DOS was very.... aged by that point.
Why DRDOS? NWDOS-7 was great, it could even do multithreading and networking
LOL...
-
@dyasny said in Testing oVirt...:
Why DRDOS? NWDOS-7 was great, it could even do multithreading and networking
NWDos was just a rebranding. Still DR-DOS.
-
@scottalanmiller said in Testing oVirt...:
@dyasny said in Testing oVirt...:
Why DRDOS? NWDOS-7 was great, it could even do multithreading and networking
NWDos was just a rebranding. Still DR-DOS.
oh I know, but Novell added the networking stack in there, and iirc the multitasking was also developed in cooperation with Novell
-
@dyasny said in Testing oVirt...:
oh I know, but Novell added the networking stack in there, and iirc the multitasking was also developed in cooperation with Novell
Well, no one else was going to invest in DR-DOS. Jajaja
-
@scottalanmiller LOL
-
For folks that might be interested in kicking the tires, here's a nice summary:
https://www.redhat.com/en/blog/red-hat-virtualization-43-quick-start -
@FATeknollogee said in Testing oVirt...:
For folks that might be interested in kicking the tires, here's a nice summary:
https://www.redhat.com/en/blog/red-hat-virtualization-43-quick-startHow long until these are pushed down stream?
-
@DustinB3403 said in Testing oVirt...:
@FATeknollogee said in Testing oVirt...:
For folks that might be interested in kicking the tires, here's a nice summary:
https://www.redhat.com/en/blog/red-hat-virtualization-43-quick-startHow long until these are pushed down stream?
RHV-H/RHV-M are the downstream.
-
@FATeknollogee said in Testing oVirt...:
@DustinB3403 said in Testing oVirt...:
@FATeknollogee said in Testing oVirt...:
For folks that might be interested in kicking the tires, here's a nice summary:
https://www.redhat.com/en/blog/red-hat-virtualization-43-quick-startHow long until these are pushed down stream?
RHV-H/RHV-M are the downstream.
Oh
-
@FATeknollogee said in Testing oVirt...:
@DustinB3403 said in Testing oVirt...:
@FATeknollogee said in Testing oVirt...:
For folks that might be interested in kicking the tires, here's a nice summary:
https://www.redhat.com/en/blog/red-hat-virtualization-43-quick-startHow long until these are pushed down stream?
RHV-H/RHV-M are the downstream.
Of oVirt? Yeah, I think we get the features in oVirt first. So anyone on oVirt likely had that stuff already.
-
@DustinB3403 said in Testing oVirt...:
@FATeknollogee said in Testing oVirt...:
@DustinB3403 said in Testing oVirt...:
@FATeknollogee said in Testing oVirt...:
For folks that might be interested in kicking the tires, here's a nice summary:
https://www.redhat.com/en/blog/red-hat-virtualization-43-quick-startHow long until these are pushed down stream?
RHV-H/RHV-M are the downstream.
Oh
@DustinB3403 Curious, are you an RHV user (aka subscriber)?
-
@FATeknollogee said in Testing oVirt...:
@DustinB3403 said in Testing oVirt...:
@FATeknollogee said in Testing oVirt...:
@DustinB3403 said in Testing oVirt...:
@FATeknollogee said in Testing oVirt...:
For folks that might be interested in kicking the tires, here's a nice summary:
https://www.redhat.com/en/blog/red-hat-virtualization-43-quick-startHow long until these are pushed down stream?
RHV-H/RHV-M are the downstream.
Oh
@DustinB3403 Curious, are you an RHV user (aka subscriber)?
I'm not.
-
@scottalanmiller What's the backend storage on your oVirt install, NFS, Gluster, iSCSI?
-
@FATeknollogee said in Testing oVirt...:
@scottalanmiller What's the backend storage on your oVirt install, NFS, Gluster, iSCSI?
We decided not to use oVirt. But if we were, none of those would make sense. We are using virt-manager and local storage basically everywhere.
-
@scottalanmiller said in Testing oVirt...:
@FATeknollogee said in Testing oVirt...:
@scottalanmiller What's the backend storage on your oVirt install, NFS, Gluster, iSCSI?
We decided not to use oVirt. But if we were, none of those would make sense. We are using virt-manager and local storage basically everywhere.
Can you say why you decided not to use?
-
@FATeknollogee said in Testing oVirt...:
@scottalanmiller said in Testing oVirt...:
@FATeknollogee said in Testing oVirt...:
@scottalanmiller What's the backend storage on your oVirt install, NFS, Gluster, iSCSI?
We decided not to use oVirt. But if we were, none of those would make sense. We are using virt-manager and local storage basically everywhere.
Can you say why you decided not to use?
Yeah, way too much overhead and complexity. It make simple tasks hard and it is totally focused on clustering which rarely has any place in the SMB. Deploying it was a huge headache. Had some neat features, but none that we cared about. We ran into some issues with it that were enough that we questioned the logic of trying to use it.
Tested virt-manager instead and it was flexible, simple, and worked perfectly, instantly. The real thing was that in the end oVirt just offered nothing of particular value, but had a lot of negatives.
-
@scottalanmiller said in Testing oVirt...:
@FATeknollogee said in Testing oVirt...:
@scottalanmiller said in Testing oVirt...:
@FATeknollogee said in Testing oVirt...:
@scottalanmiller What's the backend storage on your oVirt install, NFS, Gluster, iSCSI?
We decided not to use oVirt. But if we were, none of those would make sense. We are using virt-manager and local storage basically everywhere.
Can you say why you decided not to use?
Yeah, way too much overhead and complexity. It make simple tasks hard and it is totally focused on clustering which rarely has any place in the SMB. Deploying it was a huge headache. Had some neat features, but none that we cared about. We ran into some issues with it that were enough that we questioned the logic of trying to use it.
Tested virt-manager instead and it was flexible, simple, and worked perfectly, instantly. The real thing was that in the end oVirt just offered nothing of particular value, but had a lot of negatives.
What was the purpose of looking into it in the first place? What were the goals? What was the problem you were trying to solve?
-
@Obsolesce said in Testing oVirt...:
@scottalanmiller said in Testing oVirt...:
@FATeknollogee said in Testing oVirt...:
@scottalanmiller said in Testing oVirt...:
@FATeknollogee said in Testing oVirt...:
@scottalanmiller What's the backend storage on your oVirt install, NFS, Gluster, iSCSI?
We decided not to use oVirt. But if we were, none of those would make sense. We are using virt-manager and local storage basically everywhere.
Can you say why you decided not to use?
Yeah, way too much overhead and complexity. It make simple tasks hard and it is totally focused on clustering which rarely has any place in the SMB. Deploying it was a huge headache. Had some neat features, but none that we cared about. We ran into some issues with it that were enough that we questioned the logic of trying to use it.
Tested virt-manager instead and it was flexible, simple, and worked perfectly, instantly. The real thing was that in the end oVirt just offered nothing of particular value, but had a lot of negatives.
What was the purpose of looking into it in the first place? What were the goals? What was the problem you were trying to solve?
Remote management of multiple KVM sites.
-
@scottalanmiller said in Testing oVirt...:
Yeah, way too much overhead and complexity. It make simple tasks hard and it is totally focused on clustering which rarely has any place in the SMB. Deploying it was a huge headache. Had some neat features, but none that we cared about. We ran into some issues with it that were enough that we questioned the logic of trying to use it.
Tested virt-manager instead and it was flexible, simple, and worked perfectly, instantly. The real thing was that in the end oVirt just offered nothing of particular value, but had a lot of negatives.
I disagree about oVirt having lots of negatives.
You guys were attempting to use the wrong tool for the job.@scottalanmiller said in Testing oVirt...:
Remote management of multiple KVM sites.
Perfect job for virt-manager :thumbs_up:
-
@FATeknollogee said in Testing oVirt...:
@scottalanmiller said in Testing oVirt...:
Yeah, way too much overhead and complexity. It make simple tasks hard and it is totally focused on clustering which rarely has any place in the SMB. Deploying it was a huge headache. Had some neat features, but none that we cared about. We ran into some issues with it that were enough that we questioned the logic of trying to use it.
Tested virt-manager instead and it was flexible, simple, and worked perfectly, instantly. The real thing was that in the end oVirt just offered nothing of particular value, but had a lot of negatives.
I disagree about oVirt having lots of negatives.
You guys were attempting to use the wrong tool for the job.@scottalanmiller said in Testing oVirt...:
Remote management of multiple KVM sites.
Perfect job for virt-manager :thumbs_up:
Its the wrong tool for the job because of its negatives
Had it not had those negatives it would have been the better tool.
