Hi Tamas, I'm probably stuck with 3.0.2 for now since I decided to use vSphere 5 (instead of the KVM install I just had). Many of the issues I've had are actually documented bugs, but since the project is somewhat in limbo I don't know how long we have to wait. I've been installing and re-installing in different configs CS 3.0.2 for about a week now, and finally got it to a sweet spot where it would run just fine with a single hypervisor. One of the things that really seems to mess it up, is enabling local storage. This tends to just make things horribly unstable. I just blew away my current setup of XenServer+KVM and am going to do another attempt (But with XenServer and vSphere) with local storage (since both are purported to support local storage). I'm sure 3.0.2 runs just fine once it's setup and it's working, but I just find it very disturbing that one small change can throw the whole system. I'd be very worried in using it production.
Thanks, Alex On Fri, Jun 22, 2012 at 5:25 PM, Tamas Monos <tam...@veber.co.uk> wrote: > Hi, > > I think 3.0.2 is not pre-alpha by far. I can easily run a production > environment on it with billing integration and customers are happy. > Nothing is perfect ever but there is always a workaround. If you could > describe what is unusable or blows up we might be able to help. > > 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: Alexey Zilber [mailto:alexeyzil...@gmail.com] > Sent: 22 June 2012 02:33 > To: cloudstack-users@incubator.apache.org > Subject: Re: CS 3.0.2 does not report router system vm. > > That's a funny place for it to show up, imho. It's a system vm. I'm > pretty sure when I was using the Xen hypervisor it was showing up under > system vm's. Then again, the 3.x branch is so pre-alpha I don't know where > stuff will show up anymore. > > Any news on when the incubator project is going to be ramped up? 3.0.2 is > essentially unusable. Just adding another hypervisor to the mix causes it > to blow up. I did notice a ton of bug fixes, but those won't show up in > any builds till the incubator project is up and running I'm guessing. > > Thanks, > Alex > > On Fri, Jun 22, 2012 at 8:38 AM, Edison Su <edison...@citrix.com> wrote: > > > > > > > > -----Original Message----- > > > From: Alexey Zilber [mailto:alexeyzil...@gmail.com] > > > Sent: Thursday, June 21, 2012 5:14 PM > > > To: cloudstack-users@incubator.apache.org > > > Subject: CS 3.0.2 does not report router system vm. > > > > > > Hi All, > > > > > > This looks like a bug in CS 3.0.2. I did a clean install. > > > Everything is > > > on Centos 6.2. Installed KVM as the first hypervisor in the cluster. > > > Launched an instance. virsh reports: > > > > > > [root@kvm1 init.d]# virsh list > > > Id Name State > > > ---------------------------------- > > > 1 s-1-VM running > > > 2 v-2-VM running > > > * 3 r-4-VM running* > > > 4 i-2-3-VM running > > > > > > > > > #3 above is the system router vm. It does not show up under 'system > > > vm' > > > > Router VM should not be shown up under "system vm". It should be under > > "zone->network->" > > > > > under the Zones. (#1 and #2 do). This is concerning because when I > > > used > > > Xen, it reported it correctly. > > > > > > Thanks, > > > Alex > > > >
