alexandremattioli commented on code in PR #444:
URL:
https://github.com/apache/cloudstack-documentation/pull/444#discussion_r1794112856
##########
source/plugins/vxlan.rst:
##########
@@ -17,68 +17,47 @@
The VXLAN Plugin
================
-System Requirements for VXLAN
------------------------------
+General
+-------
+CloudStack supports VXLAN technology to enhance scalability and flexibility in
networking designs.
-In CloudStack 4.X.0, this plugin only supports the KVM hypervisor with the
-standard linux bridge.
+Using VXLAN (Virtual Extensible LAN) over traditional VLAN (Virtual LAN)
offers several key benefits, especially for modern data centers and cloud
networking environments that require high scalability and flexibility.
-The following table lists the requirements for the hypervisor.
+VXLAN overcomes the limitations of traditional VLANs by providing a highly
scalable, flexible, and efficient networking solution. It enables the creation
of a large number of isolated virtual networks over a common physical
infrastructure,
+supports better utilization of network resources through Layer 3 routing
capabilities, and simplifies network management and provisioning.
-.. cssclass:: table-striped table-bordered table-hover
+When deploying a VXLAN-based network, there are two options to choose from:
-+----------------+-----------------------------------------------+----------------------------------------------------------------------------------------------------------------+
-| Item | Requirement | Note
|
-+================+===============================================+================================================================================================================+
-| Hypervisor | KVM |
OvsVifDriver is not supported by this plugin in CloudStack 4.X, use
BridgeVifDriver (default). |
-+----------------+-----------------------------------------------+----------------------------------------------------------------------------------------------------------------+
-| Linux kernel | version >= 3.7, VXLAN kernel module enabled | It is
recommended to use kernel >=3.9, since Linux kernel categorizes the VXLAN
driver as experimental <3.9. |
-+----------------+-----------------------------------------------+----------------------------------------------------------------------------------------------------------------+
-| iproute2 | matches kernel version |
|
-+----------------+-----------------------------------------------+----------------------------------------------------------------------------------------------------------------+
+ • Multicast
+ • EVPN using BGP
-Table: Hypervisor Requirement for VXLAN
-
-
-Linux Distributions that meet the requirements
-----------------------------------------------
-
-The following table lists distributions which meet requirements.
-
-.. cssclass:: table-striped table-bordered table-hover
-
-+----------------+-------------------+-------------------------------------------+----------------------------------------------------------------+
-| Distribution | Release Version | Kernel Version (Date confirmed)
| Note |
-+================+===================+===========================================+================================================================+
-| Ubuntu | 13.04 | 3.8.0 (2013/07/23)
| |
-+----------------+-------------------+-------------------------------------------+----------------------------------------------------------------+
-| Fedora | >= 17 | 3.9.10 (2013/07/23)
| Latest kernel packages are available in "update" repository. |
-+----------------+-------------------+-------------------------------------------+----------------------------------------------------------------+
-| CentOS | >= 6.5 | 2.6.32-431.3.1.el6.x86\_64 (2014/01/21)
| |
-+----------------+-------------------+-------------------------------------------+----------------------------------------------------------------+
-
-Table: List of Linux distributions which meet the hypervisor
-requirements
+While Multicast is the easiest to set up, EVPN offers much more control,
scalability, and flexibility. Therefore, it is chosen in most VXLAN network
deployments.
Review Comment:
```suggestion
While Multicast is the easiest to set up VXLAN isolation, EVPN offers much
more control, scalability, and flexibility. Therefore, it is chosen for most
VXLAN network deployments.
```
--
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: dev-unsubscr...@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
