Multiple Interfaces on RHEVM-Self Hosted

Latest response

Is it possible to have multiple interfaces on a self-hosted RHEVM? The RHEVM vm seems to be limited in the configurations that can be manipulated on it and we are having trouble adding a second interface or network to it.

Responses

Anybody??

Hi Brent, I am not clear what issue you are trying to describe. I typically install my RHEV Manager on a VM and I have been successful adding a separate interface (in my case for a backup network ).

What kind of trouble are you having?

What process do you go through to add the second interface? Is it during the VM setup or after the VM is up and running? We are just getting started with RHEV and self hosted engines. We tried configuring the RHEVM VM as instructed and then adding a second interface in the Manager GUI as you would any other VM but it seems we can't add it there. I think we were finally able to add it by editing the ova file but that doesn't seem to be the "cleanest" way to do things.

I apologize Brent, when I read your first post, I read that as "bare metal" and not the self-hosted option that has been developed - again, I apologize. I recommend opening a ticket on this. That said, I believe my approach would resemble what you had done (adding once the VM is deployed). I have some lab/testing work to do with my own RHEV environment which I am now curious how this would work (after actually understanding your question). If I learn anything noteworthy, I'll be sure to update this thread.

Thanks James. Any info you come across would be helpful.

My understanding is that while the RHEVM VM is listed as just another VM to be managed through the interface, it is not possible to manage it through conventional RHEV methods.

Instead, it may be necessary to manually modify the Manager's XML configuration (located in /var/run/libvirt/qemu) with the desired changes. If you aren't comfortable with raw XML, you may want to try making the changes through vdsClient.

In either case, be aware that the changes would also need to be manually replicated across any hosts in your cluster, and that you should exercise caution so as not to leave your Manager VM in a state of disrepair.

Thanks! We will give it a shot and see what happens.

Russell, I have been trying for the past few days to accomplish what we want using vdsClient as you suggested and still don't seem to be able to get it right. On my host I have eth0.305 and eth3.306 (vlans, obviously). I would like these same two networks to be available on my self-hosted engine. During hosted-engine deployment I am able to choose one or the other of those interfaces to use but not both. I've attempted several times using vdsClient addNetwork but don't ever seem to be able to get it quite right. Are you familiar enough with it to guide me through how I would accomplish this?

Brent, my apologies -- I'm not intimately familiar with the process, as it is not something I've had to do routinely (and I'm not in the office this week to try).

However, I believe the following process may produce your desired result:

  1. Set the Manager VM's maintenance mode to 'global'.
  2. Gracefully shutdown the Manager VM.
  3. On your physical host(s), edit /etc/ovirt-hosted-engine/vm.conf
    3a. Duplicate the existing network interface entry.
    3b. Modify the MAC address, UUID and network name of the newly added interface.
    3c. Replicate any changes across all physical hosts.
  4. Start the Manager VM.
  5. Set the Manager VM's maintenance mode to 'none'.

Let me know how it goes.

For the sake of time, we have decided to re-design our network to include only one interface on our hosted engine. So unfortunately, I was not able to fully test all suggestions offered here. I appreciate all of the feedback and suggestions offered.

Close

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