+1. test your use case diligently, then push to prod.
On Wed, Feb 13, 2013 at 9:09 AM, Tamas Monos <tam...@veber.co.uk> wrote: > Hi, > > I am personally still using 3.0.2 because we have our public services up > for around a year now and the previous 4.0.0 upgrade path was broken due to > template and usage problems especially on Vmware. > > The usage issue meant to be fixed in 4.0.1 (which just got released) and > the template problem will not affect you if you start with 4.0.1 from > scratch. > Put up a test environment with 4.0.1 see if you are happy with it, check > usage by yourself and if you are happy go live. > Keep that test environment for further upgrade tests as upgrades can > always be problematic even if the product is stable. > > 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: Nik Martin [mailto:nik.mar...@openfra.me] > Sent: 13 February 2013 15:58 > To: cloudstack-users@incubator.apache.org > Subject: CS 4 Production quality? > > Would Cloudstack 4 be considered usable in a production environment? I > looking to build a new cloud using CEPH as Primary Storage, so I'm > wondering if starting with 4 in the next 4 weeks is advisable yet. > > This will be a public cloud, so downtime won't be tolerated very well. > > Nik Martin >
