Yes once again and for a long time now I think, I moved to i3. It does not make so many thing than Awesome, however working on multiple screen with it, it’s better.
That’s why I wanted to make a new test with it and it’s now adopted. I spent a little bit time on reconfiguring all my needs (workspaces depending my screen configuration, opening app on a defined workspace, keyboard bindings etc…).
And finally MariaDB 10 is out! I’m exited to finish my book about it. Here are the news:
Replication MariaDB 10 sets a new standard in performance. It is many times faster than previous generations of MariaDB and especially legacy database MySQL thanks to new features including parallel replication and a further advanced group commit. Also, the replication slaves are now crash-safe. It’s also now possible to replicate data from multiple master servers giving a complete view of the distributed data across big datasets for real-time analytical purposes via the multi-source replication feature.
Some of you will tell me that most utility is doing it as well. And that’s right, but with ccze you will be able to colorize everything with a pipe. For example when you play with a verbose service like Pacemaker, you need to get colorization if you want to win time. Here is an example:
tail -f /var/log/syslog | ccze -A
A meetup on Ansible and SaltStack will take place in Paris next Monday. It unfortunately has not been initiated on the traditional meet up website and you may missed it like me.
So if you’re interested by those two configuration tool outsiders, follow the link. Both tools are written in Python, that why it is a Python meetup at first.
I’m happy to participate to the meetup as this is the first one, I’m sure I’ll learn interesting things on it and meet new faces :-)
When you manage Postfix and have a trouble with your mail infrastructure, you may want to set in maintenance your Postfix without loosing any mails. Here is a way to hold the queue, giving the time to analyze the problem and then release the queue.
I’ve wrote some tips on it. I hope it will help you.
Packer is a tool for creating identical machine images for multiple platforms from a single source configuration. You can win a lot of time by testing your application on multiple environments (AWS, OpenStack, VirtualBox, Vmware…).
Let’s say you’ve got a LAMP environment to deploy in production on OpenStack. However, you can’t perform your development/integration on it as you don’t have access yet. You can’t loose time and wait for it to test.
When you have a huge amount of mail to deliver, you can’t release the queue at once and let the server maximize the outgoing mail throughput ! The result will be: you’ll get blacklisted from a lot of MX servers.
That’s why you should take care of it and do traffic shaping. I’ve wrote a little tips on it.
