Hi Jay,
On Fri, 2011-05-06 at 11:36 -0400, Jason Guiditta wrote:
On Fri, 2011-05-06 at 16:09 +0100, Mark McLoughlin wrote:
> Hey,
>
> Before hacking on Aeolus, I wanted to have a dev setup where:
....
> My notes below. I'd have put them here:
>
>
http://www.aeolusproject.org/page/Development_Setup
>
> but perhaps this is too sadistic a setup to be generally recommended?
>
> Thoughts?
Mark, nice notes, I think those would be great to replace the content of
the above wiki page.
Okay, I've done that now:
http://www.aeolusproject.org/page/Development_Setup
There are a couple things I think are missing, but we could update
them on the page as people hit problems. For instance you dont build
and install the connector/console (in conductor/services), so this
setup will not actually build images.
Nice catch! Obviously, I hadn't actually played with image factory at
that point :)
Another thought is that it may still be less effort (and not magic)
to
build the conductor rpm and install it to get all the deps (including
the services mentioned above), instead of manually doing it. You don't
have to actually run from the rpm, but it might be a bit simpler (that
is what I usually do).
Cool, I added that
Anyway, thanks again, this is similar to what I do for my dev setup
when I am not running the rpms/puppet-managed version, and is a nice
doc addition, imo.
Thanks,
Mark.