You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Nik Martin <ni...@nfinausa.com> on 2012/12/21 01:31:24 UTC

4.x for production

Building on my last issue with port forwarding, is 4.0 production 
quality? I have a very new public cloud that I have some customers on, 
and it would be bad if I upgraded and things went bad.

Any thoughts?
-- 

Regards,

Nik

Nik Martin
nfina Technologies, Inc.
+1.251.243.0043 x1003
http://nfinausa.com
Relentless Reliability

Re: 4.x for production

Posted by Nik Martin <ni...@nfinausa.com>.
On 12/21/2012 05:07 AM, Tamas Monos wrote:
> 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.
>

Thanks for the response.  The proper usage reporting is important, as is 
  stability since we're new in the cloud hosting business. Luckily we 
are also in the hardware business too so I can stage a cloud on 3.02 and 
migrate to 4.1 in a sandbox without affecting live customers.

Nik
> 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.Emneina@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" <ta...@veber.co.uk> wrote:
>
>>
>> I highly recommend a test infrastructure you can try upgrades before you touch your live production environment!
>
>


-- 

Regards,

Nik

Nik Martin
nfina Technologies, Inc.
+1.251.243.0043 x1003
http://nfinausa.com
Relentless Reliability

RE: 4.x for production

Posted by Tamas Monos <ta...@veber.co.uk>.
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.Emneina@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" <ta...@veber.co.uk> wrote:

> 
> I highly recommend a test infrastructure you can try upgrades before you touch your live production environment!



Re: 4.x for production

Posted by Ahmad Emneina <Ah...@citrix.com>.
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" <ta...@veber.co.uk> wrote:

> 
> I highly recommend a test infrastructure you can try upgrades before you touch your live production environment!

RE: 4.x for production

Posted by Tamas Monos <ta...@veber.co.uk>.
Hi,

If you are on 3.0.2 I'd recommend to stick with it for production.
I've tried to update earlier on from 3.0.2 to 4.0 and found some problems I cannot go in production with.
Hopefully by 4.1 those will be fixed and I'll try upgrading again. 

I highly recommend a test infrastructure you can try upgrades before you touch your live production environment!

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.martin@nfinausa.com] 
Sent: 21 December 2012 00:31
To: cloudstack-users@incubator.apache.org
Subject: 4.x for production

Building on my last issue with port forwarding, is 4.0 production quality? I have a very new public cloud that I have some customers on, and it would be bad if I upgraded and things went bad.

Any thoughts?
-- 

Regards,

Nik

Nik Martin
nfina Technologies, Inc.
+1.251.243.0043 x1003
http://nfinausa.com
Relentless Reliability