On 07/25/11 - 11:35:00AM, Matt Wagner wrote:
On Mon, Jul 25, 2011 at 05:53:17AM -0400, Chris Lalancette wrote:
> On 07/24/11 - 02:44:33PM, Hugh Brock wrote:
> > * Documentation
> > * I'd like to see the community get into the habit of creating or
> > updating wiki how-to pages as we go along. I'm not sure exactly
> > how to promote this (free beer once a month to the best new
> > page?), but I am fairly sure we do need to make the infrastructure
> > a little easier to deal with for it. Like it would be good if the
> > wiki didn't become unreachable a lot, the way the Redmine wiki
> > seems to do.
> Yes, and merging the two wikis into one would help too :).
You know, I'm hesitant to suggest that a third wiki will solve our
I'm really liking Github's wiki system. To Hugh's requirement, it
doesn't go down all the time. It also supports multiple markup formats,
so people can write in whatever is most natural to them. (As trivial as
this sounds, we want to make it easy.) We could migrate content over
from both wikis to avoid the obvious problem of having three wikis.
Of course, the obvious downside is that not all of our projects are
using Github, so it might be a little odd to have documentation kept on
an external site.
Yeah, I am liking github more and more, and I think we should move more of our
projects to it. However, for the wiki itself, I suggest we just take the
content from the mediawiki and put it in redmine. After all, redmine has to
work *anyway*, so we may as well use the wiki there.
> > * Way better logging and error reporting.
> > * All components should be using syslog if at all possible
> I don't know that I agree here. Why would I want all of my logs dumped into
> the same bucket, where it is difficult to tease them apart? I kind of like the
> per-daemon logging, as it is easy to debug the piece you care about. Maybe
> what we should have is an aggregation tool, or sos plugin, that will gather all
> of the stuff together from somebody when we need to debug multiple components.
I really don't like the idea of inventing our own log aggregator,
because we end up re-inventing the wheel. You can configure syslog to
write log files per-daemon if you want, but they'll all be in /var/log,
as opposed to having some things randomly writing to
Well, nothing should ever be writing to /usr/share/aeolus-conductor in the
first place; it is a bug that we need to fix.
As far as syslog goes, if we can make the daemons use individual files
through syslog, then I am fine with using it. However, if it requires yet more
configuration that nobody has setup by default, and yet more rubygems, then
I am not for using it. I want to make this easier to use and with less
dependencies, not harder and with more dependencies.