Slair1 commented on issue #3721: network: cleanup dhcp/dns entries while remove a nic from vm URL: https://github.com/apache/cloudstack/pull/3721#issuecomment-569757319 > I'm wondering if it would make sense to make the "recreate.systemvm.enabled=**TRUE**" a default value in 4.14 and onwards, since: > > * doesn't leave all the garbage VR's old ROOT disk had since new ROOT disk created > > * no orphaned DHCP/DNS configuration data (issues explained in this comment) > * no potential log garbage (not that much of the issue afaik) > * /var/cache/cloud/processed files can be huge on old VRs > * doesn't bring any usable (day to day) improvements for cloud operator/normal user > > * CPVM and SSVM are not restarted daily and cloud-operator can wait for 2 minutes more to configure CPVM/SSVM from scratch vs. booting an existing/configured VM > * VR's are also not restarted daily and since VR can be stopped either manually (you planned some actions, so you can wait for 2 more minutes?) or automatically by network.gc when there are no Running VMs in the network - again one can wait for 2 more minutes for a clean VR for the very first existing VM he starts in that existing network. @andrijapanicsb In a different scenario where a VR was just rebooted, and this option was set to TRUE, would we lose our existing DHCP/DNS configuration data for VMs that are still connected to the VR/network? I don't fully know how that config data is persisted, so sorry if it's a dumb question!
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
