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
> -
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
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 at the
> network level those are used.
Op 20/05/2024 om 14:45 schreef Alex Mattioli:
Hi Alex,
In this scenario:
I think adding the ability to add network specific peers as mentioned in one of
>your prior replies would still allow the level of control some operators (myself
>included) may desire.
How do you propose network
Hi Alex,
In this scenario:
>I think adding the ability to add network specific peers as mentioned in one
>of >your prior replies would still allow the level of control some operators
>(myself >included) may desire.
How do you propose network specific peers to be implemented?
Regards
Alex
Hi Alex,
This may be a difference in perspective in implementation of BGP at the tenant
level. I see the ability this would provide to seamlessly establishing those
peering relationships with minimal intervention (helping scalability).
I think adding the ability to add network specific peers
Hi Alex,
> I am not convinced that specifying BGP peers at the zone level is a good idea
> given the impacts BGP can have on a given network. I would much rather see
> both peer and AS specification handled at the >network configuration, or
> another more specific level.
I don't see how else
Hi Wido,
Thanks for the feedback, comments below:
> I would suggest that the upstream router (Juniper, Frr, etc) should then use
> Dynamic BGP neihbors.
That's the plan.
> I do suggest we add BGP passwords/encryption from the start for safety
> reasons.
That's very likely to be there from
My apologies! I totally missed this one. Commments inline.
Op 15/05/2024 om 14:55 schreef Alex Mattioli:
Hi all,
Does anyone have an opinion on the implementation of dynamic routing in
Isolated networks and VPCs?
So far the design is:
1 - Operator configures one or more BGP peers for a
Hello Alex,
I appreciate this back and forth as I am excited about the potential this
feature would hold.
* This is a very valid point. We could add network specific BGP peers as
well, which would override the automatic AS allocation, in the same way that we
now allocate DNS servers in
Hi Alex,
> Would zone-level BGP peers be those used by default for establishing new BGP
> peers in networks where dynamic routing is enabled?
Correct, so far we plan to allow for up to 4 BGP peers for a zone, with the
possibility to setup different metrics to each peer.
> This could affect a
Hi Alex,
I appreciate the clarity!
Excuse my ignorance if I am misunderstanding the intention of specifying BGP
peers at the zone level.
Would zone-level BGP peers be those used by default for establishing new BGP
peers in networks where dynamic routing is enabled?
This could affect a
Hi Alex,
Answers inline below with >
Cheers
-Original Message-
From: Dietrich, Alex
Sent: Wednesday, May 15, 2024 3:12 PM
To: users@cloudstack.apache.org; d...@cloudstack.apache.org
Subject: Re: Dynamic routing for routed mode IPv6 and IPv4 Isolated and VPC
networks
Hello Alex,
Hello Alex,
I appreciate you taking on this initiative as I’d like to see similar
functionality made available in CloudStack.
I do have some feedback on your implementation approach:
1 - Operator configures one or more BGP peers for a given Zone (with different
metrics)
What is the intention
Hi all,
Does anyone have an opinion on the implementation of dynamic routing in
Isolated networks and VPCs?
So far the design is:
1 - Operator configures one or more BGP peers for a given Zone (with different
metrics)
2 - Operator presents a pool of Private AS numbers to the Zone (just like
Hi all,
I'd like to brainstorm dynamic routing in ACS (yes, again... for the newcomers
to this mailing list - this has been discussed multiple times in the past 10+
years)
ACS 4.17 has introduced routed mode for IPv6 in Isolated networks and VPCs, we
are currently working on extending that to
16 matches
Mail list logo
