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:
- I build and run all the main Aeolus-specific bits from git, to make
it easy to debug and modify anything I need. I figure I want
conductor, deltacloud, iwhd and image factory
- I want to do as much as non-root as possible to avoid needing to
change system configuration or screwing up a RPM/puppet install
of Aeolus
- I want to have all the various daemons running in the foreground to
make it easy to keep an eye on logs, kill them if needed or debug
them
- I want to avoid as much "magic" going on as possible - even if
means making some work for myself, I'd prefer to get a feel for all
the pieces of the system rather than having something done
automatically that I don't know about
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?
Cheers,
Mark.
Mark, nice notes, I think those would be great to replace the content of
the above wiki page. 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.
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). 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.
-j