Description of problem: In the RHCI Getting Started Guide (http://docbuilder.usersys.redhat.com/23119/) I'm not sure how to interpret one of the sentences that is a bullet point in RHEV Limitations in 1.1: "Only RHEL hosts are supported hypervisor hosts. RHEV Hypervisor is not supported. That seems to be saying that a limitation of RHEV is that it only runs on a RHEL hypervisor, and not a RHEV hypervisor? During the installer, we set up a RHEV-H system, as well as a RHEV-M system, and we can deploy CFME to the RHEV-H. Which seems like it goes against what that sentence says is possible, but I guess I'm just misinterpreting it.
(In reply to Matt Reid from comment #0) > Description of problem: > In the RHCI Getting Started Guide > (http://docbuilder.usersys.redhat.com/23119/) I'm not sure how to interpret > one of the sentences that is a bullet point in RHEV Limitations in 1.1: > "Only RHEL hosts are supported hypervisor hosts. RHEV Hypervisor is not > supported. > > That seems to be saying that a limitation of RHEV is that it only runs on a > RHEL hypervisor, and not a RHEV hypervisor? During the installer, we set up > a RHEV-H system, as well as a RHEV-M system, and we can deploy CFME to the > RHEV-H. Which seems like it goes against what that sentence says is > possible, but I guess I'm just misinterpreting it. Hi Matt, Thanks for filing this bug. According to BZ#1252536, only RHEL-based hypervisors are supported and that's why the sentence was added. I don't have a test instance at hand atm. Could you confirm if it's RHEV-H that's gets deployed as part of the RHEV+CF deployment and not a RHEL-based hypervisor? I assume later on, you can add additional RHEV-H and RHEL-based hypervisors to the environment? What's the suggested work flow for adding additional hypervisors? Cheers, Julie
Sorry Julie, looks like I was mistaken. Just clarified with jmatthews, and it isn't RHEV-H, it's RHEL. The sentence still seems a little confusing to me, as the distinction between RHEL used as a hypervisor and RHEV-H is small to me (rightly or wrongly). Could we rephrase that to simply say that when RHEV is deployed in a hypervisor + engine configuration, that the hypervisor will be RHEL based, and can't be RHEV-H at this point in time? In my mind that's a little clearer, but it could just be me.
Verified.
Documentation now available at: https://access.redhat.com/documentation/en/quickstart-cloud-installer/version-1.0/quickstart-cloud-installer-guide/