I am saying you should export your db and run a test upgrade against it using the 4.4 branch so we can make sure it works correctly by the time we release. Op 19 jun. 2014 19:10 schreef "Carlos Reátegui" <create...@gmail.com>:
> Hi Daan, > > I have not tried 4.3. I saw some of the issues people were having and > decided to hold off from trying. > > Do you suggest I try with 4.3 or should I build my own deb packages and > try 4.4? > > BTW I am on ubuntu 12.04 + XenServer 6.0.2 > > > On Jun 19, 2014, at 12:35 AM, Daan Hoogland <daan.hoogl...@gmail.com> > wrote: > > > Carlos, please export your db and do a test upgrade on a lab machine? > > Now is the time to solve any upgrade issues in 4.4. > > > > Have you tried the 4.3 upgrade already? > > > > regards, > > Daan > > > > On Wed, Jun 18, 2014 at 7:04 PM, Carlos Reátegui <create...@gmail.com> > wrote: > >> Hi Rohit, > >> > >> The awsapi was one of the reasons we chose to use ACS. We have > developed some internal tools and apps to manage our deployments on AWS > that we want to re-use on ACS. We have not been able to use it yet because > it was broken in 4.1.1. We tried to upgrade to 4.2 and were unsuccessful > and are now waiting for 4.4 to finally upgrade and hopefully be able to use > the awsapi. > >> > >> We use ACS internally for development and testing of our applications > that we push to AWS. > >> > >> thanks, > >> Carlos > >> > >> > >> On Jun 18, 2014, at 12:11 AM, Rohit Yadav <bhais...@apache.org> wrote: > >> > >>> Hi, > >>> > >>> Who uses "awsapi" or any other EC2 compatible interface such as > ec2stack > >>> with CloudStack (or CloudStack distros such as Citrix CloudPlatform) in > >>> production? And, if marketing and publicity are/were big motivation(s)? > >>> > >>> In case you don't want to discuss on this thread, please take this > >>> anonymous poll: > >>> > http://www.polljunkie.com/poll/fbyfdc/who-uses-awsapi-with-cloudstack-in-prouduction > >>> > >>> # Some stats > >>> > >>> I've been watching Collab14 videos and found references where many > speakers > >>> reference overall CloudStack codebase to be about 1.5M (million) lines > of > >>> Java code which is not "exactly" true. Let me share some findings; > >>> > >>> - As of today, CloudStack master is about 1.7M lines of Java code [1] > >>> - CloudStack "awsapi" artifact is 1.04M lines of Java code [2] > >>> - Code excluding "awsapi", tests and license/comment is about 590k > lines of > >>> Java code [3] > >>> - The core excluding plugins, api and the above is about 300k lines of > Java > >>> code [4] > >>> > >>> Why should I care: > >>> - some useful/fun stats to keep in mind > >>> - it's not a giant mammoth that cannot be fixed or developed upon > >>> - encouraging for new developers that if they try they can understand > and > >>> fix it > >>> > >>> FYI, this started on twitter yesterday: > >>> https://twitter.com/_bhaisaab/status/479007075414974465 > >>> > >>> [1] cd cloudstack-repo && find . | grep java$ | xargs cat | wc -l > >>> [2] cd cloudstack-repo && find awsapi | grep java$ | xargs cat | wc -l > >>> [3] cd cloudstack-repo && find . | grep -v awsapi | grep -v [tT]est | > grep > >>> java$ | xargs cat | grep -v '^//' | wc -l > >>> [4] cd cloudstack-repo && find . | grep -v awsapi | grep -v [Tt]est | > grep > >>> -v plugins | grep -v api | grep java$ | xargs cat | grep -v '^//' | wc > -l > >>> > >>> Regards. > >> > > > > > > > > -- > > Daan > >
