vxlan: Update VXLAN documentation to include EVPN#444
Conversation
This is a first attempt on getting proper documentation on how to use VXLAN with BGP and EVPN underneath CloudStack
|
cc @rajujith @NuxRo @andrijapanicsb @alexandremattioli - can you review the content & technicalities, otherwise LGTM. Thanks for the PR @wido |
yadvr
requested review from
DaanHoogland,
NuxRo,
andrijapanicsb and
weizhouapache
NuxRo
left a comment
NuxRo
left a comment
There was a problem hiding this comment.
Corrected a few very minor typos, hashtag polish, otherwise LGTM.
source/plugins/vxlan.rst
Outdated
| .. note:: Please use rebuild kernel and tools at your own risk. | ||
| Under Linux you can NOT provision (start) more than 20 VXLAN interfaces and error message "No buffer space available" can be observed in Cloudstack Agent logs after provisioning required bridges and VXLAN interfaces. | ||
|
|
||
| Increase needed parameter to sane value (i.e. 100 or 200) as required. |
There was a problem hiding this comment.
| Increase needed parameter to sane value (i.e. 100 or 200) as required. | |
| Increase the needed parameter to an appropriate value (i.e. 100 or 200) as required. |
source/plugins/vxlan.rst
Outdated
| :: | ||
| - BGP Routing Daemon on the hypervisor | ||
| - No LACP/Bonding will be used | ||
| - Modified script is required to use EVPN instead of Multicast |
There was a problem hiding this comment.
| - Modified script is required to use EVPN instead of Multicast | |
| - The modified script is required |
There was a problem hiding this comment.
@NuxRo Did you truncate the phrase by accident?
source/plugins/vxlan.rst
Outdated
| Since all VXLAN (VTEP) interfaces provisioned on host are multicast-based (belong to certain multicast group, and thus has it's own multicast IP that is used as VTEP), this means that you can not provision more than 20 (working) VXLAN interfaces per host. | ||
|
|
||
| .. note:: Please use rebuild kernel and tools at your own risk. | ||
| Under Linux you can NOT provision (start) more than 20 VXLAN interfaces and error message "No buffer space available" can be observed in Cloudstack Agent logs after provisioning required bridges and VXLAN interfaces. |
There was a problem hiding this comment.
| Under Linux you can NOT provision (start) more than 20 VXLAN interfaces and error message "No buffer space available" can be observed in Cloudstack Agent logs after provisioning required bridges and VXLAN interfaces. | |
| Under Linux you can NOT by default provision (start) more than 20 VXLAN interfaces and the error message "No buffer space available" will appear in the Cloudstack Agent logs after provisioning the required bridges and VXLAN interfaces. |
There was a problem hiding this comment.
Left some polish suggestions.
Also, the zone creation isolation method screenshot shows VLAN, probably a good idea to replace it with one showing VXLAN to avoid confusion.
Otherwise LGTM. Am actually setting up an env following the doc together with the guys from https://www.netris.io/ @wido
source/plugins/vxlan.rst
Outdated
| :: | ||
| - BGP Routing Daemon on the hypervisor | ||
| - No LACP/Bonding will be used | ||
| - Modified script is required to use EVPN instead of Multicast |
There was a problem hiding this comment.
@NuxRo Did you truncate the phrase by accident?
Great! Good to see more people are going to use it. I do recommend to use Frr-10 btw, has some nice bug fixes. But this is frr-stable nowadays. |
Indeed they are using FRR10. They have a very cool product, lots of interesting networking automation/orchestration, and soon with ACS integration. |
|
All changes approved, all checks passed. I see no objections, merging this one soon. |
5 participants
This is a first attempt on getting proper documentation on how to use VXLAN with BGP and EVPN underneath CloudStack
For PR apache/cloudstack#9778
📚 Documentation preview 📚: https://cloudstack-documentation--444.org.readthedocs.build/en/444/