On Thu, Jul 28, 2011 at 04:28:58PM -0400, Jason Guiditta wrote:
> * Interface with Image Warehouse. We're already doing this
to some
> extent, but two major areas came up on the call today. The first is
> that a lot of what we're doing is already supported in the
> aeolus-image command-line tool. To avoid code duplication and
> reinventing the wheel, we'd like to break out a common library we can
> both use. (This also applies to image importation.) Obviously, we'll
> want to work with the Infrastructure team around aeolus-image. Second,
> we endeavor to switch from our custom-written WarehouseModel code
> using rest-client and nokogiri to ActiveResource.
Curious on this decision - rest-client is able to return things in
ActiveResource style, why is a switch needed? Or rather, what is the
benefit? I ask, because we use rest-client in many aeolus components
(including non-direct components, like deltacloud), and adding a
different rest client adds a new dep, so I want to make sure we have a
really good reason to do so after all the recent effort to decrease our
number of dependencies.
It's not so much that we want to swap one technology for another, as it
is that we identified the current interface as being fairly roundabout
and inefficient. We had hoped that switching to ActiveResource would
clean this up. Perhaps this is erroneous.
That said, isn't ActiveResource a native component of Rails 3? Or is the
goal to keep aeolus-image from requiring Rails?
-- Matt