weizhouapache commented on PR #13792: URL: https://github.com/apache/cloudstack/pull/13792#issuecomment-5218633957
> @weizhouapache Thanks. Just to clarify where this came from OVS/GRE was on a list of CloudStack areas/issues given to me by someone else running CloudStack to look into. It isn't something from my own deployment. We use VMware NSX and aren't using OVS/GRE. > > I've looked further into the alternatives as well. CloudStack's native KVM VXLAN path is separate from the OVS/GRE implementation. Native VXLAN provides the L2 overlay and network-isolation transport, but CloudStack does not use that native VXLAN path to implement its distributed VPC router. The OVS provider additionally maintains VPC-wide host/tier/VM topology, distributed gateway information and ACL/routing policy on each participating host. Therefore native KVM VXLAN is an alternative to OVS/GRE for basic overlay transport, but it is not a direct replacement for the distributed-router functionality exercised by this PR. > > I'm not attached to OVS/GRE as a direction for CloudStack. The PR fixes issues in code CloudStack currently carries, but if there aren't meaningful users of that path anymore and the better direction is to deprecate or remove it rather than continue maintaining it, that's completely fine with me and I'll drop the PR. If OVS/GRE is still considered supported functionality, I'll continue with the testing and the fix. thanks @Dogface2k Your PRs are always more than welcome. The feature is still supported, but it may not be widely used. Personally, I don't know of any users who are actively using it at the moment. So there is no need to withdraw the PR. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
