What will I need to buy to run RHEV 3.0?

Latest response

RHEV 3.0 has not been released yet, but customers are already asking how the RHEV 3.0 product will be priced, especially now that it is based on RHEL 6 and JBoss. The good news is nothing has changed: RHEV is just as easy to buy as before. And the JBoss runtime needed to run RHEV Manager is included in your RHEV subscription.

 

RHEV 3.0 Pricing Based on Managed Sockets and Desktops, Just Like Today

 

  • The basic product for RHEV, called RHEV for Servers, is priced on the basis of the sockets in the hypervisors being managed. This does not change for RHEV 3.0.
  • There is a single edition of RHEV for Servers, with all of the enterprise virtualization management features we offer.
  • Customers simply need to count the occupied CPU sockets in all their servers, then choose either a Standard (Business Hours) or Premium (24 x 7) support model. That's it.
  • RHEV Manager (the management system) is included, as is the ability to run unlimited server virtual machines. Guest operating systems (Windows, RHEL, etc.) must be purchased separately.
  • If you want to run desktop operating systems, you will need RHEV for Servers for every socket in your environment, and then add the RHEV for Desktops add-on, which is sold in packs of 25 concurrent desktops. RHEV for Desktops gives you support for desktop operating systems, the desktop User Portal, the SPICE client, and RHEV desktop guest agents.

RHEV Manager requires a RHEL subscription, but JBoss included

 

  • For your RHEV Manager servers, you will be required to have an active RHEL subscription running the latest RHEL 6. Your RHEV subscription will give you the RHEL channels you will need to subscribe to in order to run RHEV, including the appropriate JBoss platform.
  • The JBoss platform is included with your RHEV subscription (it doesn't cost extra), but it is limited to running the RHEV Manager platform and cannot be used for other purposes.

RHEL for your hypervisor servers is optional, but not required

 

  • Every RHEV for Servers subscription includes the RHEV Hypervisor (RHEV-H) which is a slimmed down version of RHEL with just enough packages to act as a hypervisor. It can run any guests (RHEL, Windows, etc.) and is included free with RHEV. Most customers prefer to deploy RHEV-H in their environments, and they can do so for every server for which they have purchased RHEV for Servers.
  • Some customers prefer to use RHEL as a hypervisor on the bare metal, which we also support. These RHEL subscriptions would need to be purchased separately, but it's also the same subscription you need to buy RHEL guests.
    • For example, if you buy unlimited RHEL guests for all of your servers, you get a bare metal instance of RHEL for free which you can install on each server and configure as a hypervisor for RHEV.
    • Or, you can choose to install RHEV-H on your servers and simply activate the unlimited RHEL guest subscriptions on those servers.

Responses

Will I need to purchase an additional RHEL subscription to migrate from the Windows RHEV-M installation to a new RHEL RHEV-M install?

Kenneth,

 

Good question!

 

Take a look at a post Chuck made a bit ago, which has full details:

 

https://access.redhat.com/discussion/what-will-i-need-buy-run-rhev-30

 

Thanks!

 

Andrius.

Red Hat, Inc.

I've got two enclosures with 3 blades on each one. 

 

Each blade has two sockets but only ONE socket used, for a total of 12 sockets across both enclosures, with only 6 sockets occupied by a CPU.

 

 

By our policy we're planning to start with 2.2 and once released we'd be migrating to 3.0 after testing. So the initial purchase would be with 2.2

 

 

Should we buy 6 or 12 RHEV licenses  ?

 

thanks for your insights.

 

 

Andres,

 

As long as the second socket doesn't have a processor attached, you shouldn't be required to purchase the second subscription per system.

 

Hope this helps!

 

Regards,

 

Andrius Benokraitis

Red Hat, Inc.

Thanks Andrius  :)

I'm curious about why JBoss is included, as a necessary component of running the RHEV Manager service, but not RHEL? RHEL seems to be on the same level as JBoss in terms of "I need it to be able to run it.", but, in our case, we have no active RHEL subscriptions, so in order to make the supported transition from 2.2 to 3.0, we now have to spend an additional ~$800+ on a RHEL machine, which is no small expense.

Hi Adam,

 

JBoss is included only because it is required for RHEV-M itself to work properly. JBoss is not to be used for direct use by the customer.

 

As for the additional expense, having RHEV-M run on RHEL offers better use cases (being able to cluster RHEV-M as a RHEL HA service), ability to consolidate services (run IPA on the same server), as well as offer a migration path for customers using RHEV-M on Windows 2003 Server (which looks to be moving out of Mainstream Support phase later this year).

 

We understand this could be painful for some customers, but we also feel the benefits of upgrading outway the drawbacks.

 

I highly recommend that you contact your designated Red Hat sales associate to evaluate your situation, which may actually incur longer-term cost savings even if there is a short-term loss.

 

Hope this helps!

 

Regards,

 

Andrius

Red Hat, Inc.

Hi, I'm bringing this thread back from the death but I need some clarification about the new RHEV subscription model.

If I've got several servers (blade, whatever) with only 1-socket, should I buy 1 subscription for each one of those servers, or should I count the total number of sockets and buy enough 2-sockets subscriptions so I cover all the sockets used in my platform?

Thanks in advance for your clarification.

Best Regards,

Andres

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.