Proofreading of our procedure to cleanly re-create vrouters and restart CloudStack on a running VMware cluster after an interruption

Hello everyone, We had an unexpected problem on our infrastructure while we were upgrading CloudStack from 2.2.13 to 4.1 which led us to stop CloudStack before being able to finalize the update.We still have the vrouters to update but have a production platform that is a bit messy. We're trying to

VM with wrong Service Offering avec host went into maintenance mode ?

Hi to the list, A customer notified us that one of its VM is wrongly displayed in CS. This VM shows up using a service offering of 1 vCPU and 1 GB of RAM when it is a 4vCPU and 8GB VM in vCenter, which is confirmed in the OS itself. Context : - CloudStack 2.2.13 - VMware ESXi 5.0 - VM is a "class

Re: [VOTE] Apache CloudStack 4.0.2

Hello, Same as Nicolas, as we work together and it prohibits us from upgrading our production platform : I also vote -1 on the 4.0.2 release due to the issue https://issues.apache.org/jira/browse/CLOUDSTACK-528 Kind regards, Guillaume On Wed, Apr 17, 2013 at 4:06 PM, wrote: > Hello, > I'm -1