The first time I’ve heard about “agile” in relation to IT project I thought about yet another buzzword that does nothing to what I did back then. It was 2008 and It was my second job in IT. Before I was working as an IT administrator which basically meant that I was doing everything from installing Windows XP on workstations, maintaining Novell Netware server as well as an awesome Windows NT machine with state of the art tax application installed on it (yep, that was sarcasm).
My work routine was like this: I got to work in a morning, reviewed if backups were there and were valid. Checking emails and then proceed with my personal to do list. This list involved improving stuff in our infrastructure, implementing Bacula as a primary solution (xcopy was cool, but it wasn’t enough). Continue reading What it takes to bring agility in your organization?
It was middle of year 2011 and I decided enough is enough. I needed a new job. And this is how my long almost five years long quest began. It started slowly, with updating my CV, looking around in my area, checking companies I probably want to work for and figuring out what I’d like to do next.
Job interviews are hard. You try to prepare, dress up, go to the companys office, you talk a lot, you meet people, shake hands, talk some more and you get rejected a lot.
Essentially, seeking for a job is like looking for a publisher for your new shiny book. Or looking for a company that will create your awesome device. It’s hard, very hard. Continue reading Job interviews, do you speak them?
After years and years of struggling to join a bigger conference, I managed to see how conference looks like. Warsaw way.
That was a second edition of such conference in Poland, so I guess team is still learning. But, I must say, organization was well thought, didn’t notice bigger issues.
Conference lasted two full days of talks and ignite talks on the first day. On the first day, surprise surprise, there was also an after party. Continue reading DevOps Days Warsaw
After a long, long, long, (seriously) long time not writing, I decided to write something daily. Yes, daily.
… but not necessarily on this blog though.
In the mean time: I haven’t decided yet what to do with this space. I know I still want to write in English, but I don’t know how much technical I want to stay.
Currently I’m working with one magazine in Poland and I’m writing mainly for them instead of blogging. I’ve been thinking on translating everything I write also to English and publish it right here. That may be one way to maintain publishing here.
Another idea which came into my mind is writing about recruiting. I have a bit of experience with HR and talking to various people from different countries (Germany, US, Ireland, UK, Poland) about job. Couple of weeks ago I came across recruiter from adult industry – that was interesting.
I guess I’ll have enough material with those two.
For now my intention was just saying “hi” and getting my all thoughts together in this post.
Couchbase is a NoSQL document database designed for high scalability and availability. It’s very flexible and dead easy to configure once it’s installed. And it’s much more than simple NoSQL for documents, for example it can be used as a Memcached replacement. Continue reading Couchbase check for Nagios/Icinga
File resource in Moodle is another course element that can be used for serving files for students. It’s assumed that there will be only one file per resource, but you can upload multiple files and set one of them as default to be downloaded when student click on the resource.
We’ll be adding multiple resources and multiple files in this example. Doing so using pure php coding would be complicated enough to mess things up very easily, so we’ll use Moodle APIs to do some things for us. And it’ll be additional plus as we will be more Moodle version independent as long as API will remain not changed. Continue reading Moodle: Add (file) resources and upload files into it
As setting up Puppet server and agents using VMs provided by Puppetlabs is simple as shooting fish in a barrel, setting it up on actual servers may be a little more annoying. Continue reading Puppet common errors
Bacula by default is backing up all symbolic links as… well, symbolic links. It does not follow them and there is no option for FileSet to make it do that.
However you can make it follow symlinks to directories and back up files located somewhere else.
Example File entry:
File = /some/directory/symlink_to_dir/.
To follow and backup symbolic links file targets, you’ll have to use a trick described in my previous post – Including files from file on client machine, plus use a bit find-fu:
find /dir/to/search -type l -name "*" -printf "%l\n"
Just remember to have symlinks pointing to file using full paths, eg. /home/user/backup_me.tar.gz
Including files to be backed up from file is not a killer feature of backup software, but it’s very useful when you need to backup only set of files from large directory structure.
Using Bacula makes that a bit more complicated though because of its divided structure (Storage Daemon, File Daemon and Director). Director tells File Daemon which files to back up and where to send them, that’s why Director must know which files must be backed up. Continue reading Bacula: Icluding files list from file on client machine
Bacula is somewhat complicated backup system, but once mastered, it’s extremely convenient and comfortable solution. Still, adding new clients can be a pain if you don’t have a “standard” file set. Tuning it may take a long time, but there’s a way to make it a bit easier for you. Continue reading Bacula: List files that would be backed up using bconsole