Hi Darren, Thanks for your reply! Could you share a bit more on your plans/ideas?
We also have been braining on other approaches of managing the systemvm's, especially small customizations for specific tenants. And maybe even leveraging a config mgmt tools like chef or puppet with the ability to integrate CS with that in some way. Cheers, Roeland -----Original Message----- From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com] Sent: woensdag 4 september 2013 20:30 To: dev@cloudstack.apache.org Cc: Roeland Kuipers; int-cloud Subject: Re: [DISCUSS] OOM killer and Routing/System VM's = :( On 09/04/2013 11:15 AM, Roeland Kuipers wrote: > It would be nice to see that the VPC router config is persistent across > reboots even when rebooted outside cloudstack and using the same mechanism as > the other system vm's to make things more consistent and reliable. > > What is your opinion on this? Otherwise will add it to our backlog to > contribute improvements in this area. This isn't terribly helpful for your immediate customer issue, but I'm in the process of putting together a proposal for a new approach to managing the System VMs. Lots of things will change, but it will cover the the case where the VM reboots itself or somebody does it from the hypervisor. The VM will come back up and its current configuration will be restored. It is a rather ambitious change so don't expect to see it done for a couple months. Darren
