@scottalanmiller said in Exploring VitalPBX:
@FATeknollogee said in Exploring VitalPBX:
Damn, if this ain't the easiest PBX I've ever installed!!
Heck yeah, it feels like there has to be more to do, lol. The whole process is just so ridiculously easy.
That's right, it just seems way to easy!
Just spoke (by phone) to Jose Montes at VitalPBX.
I pointed him to this thread, he'll come on later to chime in & hopefully (wrong sp: hoefully) answer a few questions.
Damn, if this ain't the easiest PBX I've ever installed!!
@scottalanmiller said in Where Does oVirt Make Sense:
@FATeknollogee so if you have 100 Nodes, and one engine, you have to shut down all 100 Nodes all at the same time just to patch the Engine?
In a multi-node system, the vm's would continue to run while you patch & reboot the hosted engine.
Not sure how your example would work.
Here is my procedure to update a single node
put host in global maintenance
# hosted-engine --set-maintenance --mode=global
run yum update on hosted engine
# yum update -y
run engine-setup on hosted engine
# engine-setup
shutdown all VMs and hosted engine
run yum update on physical host
reboot
start hosted-engine
disable global maintenance
# hosted-engine --set-maintenance --mode=none@scottalanmiller said in Where Does oVirt Make Sense:
@FATeknollogee said in Where Does oVirt Make Sense:
One slight problem is when you have to update oVirt, you need to shutdown your vm's since there's no other hosts to migrate to.
But only the oVirt Node, not the oVirt Engine, correct? The engine has to be able to lose connectivity. If so, that's not really a slight problem, as that's just part of any single node pattern.
You shut the vm's down, update the engine, then you can also update the host, reboot the host & then re-start the engine.
@scottalanmiller said in Where Does oVirt Make Sense:
So with a single node deployment, you can have many single node deployments, all with local storage, all managed by a single oVirt? That's very, very contrary to what someone was promoting in the other thread.
Yes sir.
I've only tried & installed 1 single node deployment.
According to folks like Sandro & Sahina, you can manage multiple single node deployments.
One slight problem is when you have to update oVirt, you need to shutdown your vm's since there's no other hosts to migrate to.
@scottalanmiller said in Where Does oVirt Make Sense:
@FATeknollogee said in Where Does oVirt Make Sense:
@scottalanmiller said in Where Does oVirt Make Sense:
Sandro Bonazzola reached out to me to add a major correction to the list... oVirt supports a single node deployment mode. Getting more information on that now.
I told you about single node deployment in the other thread!
https://mangolassi.it/post/468419Hmm... not at the point in the thread where that goes to. Will have to dig around for it. What's the storage situation when you do that?
It's local storage on the host since its a single node!
@scottalanmiller said in Where Does oVirt Make Sense:
Sandro Bonazzola reached out to me to add a major correction to the list... oVirt supports a single node deployment mode. Getting more information on that now.
I told you about single node deployment in the other thread!
https://mangolassi.it/post/468419
@scottalanmiller curious question...why are you responding to a post from Dec of 2018 made by a user who only posted that one time?
You do realize some type of "shared" storage is necessary unless you opt for the single node install option (which it sounds like you guys didn't choose)?
oVirt is the RH equivalent of vSphere.
oVirt was not made to manage standalone instances of virt-manager.
@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:
@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?
@scottalanmiller What's the backend storage on your oVirt install, NFS, Gluster, iSCSI?
@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)?
@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.
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
From mailcow blog: https://mailcow.email/2019/04/18/mid-april-updates/
Doesn't specify who is in charge of support:
"For commercially used mailcows, please consider buying a support subscription or help to keep mailcow alive by donating. 
I really, really miss working on mailcow full time. Only because of all amazing contributors, mailcow is still growing and gaining new features. Thanks!!!
Greetings to tinc.gmbh!
Unfortunately, Docker seems to be the only "supported" method of installing mailcow, unless I read that wrong.
Maybe someone else has better or more up to date info?