On Thu, Sep 7, 2017 at 8:01 PM, Christopher Cox <c...@endlessnow.com> wrote: > On 09/07/2017 06:33 AM, david caughey wrote: >> >> Hi Folks, >> >> I'm giving a demo of our new 3 node oVirt deployment next week and am >> looking for some high points that I can give to the Managers that will be a >> sell point. > > > Could be hard to sell. It's not like VMware (all in all) is deficient > functionality wise. > >> If you could help with the below questions I would really appreciate it: >> >> Who are the big users of oVirt?? > > > We use oVirt in production. We have about 130 VMs on a 9 node cluster using > Dell blades. It houses both our test and production VMs. We have a > separate oVirt setup for development hosting probably about 20 VMs (maybe > less), it's an 7 node cluster (but much lesser blades there). > > In both cases they are connected to Equalogic iSCSI SAN equipment with > multiple tiers of storage. Each production blade has 4 x 10gbit iSCSI > (multi)paths to storage. The production blade subsystem uses multiple > 40Gbit links, for iSCSI storage and for LAN. Just 10Gbit links and 1Gbit > paths on the development blades and subsystem. > > Both use a dedicated oVirt management host. > > The production(and test) blades run oVirt 3.6 and the dev blades are oVirt > 3.5. > > About 2 years ago we migrated our production blades from oVirt 3.4 on older > blades and older SAN equipment to oVirt 3.6 on new blades and new SAN > storage. We used oVirt's export domain to facilitate the move. > > We will be migrating off the development cluster and we are setting up a new > cluster on the same DC as our production area which will be used to house > both test and development. Thus we are moving to just the one oVirt 3.6 > (we're adding 5 extra blades for that cluster). > > Btw, our VMs include multiple version of CentOS, Windows Server and Windows > desktops (and even some docker nodes, but we're redoing all of that). Our > VMs include about 10 large PostgreSQL database servers, some MySQL, several > Jboss servers, many web microservices (Springboot) servers and lost of > application infrastructure servers. > >> >> Why oVirt and not vMware?? >> (we are a big vMware house so free doesn't cover it) > > > Uh free, and to be honest, that's the best reason to do this IMHO. > >> >> What is the future for oVirt?? > > > Unknown. But pretty sure Red Hat will want to keep RHEV around, which means > oVirt probably will be here for quite some time. > >> >> Why do you use oVirt?? > > > Free. > >> >> Any links or ideas appreciated, > > > oVirt is NOT VMware. But if you do things "well" oVirt works quite well. > Follow the list to see folks that didn't necessarily do things "well" (sad, > but true). > > I inherited this oVirt... not ideal for blades because it's better to have > lots of networks. We just have two blade fabrics, one for SAN and one for > the rest, and it would be nice to have ovirtmgmt and migration networks be > isolated. With that said, with our massively VLAN'd setup, it does work and > has been very reliable. For performance reasons, I recommend that you > attempt to dedicate a host for SPM, or at least keep the number of VMs > deployed there to a minimum. There are tweaks in the setup to keep VMs off > the SPM node (talking mainly if you have a massively combined network like I > have currently).