Hi, Simone Tiraboschi <stirabos@redhat.com> writes:
On Mon, May 21, 2018 at 7:49 AM, <ovirt@fateknollogee.com> wrote:
Use case: small sites with a minimum number of vm's.
Is there such a thing as a single host install?
In the past we had the all-in-one mode but we deprecated it. Now the suggested mode is hosted-engine since you could expand it adding other hosts in the future.
I am running in this configuration and have had little problem. I migrated from an old vmware-server platform, and, modulo a few hiccups along the way and a few false starts as I was installing ovirt, it's been pretty stable for me!
Is it valid for production use?
With a single host the upgrades will become more intrusive: without the capability to migrate your VMs on other hosts at upgrade time, you will be required to bring down everything.
This is true -- I have to bring everything down when I want to upgrade the system, especially the host itself. So I don't upgrade as often as I might if I had multiple hosts where I could migrate.
What kind of storage?
NFS in loopback could be problematic, I'd suggest gluster in replica 1 or iSCSI.
I'm running loopback NFS and I've not encountered any issues. I've been running this way since 2016-10-22. I did not understand Gluster enough and wasn't sure how I could make a "replica 1" -- everything seemed to imply you *NEEDED* 3 gluster hosts. So I went with what I knew -- NFS. This might be problematic if I move forward to a multi-host platform as I'll have to "migrate" my storage -- specifically for hosted-engine -- which IIRC requires a re-install (or some other drastic measure). -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warlord@MIT.EDU PGP key available