Description of problem: It should be possible to use hosts on RHEVM as ovirt hosts (to run VMs) and also as storage hosts (gluster). For now, it's not possible to enable gluster service on an ovirt cluster. User should be able to use host as gluster host even though it has been already used to run VMs.
*** Bug 998903 has been marked as a duplicate of this bug. ***
*** Bug 1144154 has been marked as a duplicate of this bug. ***
Customer requested for this : ====================== RFE Request ====================== 3. What is the nature and description of the request? > Customer wants this feature to be ported in RHEV, this feature is available only on Ovirt. They have tested on Ovirt this type of configuration, a cluster with Virt+Gluster services, 2 nodes that provide storage domain by GLUSTER, and Virt Service, all in the 2 nodes. [In Rhev actually it is not possible to have a cluster with virt+gluster services at the same time, in rhev we have to create separate cluster with GLUSTER.] # Use case of this feature and how important it is for them ? Customer back back with: ------------------------ > It is very useful. For example: have 2 nodes that have ovirt+gluster services, in this use case, customers can have a fully private cloud ( computing+storage ) 100% HA. It's very cheap but powerful solutions as private cloud entry point for an average of 10 VM (depending of hardware ) . > Of course 10 gigabit interconnection must be created. 2 total node, every node 2 ethernet for public vlan, 2 10gigaibt for internal connection for gluster, and 2 ethernet for management . 4. Why does the customer need this? (List the business requirements here) > with this new feature we can sell to clients a complete " private cloud " solutions with just 2 nodes. Interconnected in 10 gigabit that provide computing and storage solutions, both in HA . 5. How would the customer like to achieve this? (List the functional requirements here) > simply adding in rhev the cluster option " Virt+Gluster " that already is active in Ovirt 8. Does the customer have any specific timeline dependencies ? > ASAP 11. Would the customer be able to assist in testing this functionality if implemented? > Yes. of course. we already tested in Ovirt with success.
Gajanan - please note that 3 nodes would be required for as we plan to use replica 3. VMs will work as long as 2 out of the 3 nodes are up and running
Hi Itamar should i update this to customer ?
We are actively looking at this as a high priority for 3.6, but planning for 3.6 is not done yet for commitment. as mentioned in comment 13, it is already clear we will need replica 3 in gluster for a node failure to behave correctly. (with 2 nodes, one node will survive peer failure having 2 replicas, and the other node will not be able to continue (having only 1 replica).
*** Bug 1177769 has been marked as a duplicate of this bug. ***
oVirt 4.0 Alpha has been released, moving to oVirt 4.0 Beta target.
This bug had requires_doc_text flag, yet no documentation text was provided. Please add the documentation text and only then set this flag.
This feature is available with ovirt 4.1