Ha, good question. 1) Integration with Rancher, as well as with Vmware are on the roadmap. 2) underlying vlans: you don't plumb every time, you create a range

Ha, good question. 1) Integration with Rancher, as well as with Vmware are on the roadmap. 2) underlying vlans: you don't plumb every time, you create a range of vlans (vlan 600-700 for example) and allow that range on the ports that are looking towards Netris and towards hypervisors (switchport trunk allowed vlan 600-700). It's a one-time and basic configuration, which network admins would typically do in any case to enable some vlans for server virtualization platform. Then you let Netris know what are the allowed vlans and that's it. Your switch will move packets based on mac address and vlan id, switches are good on that. While Netris will pick next available vlan (from allowed range) for every V-NET.