QA validated with the fixes given by Edison. There is one minor issue reported related to rolling back transaction. Prachi says it is not a major issue. We are good to go. Edison is making new build with all fixes in and will do one more OOTB install and check. Thanks all
2012-10-09 15:48:12,875 DEBUG [db.Transaction.Transaction] (catalina-exec-int-9:null) Rolling back the transaction: Time = 1 Name = -UserCredentialsDaoImpl.getByCertUniqueId:61-DatabaseCallback.intercept:34-AuthenticationHandler.invoke:118-Phase.invoke:318-AxisEngine.invoke:251-AxisEngine.receive:160-HTTPTransportUtils.processHTTPPostRequest:275-AxisServlet.doPost:133-HttpServlet.service:637-HttpServlet.service:717-ApplicationFilterChain.internalDoFilter:290-ApplicationFilterChain.doFilter:206; called by -Transaction.rollback:887-Transaction.removeUpTo:830-Transaction.close:649-UserCredentialsDaoImpl.getByCertUniqueId:68-DatabaseCallback.intercept:34-AuthenticationHandler.invoke:118-Phase.invoke:318-AxisEngine.invoke:251-AxisEngine.receive:160-HTTPTransportUtils.processHTTPPostRequest:275-AxisServlet.doPost:133-HttpServlet.service:637 -----Original Message----- From: Wido den Hollander [mailto:w...@widodh.nl] Sent: Tuesday, October 09, 2012 3:02 PM To: cloudstack-dev@incubator.apache.org Subject: Re: [ASF40][DISCUSS] Split AWS API / CloudBridge into a separate project On 10/09/2012 11:20 PM, Sudha Ponnaganti wrote: > One more fix is needed from Edison. Wait for it if you are going to check it. > Edison post fix details here once you are done > I just worked on this with Edison and pushed a couple of commits to the 4.0 branch. The installation went fine on a Ubuntu 12.04 machine, but I never used the AWS API before, so I'm not sure how to deploy it. Wido > -----Original Message----- > From: Chip Childers [mailto:chip.child...@sungard.com] > Sent: Tuesday, October 09, 2012 2:14 PM > To: cloudstack-dev@incubator.apache.org > Subject: Re: [ASF40][DISCUSS] Split AWS API / CloudBridge into a > separate project > > On Tue, Oct 9, 2012 at 5:10 PM, Wido den Hollander <w...@widodh.nl> wrote: >> >> >> On 10/09/2012 07:48 PM, Chip Childers wrote: >>> >>> On Tue, Oct 9, 2012 at 12:31 PM, David Nalley <da...@gnsa.us> wrote: >>>> >>>> On Tue, Oct 9, 2012 at 12:17 PM, Chip Childers >>>> <chip.child...@sungard.com> wrote: >>>>> >>>>> OK, >>>>> >>>>> So let me try to summarize the opinions here: >>>>> >>>>> We have a couple of folks that think it should be split back out, >>>>> but more are erring on the side of keeping the functionality. >>>>> >>>>> Assuming that we keep the code in the ACS repo for now, the second >>>>> question is one of packaging. Wido proposed a "cloudbridge" >>>>> package for this specific code. I think that makes sense, in that >>>>> it gives us options for breaking apart from CS in the future. >>>>> >>>>> Can we get some opinions about the packaging specific portion of >>>>> the issue now? >>>> >>>> >>>> >>>> So we release source code - so from a release perspective I think >>>> it makes next to no difference. >>>> For the convenience binaries that are being built it might make a >>>> tremendous amount of difference - up to an including functionality >>>> not working I'd specifically not want to substantially change RPMs >>>> at this stage. >>>> Debs could have this broken out since it has never been there, but >>>> it would all need to be tested. >>>> >>>> --David >>>> >>> >>> OK, so let's move forward with this plan: >>> >>> 1 - Get the DEB package built (as a separate package). >> >> >> This will be hard. Since we have a central control file for the >> Debian packaging it will be something like cloud-awsapi or >> cloud-bridge >> >> In the spec file I saw that that cloud-awsapi is depending on >> cloud-deps, so that starts to tie it in with the rest of the >> code-base on a packaging level. >> >> >>> 2 - Test the AWS API via a DEB package installation >>> >>> We don't touch the RPM's now, since it's already been tested and (as >>> of this morning) validated as working. >>> >>> Does someone want to pick up the DEB packaging for Wido (since I >>> assume he's sleeping right now)? >>> >> >> Not a sleep yet :) I'll be offline soon though, but I can follow up >> on work done over night (for me) and continue in the morning on what >> Edison came up with. >> >> Wido >> >>> -chip >>> >> > > Wido, > > Edison has committed his DEB packaging for AWSAPI. Can you take a quick peak > at it and suggest any changes that may be necessary? Keep in mind that we > didn't change the packaging strategy for the RPMs... > so perhaps it's not as broken out as you would have originally liked. > > QA has started testing, but it would be very helpful to get your eyes on this > before we call it done. > > Thanks! >