On May 10, 2019 9:16:02 PM Dmitry Filonov <filonov@hkl.hms.harvard.edu> wrote:
I have used both hosted and standalone engine and can tell that so far I had more issues with hosted engine than with standalone one.Not like huge issues, but something like you put host in to global HA maintenance, then update hosted engine, reboot and... and it doesn't start.Not a big deal, but for a new user it might be a bit confusing.So am with Michael, if you just starting using oVirt then it's better to have standalone engine et first. And then migrate it over into hosted environment when you are comfortable to do so.Fil--Dmitry FilonovLinux AdministratorSBGrid Core | Harvard Medical School250 Longwood Ave, SGM-114Boston, MA 02115On Fri, May 10, 2019 at 9:00 PM Vincent Royer <vincent@epicenergy.ca> wrote:Disagree, I've had some pretty significant meltdowns and if you cant access hosted engine, go have drink and try again... It comes up. It's ability to self-repair and find a scrap of a host to run on is pretty impressive._______________________________________________On Fri, May 10, 2019, 2:18 PM Derek Atkins <derek@ihtfp.com> wrote:I've been running hosted engine on a single host for a few years now with
no issue. I did redo my initial install several times but its been fine
ever since. I started at 4.0.x and have gone through multiple OS and ovirt
upgrades with few issues.
-derek
Sent using my mobile device. Please excuse any typos.
On May 10, 2019 4:47:12 PM michael@wanderingmad.com wrote:
> Honestly? don't do hosted engine deployment first. If you're just getting
> started with ovirt, you're going to waste weeks on getting hosted engine
> running, and then I guarantee once it's running, it's not going to come up
> when you need it most. Just load your single host, and then load the
> engine on a separate VM/Machine to manage it. I have the engine running on
> a separate machine so just in case there is a host issue, you can still
> access the engine to fix it.
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-leave@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/7TAEQR6SZKQM2YBPCKBAEYFWF432QGAA/
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TRJGHLOBJB2GQPW32FAXKSE6DWSUO5H5/
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/I6AR5C276BXNNRZTBMU65ES5NGCON7J7/
_______________________________________________Users mailing list -- users@ovirt.orgTo unsubscribe send an email to users-leave@ovirt.orgPrivacy Statement: https://www.ovirt.org/site/privacy-policy/oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/