Hi, our team at Netris been working on this solution for a while to help DevOps folks skip networking challenges in on-prem, colo, bare metal cloud, and edge.
Kelsey and I recorded this webinar recently. I thought i would be interesting for the group here.
Happy to take questions and hear all/any feedback!
The demo seems kinda janky where you have to manually sync the config between Netris and Rancher. Is integration on the roadmap so vnets created in Netris are automatically synced to the orchestration system? Using pre-plumbed VLANs also seems to be skipping the hard part of setting them up in the first place.
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.
BTW, this was a brownfield use case for bringing VPC networking into an existing physical network without requiring major changes.
We have solution for Equinix Metal, where we consume Equinix API, and underlying pluming happens automatically. + we have a greenfield solution when we operate underlying leaf-spine fabric end-to-end.
4 comments
[ 3.4 ms ] story [ 22.0 ms ] threadKelsey and I recorded this webinar recently. I thought i would be interesting for the group here.
Happy to take questions and hear all/any feedback!
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.
We have solution for Equinix Metal, where we consume Equinix API, and underlying pluming happens automatically. + we have a greenfield solution when we operate underlying leaf-spine fabric end-to-end.
Happy to dive/discuss further. Love networking!