Did you upgrade and are you using usage info for billing? There is bug reported that the network usage is wrong. Did you notice when your system-vms are gone then the system will not re-create them? During upgrade the system-vms did not upgrade so I did them manually and then the storage clean-up script destroyed my systemVMs and I was stuck with a zone without systemVMs. I could not do anything. Just imagine any of those above happen in production. Ouch.
I've tested 3.0.0-3.0.1-3.0.2 for about three months to get a complete picture and be able to say I can put it in production. Testing for a couple of days would not suffice for me personally. I've managed to squeeze the new 4.0 console proxy into the 3.0.2 environment so I'm very happy now with it. I think the only time I'm going to touch my environment when CS starts supporting windows 2012 and windows 8. Hopefully 4.1? Personally I do not mind if a new feature is not 100% in newer releases however if a working functionality breaks in the newer release I cannot live with that, this is the reason I'm very picky. Regards Tamas Monos DDI +44(0)2034687012 Chief Technical Office +44(0)2034687000 Veber: The Hosting Specialists Fax +44(0)871 522 7057 http://www.veber.co.uk Follow us on Twitter: www.twitter.com/veberhost Follow us on Facebook: www.facebook.com/veberhost -----Original Message----- From: Ahmad Emneina [mailto:ahmad.emne...@citrix.com] Sent: 21 December 2012 10:46 To: cloudstack-users@incubator.apache.org Subject: Re: 4.x for production This suggestion below is spot on. I can add, test your primary use cases vigorously for a couple days. Then verify things like resources, make sure theyre inline with what cloudstack is reportin, with the underlying infra(esp. storage) I've been using 4.0 without a hitch since its release. CentOS 6.3 + xenserver nfs and iscsi. Ahmad On Dec 21, 2012, at 2:30 AM, "Tamas Monos" <tam...@veber.co.uk> wrote: > > I highly recommend a test infrastructure you can try upgrades before you > touch your live production environment!
