Re: Send Juju logs to different database?
On 6 May 2015 at 06:49, Lauri Ojansivu x...@xet7.org wrote: Hi, today at Ubuntu Developer Summit: http://summit.ubuntu.com/uos-1505/meeting/22437/juju-share-and-juju-sos/ Speakers talked about changing all logging to go to MongoDB, so I asked question at IRC: xet7 Would it be possible to use some different database than MongoDB for logs, because of current problems in MongoDB ? https://aphyr.com/posts/322-call-me-maybe-mongodb-stale-reads It is more likely that Juju will grow the ability to send logs to external log services using the syslog protocol (and perhaps others). You could use this to log to your own log aggregator or database. This feature has been discussed but hasn't been planned in any detail yet (pull requests would be most welcome!). The changes currently being made to Juju to support logging to MongoDB also lay the groundwork for logging to external services. This should land in the coming weeks. - Menno -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: Resolving the same windows test failures again
On 05/05/2015, Andrew Wilkins andrew.wilk...@canonical.com wrote: Those fixes were not made on v5, and only existed on v6-unstable. I later came along and merged some changes into v5 and updated Juju's dependencies.tsv to the latest commit on v5. That meant the fixes were dropped. Not easy to track this history on github, but as far as I can see v6-unstable did not exist when those changes were merged. Looks like v5 was then renamed in the web ui to v6-unstable and v5 was pushed up from an earlier revision. When your branch went to bump the rev, it therefore dropped those changes (and when I went to pull my v5 branch locally, it complained of diverged branches). Martin -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Send Juju logs to different database?
Hi, today at Ubuntu Developer Summit: http://summit.ubuntu.com/uos-1505/meeting/22437/juju-share-and-juju-sos/ Speakers talked about changing all logging to go to MongoDB, so I asked question at IRC: xet7 Would it be possible to use some different database than MongoDB for logs, because of current problems in MongoDB ? https://aphyr.com/posts/322-call-me-maybe-mongodb-stale-reads I also read from juju website that you are readying for MongoDB 3.0: http://blog.labix.org/2015/01/24/readying-mgo-for-mongodb-3-0 And also that some have switched from MongoDB to PostgreSQL: https://news.ycombinator.com/item?id=9178773 http://developer.olery.com/blog/goodbye-mongodb-hello-postgresql/ So my questions are: 1) Would it be possible to use for example PostgreSQL for logs etc? 2) Are the issues in mentioned articles linked above still valid in MongoDB 3.0 ? BR, Lauri -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
