does anybody here use virtual network templates? I want to allow ordinary users to create their own VNets, so I created a VNet template and want to instantiate it under an ordinary user. The problem is that the resulting VNET gets assigned to the CLUSTER=0 regardless of what I set up in the template:
# onevntemplate show 0 TEMPLATE 0 INFORMATION ID : 0 NAME : My VNET template USER : oneadmin GROUP : privgroup LOCK : None REGISTER TIME : 02/22 14:12:20 PERMISSIONS OWNER : um- GROUP : u-- OTHER : --- TEMPLATE CONTENTS AUTOMATIC_VLAN_ID="YES" CLUSTER="101" FILTER_MAC_SPOOFING="YES" GUEST_MTU="1200" INBOUND_AVG_BW="100" OUTBOUND_AVG_BW="100" PHYDEV="eth0" VN_MAD="vxlan"
CLUSTER=101 above. This is the cluster I want the instantiated vnets to be in.However, when I try to instantiate the VNET template 0:
# onevntemplate instantiate --name 'test-vxlan' 0 VN ID: 36 # onevnet show 36 VIRTUAL NETWORK 36 INFORMATION ID : 36 NAME : test-vxlan USER : oneadmin GROUP : oneadmin LOCK : None CLUSTERS : 0 BRIDGE : onebr36 VN_MAD : vxlan PHYSICAL DEVICE : eth0 VLAN ID : 38 AUTOMATIC VLAN ID : YES AUTOMATIC OUTER VLAN ID : NO USED LEASES : 0 PERMISSIONS OWNER : um- GROUP : --- OTHER : --- VIRTUAL NETWORK TEMPLATE BRIDGE="onebr36" BRIDGE_TYPE="linux" CLUSTER="101" FILTER_MAC_SPOOFING="YES" GUEST_MTU="1200" INBOUND_AVG_BW="100" OUTBOUND_AVG_BW="100" PHYDEV="eth0" SECURITY_GROUPS="0" TEMPLATE_ID="0" VN_MAD="vxlan" ADDRESS RANGE POOL LEASES AR OWNER MAC IP IP6 VIRTUAL ROUTERS #
The newly created VNET is added to CLUSTER=0 (only), and as such it cannot be used for new VMs in CLUSTER=101. Note that I am doing this under oneadmin, but instantiating the VNet template under an ordinary user (member of group
privgroup, of course) yields the same result.
EDIT: also, when I open the VNet template in Sunstone (as oneadmin), and click on the “Clusters” tab, there is no cluster selected. Even when I click on “Select cluster”, select cluster 101, and click on “Apply changes”, there is still no cluster selected in the “Clusters” tab".
EDIT2: when I manually add parameter
CLUSTERS = "101" to the template (note the plural), save the template, and then click on the “Clusters” tab, the cluster 101 is displayed as selected for this template. However, instantiating this template still results in the new VNet assigned to cluster 0.
Versions of the related components and OS (frontend, hypervisors, VMs):
CentOS Linux 7, Qemu, ONe 18.104.22.168 CE
EDIT 3: 22.214.171.124 CE - still the same behaviour.
Steps to reproduce: