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 t
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 as
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 spe
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,
> 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 e
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 d
rohityadavcloud commented on issue #151:
URL:
https://github.com/apache/cloudstack-cloudmonkey/issues/151#issuecomment-2120145537
Fixed by https://github.com/apache/cloudstack-cloudmonkey/pull/150
--
This is an automated message from the Apache Git Service.
To respond to the message, plea
rohityadavcloud closed issue #151: 6.4.0 add host -> authentication error
URL: https://github.com/apache/cloudstack-cloudmonkey/issues/151
--
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
rohityadavcloud merged PR #150:
URL: https://github.com/apache/cloudstack-cloudmonkey/pull/150
--
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-unsub
rohityadavcloud merged PR #60:
URL: https://github.com/apache/cloudstack-kubernetes-provider/pull/60
--
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
10 matches
Mail list logo
