weizhouapache commented on pull request #5938: URL: https://github.com/apache/cloudstack/pull/5938#issuecomment-1032424146
@DaanHoogland @rohityadavcloud @sureshanaparti this has conflicts with persistent config which is useful when VR is rebooted from out-of-band (e.g. vcenter, or command inside VR). However, the nics of VPC VR is always plugged in the following order when VPC VR is started in cloudstack (1) Source nat IP (2) additional public IPs (3) private gateway (4) vpc tiers This order is sometimes different from the IPs in json files inside the VR. This happens in many scenarios, for example (1) public ip in additional range is associated (2) private gateway is created after vpc tier creation (3) remove a vpc tier (not the last vpc tier) when it happens, IPs will be associated to wrong interfaces when reboot VR from cloudstack. with this PR, cloudstack can ensure that the order is correct and Ips are associated to correct interfaces. but the VR is rebooted from out-of-band, VR will not work anymore, as json config files are removed in bootstrap. We need to determine which we should support better (reboot VR from cloudstack, or out-of-band). -- 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]
