You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Probably all versions - observed on 4.19.1.2 and 4.20
CONFIGURATION
OS / ENVIRONMENT
SUMMARY
During zone creation, if the isolation method for public traffic is selected as VXLAN, when adding the public IP range and VNI, the broadcast domain type gets passed as VLAN and not VXLAN. Same holds true when creating vlan public IP range (after zone creation) unless 'vxlan://' is explicitly passed in the vni field.
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered:
as far as I know, vlan still works in vxlan zone, right ?
if so, I think we can keep current behavior (if vlan/vxlan is not passed then use vlan by default).
otherwise, we need to change all possible form which requires vlan id/vni (create shared network, isolated/l2 with vlanid, private gateway with vlanid) on UI.
Ok.. then we need to atleast add a doc PR to explain that one needs to explicitly pass vxlan:// before the VNI if they want to use VLANs .
Can we not add a dropdown menu to the form and then before sending the request to the backend create the vlan field to have <isolation_method>:// ?
Ok.. then we need to atleast add a doc PR to explain that one needs to explicitly pass vxlan:// before the VNI if they want to use VLANs . Can we not add a dropdown menu to the form and then before sending the request to the backend create the vlan field to have <isolation_method>:// ?
Ok.. then we need to atleast add a doc PR to explain that one needs to explicitly pass vxlan:// before the VNI if they want to use VLANs . Can we not add a dropdown menu to the form and then before sending the request to the backend create the vlan field to have <isolation_method>:// ?
That's a good idea @Pearl1594 . We could have the isolation method selected in the physical network by default, allowing the user to change it from the drop-down list.
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
OS / ENVIRONMENT
SUMMARY
During zone creation, if the isolation method for public traffic is selected as VXLAN, when adding the public IP range and VNI, the broadcast domain type gets passed as VLAN and not VXLAN. Same holds true when creating vlan public IP range (after zone creation) unless 'vxlan://' is explicitly passed in the vni field.
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: