I'm sure this is an easy decision for most but I'm new to asl. This is also my first post on art.
I was wondering if using the asl-bleeding channel on a production server is a bad idea. I've been using asl (from the asl-bleeding channel) on a FC6 box (that only has two sites) for a couple of months now. It's been working fine after some modifications to the websites' code.
But I also have a CentOS 5 server and was wondering if it's a bad idea to use asl on it since it would be from the asl-bleeding channel and there are about 50 sites on it. Common sense tells me not to use software that isn't production quality on a production server. But I'm going to have to disable SELinux since there seems to be a bug with centos5, selinux and plesk. So maybe it would be better to use the bleeding channel rather than nothing at all.
Its very stable right now, the vast amount of development is going into the user interface piece, which is what is -bleeding about it. The current release schedule is for the beta release on the 31st, and then then GA in august. Whats making it "beta" right now is that parts of the web interface still aren't operational.
That's very good to know. Thank you Scott. That makes me feel a lot better. I was really excited to see the 2.6.19 kernel added to the centos5 channel. I'll be getting a subscription for that server sometime this week.
Ive got another kernel update that probably wont be available til after 2.0 is GA. This one will add in the ability to make snapshots of the running disk, kind of like the Revert button in vmware. Useful for doing upgrades, or real-time backups.
Nothing specifically on the ASL front, but all the HA components from Fedora 7 are in the ASL kernel. The backend piece is there to handle distributed alerting (so you can have a central console for multiple ASL systems). Making the GUI aware of that is something on the 2.2 candidate list.
