shoaibjdev commented on issue #3802: OVS Provider not visible under Network Service Providers for guest network URL: https://github.com/apache/cloudstack/issues/3802#issuecomment-573582305 **@weizhouapache** - Really appreciate your help and assistance on this. We have created the custom offering and tried with it as well, but Virtual routers didn't came up. So we went with default network offering. Would you be kind enough, to direct us in the right direction as per best practices in production what is in general is adopted by customers running ACS in production as of today? Our requirement for networking is to let the tenants create their own private networks running on multiple Hypervisor nodes and all instances running on differents nodes should be able to reach each other as longs its under the same super CIDR they defined. And traffic from other tenants should not interfere with others. We want to avoid using VLAN tags from the physical networks as it wouldn't make any sense for us to plug additional VLANs when we scale the hardware, and we do not want tenants to be part of the physical network ports. So we decided to go with SDN solution and let tenants create their own networks identified by VNI's, either VXLAN or GRE from OVS works very well and mature solution for vanilla KVM and OVS setup without ACS. But we see some limitation on ACS as OVS doesn't work with VPC which would have solved this scenario. Challenge we have is just getting the OVS tunnel to work across Hypervisor hosts. Please advise how we can achieve this on ACS.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
