weizhouapache commented on issue #11827:
URL: https://github.com/apache/cloudstack/issues/11827#issuecomment-3406147585

   > [@weizhouapache](https://github.com/weizhouapache) All BGP is up and 
running, and works !!!
   > 
   > **1. Manual config of vROUTER:** I configured the vRouter manually as a 
ROOT Admin - that is going to be a burden for Subdomain customers and for the 
CS administrators: **2. Dynamic vROUTER Script:** What script takes care of the 
vRouter Dynamic config? then I can make standard for our deployments, I have to 
add several lines. **3. Router infrastructure configuration:** Any tool you 
recommend to configure the router from cloudstack - I have to add only one line 
on each router, but wan it to make automatic. **4. Subdomain Project BGP peers 
not visible:** Seems cosmetic, Maybe this is intended, and only domain admins 
should be able to see the BGP peers. Please let me know However under the 
Subdomain - Dynamic routed Project the BGP peers are empty:
   > 
   
   what manual configuration have you made inside the VR ?
   
   the frr configuration is generated by a python script: 
https://github.com/apache/cloudstack/blob/main/systemvm/debian/opt/cloud/bin/cs/CsBgpPeers.py
   if you make some changes in the script, you need to update 
/usr/share/cloudstack-common/vms/cloud-scripts.tgz on hosts or mgmt servers (if 
you use vmware)
   
   the table lists the BGP peers associated to the VPC, by default it is empty. 
the configuration is described on the UI
   ```
   Please note, if no BGP peers are selected, the VR will connect to
   (1) dedicated BGP peers the owner can access, if the owner has dedicated BGP 
peers and account setting use.system.bgp.peers is set to false;
   (2) all BGP peers the owner can access, otherwise.
   ```
   
   Only root admin can change BGP peers for network and VPC.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to