Not really messy when scripted, each step is a small API command after all.
This is what oVirt does when you connect, getting the data and populating
the .vv file for you. So if the VM migrates in the instant it takes to get
the info, the connection will fail, so you simply rerun the connect script
Thanks for the info Dan. If that's what it takes I'll need to use a
different method. The one you describe is not only very messy but
extremely breakable and error prone (e.g. if the VM migrates to another
host).
regards,
John
On 11/10/14 02:02, Dan Yasny wrote:
The steps are:
1. Find the
Hi,all
I use oVirt 3.4.4 . I want integrate the OSN int oVirt.I had some problems.
For example, I imported a network named 'private' from openstack neutron. Then
use the network in a VM's NIC.
The vdsm's problem is "libvirtError: Cannot get interface MTU on 'private': No
such device" .
The env
3 matches
Mail list logo