The ORM in the AWS module is 90% used by S3. The dependency is mostly abstracted by a DAO layer; there is another dependency on transactions. I believe Rajesh B is already working on this aspect and there is a bug open on it.
-- Chiradeep On Jun 27, 2012, at 21:52, "David Nalley" <da...@gnsa.us> wrote: > > > > > On Jun 28, 2012, at 12:45 AM, Sheng Liang <sheng.li...@citrix.com> wrote: > >>> In short, I see three options (please comment if you see more) 1. Rip out >>> hibernate and replace with some other ORM 2. Make the AWS API bits an >>> optional non-default part of the build. >> 3. Declare that hibernate is a system requirement for CloudStack >> >> I prefer option #1. It is the cleanest. I don't think it will be very >> difficult to rip out Hibernate. >> >> Sheng > > > > That is my personal inclination as well, though I am somewhat reticent to say > so, since I am not doing any of the work to rip and replace. At the same time > choice of ORM is a big issue. I know, for instance that Alex was looking into > finding another ORM for the rest of CloudStack. When I initially looked at > the Hibernate issue, Prachi told me she thought it was about 2 weeks worth of > work. > > > --David
