Hi João Jandre,
I think, it's better to do 4.19.1.0 before 4.20.0.0, and schedule 4.20.0.0
release a month or two after 4.19.1.0 release. Considering the 4.19.1.0
timelines proposed [1], you can target 4.20.0.0 in Q3, around Aug end (or early
Sept). Please let me know your thoughts.
[1] https:
Hi All,
It's been few months since the proposal, and we've fixed/tested/merged 139
Issues and PRs in the 4.19.1.0 milestone [1]. Currently, we've 202 open items
in the 4.19.1.0 milestone, tracked/triaged through the GitHub project 'Apache
CloudStack 4.19.1' [2].
We can target for the "Must hav
The idea is to allocate the AS number pools in the same way we allocate VLANs
to a zone, with the possibility to enter the AS number manually per network
(depending on offering, just like in the case of VLANs).
>This would solve most use-cases from the start:
>- BGP peer on zone level
> - over
Op 22/05/2024 om 14:55 schreef Alex Mattioli:
Thanks for the input Wido,
That said, you could also opt that you can specify BGP peers are zone level and
override them at network level if one prefers. Nothing specified at >the network?
The zone-level peers are used. If you do >specify them a
