vnic profile custom properties menu not visible in 3.4.1
Hello, I have an all-in-one environment based on f19 and 3.4.1. My host main interface (and so ovirtmgmt bridge) is 192.168.1.x I'm trying to setup a natted network for my VMs (it will be 192.168.125.x). I already completed the vdsm and libvirt part following Dan blog page here: http://developerblog.redhat.com/2014/02/25/extending-rhev-vdsm-hooks/ I created a new vnic profile named "natted" for my ovirtmgmt network. But I'm not able to see in webadmin how to add a custom property "extnet" to this vnic profile and set it to the "natted" value. I already restarted vdsmd and then ovirt-engine (not a full restart of the server yet, after installing vdsm-hook-extnet-4.14.8.1-0.fc19 package See below my screenshots, I see no way to add it. https://drive.google.com/file/d/0BwoPbcrMv8mvZF93ekI2a1V2clk/edit?usp=sharin... https://drive.google.com/file/d/0BwoPbcrMv8mvbkFVZEF3X2VhNVE/edit?usp=sharin... Is it perhaps a command line only option? Based on this page I wouldn't expect so: http://www.ovirt.org/Features/Vnic_Profiles I see instead a "Please select a key" dropdown menu where I can only select "Security Groups"... NOTE: I need this because I have to setup an openvpn tunnel between the server where I have the all-in-one setup and a remote network. Unfortunately both the networks, despite different internet providers, use 192.168.1.x for their internal networks (arghhhh! add more fantasy to providers menu please... so many private networks available: don't stop to the first one... ;-) so that I can't establish routing between the two networks after tunnel setup. I'm trying to solve using a VM with another network via NAT and setting up the openvpn tunnel from this VM, hoping it would be able to route then with the 192.168.1.x destination internal network.... Thanks Gianluca
On Sun, May 25, 2014 at 4:31 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com>wrote: [snip]
But I'm not able to see in webadmin how to add a custom property "extnet" to this vnic profile and set it to the "natted" value.
[snip]
Is it perhaps a command line only option?
Based on this page I wouldn't expect so: http://www.ovirt.org/Features/Vnic_Profiles
I see instead a "Please select a key" dropdown menu where I can only select "Security Groups"...
[snip]
OK. so after reading this page http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob;f=vdsm_hooks/extnet/README;... BTW: is it in any package? [root@tekkaman ovirt-engine]# rpm -ql vdsm-hook-extnet /usr/libexec/vdsm/hooks/before_device_create/50_extnet /usr/libexec/vdsm/hooks/before_nic_hotplug/50_extnet [root@tekkaman ovirt-engine]# before [root@tekkaman ovirt-engine]# engine-config -g CustomDeviceProperties CustomDeviceProperties: version: 3.0 CustomDeviceProperties: version: 3.1 CustomDeviceProperties: version: 3.2 CustomDeviceProperties: version: 3.3 CustomDeviceProperties: {type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}, *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.4 then [root@tekkaman ovirt-engine]# engine-config -s CustomDeviceProperties='{type=interface;prop={extnet=^[a-zA-Z0-9_ ---]+$}}' Please select a version: 1. 3.0 2. 3.1 3. 3.2 4. 3.3 5. 3.4 5 after: [root@tekkaman ovirt-engine]# engine-config -g CustomDeviceProperties CustomDeviceProperties: version: 3.0 CustomDeviceProperties: version: 3.1 CustomDeviceProperties: version: 3.2 CustomDeviceProperties: version: 3.3 CustomDeviceProperties: {type=interface;prop={extnet=^[a-zA-Z0-9_ ---]+$}} version: 3.4 # systemctl restart ovirt-engine BTW: is it correct that what before was security groups is now barely overwritten by extnet? Or is there a syntax with which I can add extnet without deleting security groups (even if I don't understand its usage, possibly with openstack integration based on its name...) Anyway now in oVirt webadmin I can edit the "natted" vnic profile and inside the dropdown menu (there isn't any header marked like "custom property" or similar, that could be useful....) shutdown and poweroff vm start vm and now it correctly gets the ip 192.168.125.91 defined inside the dhcp range for "natted" network virsh dumpxml f19 ... <interface type='network'> <mac address='00:1a:4a:a8:01:55'/> <source network='natted'/> <target dev='vnet0'/> <model type='virtio'/> <filterref filter='vdsm-no-mac-spoofing'/> <link state='up'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> ... The web admin portal gives the corect new ip of the VM, as sent by vdagent. The VM is able to navigate through Internet and http://www.whatismyip.com/ gives for example consistent and equal information both using my all-in-one server and my VM Now I'm goint to test if I can solve the openvpn issue Gianluca
participants (1)
-
Gianluca Cecchi