Archive for August, 2009
Like I announced in one of my previous posts, towards the syslog-ng OSE 4.0 release I’m going to make smaller, short-term supported releases. The first of these, called syslog-ng 3.1 is nearing completion, and thus a status report is due.
Here’s the original plan (quoting the roadmap page here):
- support tags for syslog messages: each message can be marked with one or more tags, then apply filtering based on tags
- patterndb: add tag support
- patterndb: v2 database format support
- patterndb: add parsers for IPv6 addresses and hex numbers
- converge macros in templates and name-value pairs even more (right now it is not possible to use any macro in match())
I’ve just pushed out another set of updates to our git repository, which:
- adds tag support: a new tags() filter and a tags() option for all sources and a builtin logic to assign the syslog-ng source name as a tag (in the format: .source.)
- adds support for patterndb v2 and a newly introduced but compatible v3 format
- adds “pdbtool” a new utility for managing patterndb files (not yet complete)
- a couple of new parsers (IPv6, ANYSTRING, FLOAT)
The last item in the roadmap is not yet addressed, in fact I haven’t even started it yet. I’m thinking about leaving that out altogether in order to have 3.1 released as soon as possible. If you have an opinion about that please don’t hesitate to post it here on the mailing list.
If you are experimenting with patterndb you are advised to use the 3.1 branch as development happens here. Of course if we find something that affects our current stable 3.0, I’m backporting the fix, but since 3.0 is stable, I’m only backporting bugfixes and not new functionality.
If you are interested you can get the sources via git, or if you prefer a tarball, just drop me an email.
BalaBit has grown quite a lot in the last 9 years since it was founded, these days there are about 60 employees and more than 50% of that is working in the development field (give or take a couple, I’ve lost count some time ago). As we currently work on 4 products, support 5-6 CPU architectures and a host of different Operating Systems, automation in development is a must.
We try to automate everything and that means a lot. Some examples:
- preparing the development workstation for development/testing work in 15 minutes for any of our products
- building source code for tens of CPU/OS combinations by issuing a single command
- creating bundles of intermediate components when generating setup packages
- doing releases
- test automation
- and a host of other things
Some of these solutions are completely our own development, others are derived from public projects, and as BalaBit tries hard to be a good friend of Free, Libre and Open Source Software (FLOSS) we try to contribute back to projects that we use.
A couple of weeks ago, I published our modified version of dogtail, a test automation framework for AT-SPI based applications. We maintain our own dogtail in-house and since our patches were not accepted, we published our changes in a public git repository.
Earlier, one of our developers contributed to WAF to support building with Microsoft Visual C++, we’ve been using his work in two of our internal projects.
And this time, we published cccl a wrapper for MSVC to make it compatible with the gcc command line, in order to compile autoconf based projects under MSVC.
As you could guess, BalaBit is primarily a UNIX/Linux shop, but we need to support products aimed at Microsoft Windows, however with some heavylifting combining the best of both worlds is possible. And we’ve never been afraid of challenges.
Hopefully you can use some of these results, maybe even contribute back.