----- Original Message ----- > From: "George Skorup" <geo...@mwcomm.com> > To: users@ovirt.org > Sent: Monday, February 9, 2015 4:29:15 PM > Subject: Re: [ovirt-users] New user intro & some questions > > Scott, > > I'm sure you are completely correct. I do not want to run oVirt this > way. I would very much prefer a dedicated machine for the engine, > dedicated KVM nodes and dedicated storage/gluster nodes, or a real SAN. > But this is the "you get this" and "make it work" that I get from upper > management. So I'm going to continue testing 3.5.1 this way, and when > it's too much load / performance sucks, then I can say, "I told you so". > > I was reading through the planned features for 3.6 which says storage on > the virt nodes will be supported. Again, I understand this is not > optimal, but if I have to tell them this needs to wait for 3.6 to be > released for this configuration to be supported, then so be it. And if > performance still sucks, which I don't doubt, then... I told them so.
The meaning of "support" is important here -- support from whom? It's true that there's no gluster+virt SKU of the RHEV downstream project. All configurations of ovirt proper are self-supported, or community- supported, and what we choose to support is up to us individuals. However, gluster + virt on the same nodes does work -- even w/ management through the engine. I do use gluster on my virt nodes, but I don't manage them w/ the engine, because, afaik, there isn't a way to have gluster and virt on separate networks this way, so I just manage gluster from the gluster cli. It's true, oVirt is happiest w/ separate machines for everything, and a rock-solid san of some sort, etc., but that's not the only way, and as you point out, hardware isn't free. Jason > > Anyway.. I was playing around today, and I'm not sure how or why, but > the engine UI now shows the gluster volume stuff.. on the combined virt > + gluster nodes. > > > > On 2/7/2015 1:16 PM, Scott Worthington wrote: > > On 2/7/2015 9:47 AM, George Skorup wrote: > >> On 2/7/2015 7:46 AM, Scott Worthington wrote: > >>> You can manage your oVirt gluster volumes from the oVirt engine UI. > >>> > >>> However, the gluster volumes cannot be on your oVirt hosts. An oVirt > >>> Host > >>> cannot be an oVirt-managed gluster volume provider as well. These are > >>> separate, physical hosts in oVirt <= 3.5.1. > >> Then why did it let me add the hosts as virt & gluster (default option > >> 'both') > >> during setup if it cannot be configured as such? > > The "Both" in the --== OVIRT ENGINE CONFIGURATION ==-- section of the > > engine-setup refers to if you will have "both" oVirt KVM Host clusters as > > well > > as Gluster Volume clusters. "Both" does not mean that you will have the > > Gluster storage daemon and KVM on the same host, as that configuration is > > not > > supported nor recommended. > > > > Hope that helps. > > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users