New in this release is support for blame, and upgrade to libgit2 0.20. Detailed list of changes follows.
- Renamed Repository.head_is_orphaned to Repository.head_is_unborn
- Repository.listall_references and Repository.listall_branches now return a list, instead of a tuple
- The prototype of clone_repository changed
- Added support for blame
- Carlos Martín Nieto
- Xu Tao
- Huang Huang
- Petr Hosek
New in this release is support for push. Detailed list of changes follows.
- Rename Commit._message to Commit.raw_message
- Rename Signature._name to Signature.raw_name
- Rename Signature._email to Signature.raw_email
And some bugs fixed.
- Brodie Rao
- Fraser Tweedale
- Andrew Chin
- Carlos Martín Nieto
Finally, I found a good enough Collectd front-end: the Collectd Graph Panel (CGP). But first lets look at those front-ends which did not pass the exam:
- Collectd-web is the first I tried, maybe because it is the only one with a package in Gentoo (but it is poor package, so I ended up installing from source). My main complain is that some graphs, like the very useful context-switches, don’t work. It is also quite slow generating the graphs.
- Collection4, developed by the lead developer of collectd, did not even build. I did not insist.
Many of the front-ends listed in the collectd wiki page were discarded either because they looked like dead (no new commit in the last few years) or because their deployment process was too cumbersome (need to setup database…). But I still tried a few more:
- Sickmuse is sleek. However there are some details in the way to deployment, like there is no option to make server to listen only the local interface. Alright, it’s just Python, I can fix it… Problem is, the build process requires to install npm (the Node.js package manager), just to install another package manager named Bower, just to install the JS and CSS. I mean, WTF?
- Jarmon is very simple to deploy but requires to define every plugin in the front-end, i.e. it is unable to discover the hosts and plugins just like every other front-end does. So it is a pain in the ass to maintain.
- Visage just shows nothing. I tried to add a host and plugins through the web interface, but the interface is buggy.
Like when looking for the keys, the answer was in the last pocket. Well, the CGP web site is designed to discourage potential users. There is no documentation. I had to dig a little to find out how to get it working with Nginx for instance.
Just one note about CGP, it has two modes to generate the graphs: PNG (the default) and canvas, to generate the graphs in the browser. The canvas mode did not work for me: zooming with the mouse scroll is so sensible it is unusable; it is slow, the fan in my notebook started to run like crazy; my browser even gave me some error like “This scripts is stalled, kill it?”. But the PNG mode is fine.
Conclusion. The weakness of Collectd is the lack of a good and well established front-end. Instead there are more than a dozen front-ends of varying quality. This is my selection:
- CGP. Don’t look any further, unless you have some free time.
- Visage. This one is promising, maybe I will try again once they get 3.0 out.
- Sickmuse. If it only was less trendy and more practical… Three things to improve: the build process, deployment and usability.
Three months after the previous release I am happy to present a new major version of pygit2, the Python bindings for the libgit2 library. Follows a summary with the changes.
- New Oid type
- Changed signature of Repository.create_reference
- Reference.oid and Reference.hex removed, use Reference.target instead
- Drop del Index[path] from the API, use Index.remove(path) instead
- Drop TreeEntry.to_object
- Changed signature of Repository.checkout
- Repository.create_blob_from_file removed, use instead new methods
- Add len(TreeBuilder) and TreeBuilder.get
- Add Repository.merge_base
- Support changing the head with Repository.head = refname
- Improved support for diff
- Add support for clone
- Python 2: Support hex oids as byte strings
- Add Reference.get_object
- Add Remote.save
- Add support for branches, new type Branch
- Upgraded to libgit2 0.19
- Partial documentation review
Fourteen developers have contributed to this release, including myself, and:
- Nico von Geyso
- Daniel Rodríguez Troitiño
- Bernardo Heynemann
- Rémi Duraffort
- Andrey Devyatkin
- Hervé Cauwelier
- Jiunn Haur Lim
- Richo Healey
- Carlos Martín Nieto
- David Fischer
- Fraser Tweedale
- Jun Omae
- Xu Tao
Few weeks ago Munin was flooding me with message alerts about IO latency, read or write, going too high. Ironically it turned out Munin was the culprit. And the solution was to use rrdcached.
Lets see a Munin graph that shows pretty well the difference using rrdcached made:
Around week 21, when I deployed this optimization, writes dropped quite a lot and reads stabilized.
Now follows the step-by-step guide to use rrdcached (with Gentoo).
OVH, the hosting company where I have my dedicated serves, does some quality assurance on the Linux kernels, the ones it deploys on newly installed servers.
Now, after more than a year, there has been a new release. This is how upgraded the kernel on my Gentoo servers, which use Grub2:
# cd /boot
# wget ftp://ftp.ovh.net/made-in-ovh/bzImage/latest-production/bzImage-3.8.13-xxxx-grs-ipv6-64
# wget ftp://ftp.ovh.net/made-in-ovh/bzImage/latest-production/System.map-3.8.13-xxxx-grs-ipv6-64
# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/bzImage-3.8.13-xxxx-grs-ipv6-64
If you use Grub2, regardless of the distribution, it should work the same.
This week a hard disk from one of my servers broke. It has been replaced with just 3 minutes of downtime (kudos to OVH), and right now the RAID array is being rebuilt.
Since this is the first time this happens to me, and the server is running a production mailman service, I decided to take my time and set-up a backup MX server. This is how I did it.
Remember that I am using a Gentoo distribution, this may be slightly different in other distro. Continue reading
Update 31/12/2012: Now this is a bit simpler, since bug 448414 has been fixed.
Before we start with the step-by-step procedure to get the mailman plug-in working, lets recall how to test a munin plug-in:
$ sudo munin-run mailman
The output above is what you should get once the mailman plug-in is correctly set-up. Continue reading
If you have some problem with exim, and the logs are not enough, edit the /etc/conf.d/exim file, and add the debugging option (-d):
# Command-line options for running exim
EXIM_OPTS="-bd -q15m -d"
Then restart exim:
# /etc/init.d/exim restart
The exim daemon will not be detached from the console, the debug information will be printed to the standard output. Good luck!
This should be the last release in the v0.17 series. The master branch has already been moved to be based in the libgit2′s development branch.
New in v0.17.3:
- New Blob.size getter
- New Repository.create_blob_fromfile method
- Signature, now the time and offset parameters are optional
- Improved diff support
- Add pygit2.__version__
- Optimize usage of Travis
- Various fixes for the unit tests
- Various documentation improvements
Thanks to Alex Chamberlain, Carlos Martín Nieto, Eric Davis, Eric Schrijver, Petr Viktorin, Ridge Kennedy and W. Trevor King.