Cool Tools

by Oliver on Saturday, October 15th, 2011.

Today at DevOpsDays Göteborg we rounded out the day’s events with an Open Space session on Cool Tools. Basically I wanted to have a session where as experts in our field we can suggest life-saving, life-changing or just handy tools we use from day to day that others may not be aware of. Each person got up, said some small amount about the tool in question and wrote it on the board. In the end we had a board full of suggestions and used up all the time!

So in the interests of posterity here is the list:

So there you have it. Please let me know if any of the URLs are wrong, and I hope some of these links help you in some way!

Tags: , , ,

Saturday, October 15th, 2011 Tech
  • Thanks Oliver, nice collection, I will try to explore those!

    Here are a few others I used before that might be added to such a list. I hope they are useful to someone out there.

    tig – console UI for git, similar to gitk
    htop – top on steroids
    rancid – network device config versioning
    smokeping – tool for monitoring the quality of network connectivity
    NeDi and netdisco – tools that can help in searching machines in a large network
    BackupPC – powerful and scalable backup solution ideal for hordes of nearly identical Linux machines

  • Thanks Oliver for writing these up!

    It’s been a cool and inspiring session.



  • Phil Pirozhkov

    RVM and rb-env are mutually exclusive. ruby-build should be used in conjunction with rb-env.
    No idea how keepass, a windows utility got in the list.
    vimdiff? it’s one specific vim feature.

    I would add some interesting DevOps tools below.


    Deployment (leaving capistrano aside):

    Cloud management

    Open source github clone


    and much more

    But the best approach is to stop collecting cool tools and start building something already.

    • Phil Pirozhkov

      Yep, travis-ci also

    • Hi Phil, thanks for your additional links.

      Were you in the Cool Tools session? It was OS-agnostic so we did have some Windows users there who suggested some tools – even more important since the general approach to Windows is that of a black box so additional real diagnostics wherever possible is a good thing.

      In reply to your last point, there are always better ways of doing our jobs and often we don’t have the time to catch up on every new project on Github or just aren’t aware of things which can make our workflows more efficient. It’s not the end goal to amass the most tools but it helps to use the best tools to get the job done.

      • Hi Oliver,

        Sorry for very late reply – I’ve came across this answer by doing a google search on my name plus vim, lol.
        No, unfortenately I haven’t attended the session, but there were some very nice topic related sessions in a company I was working in a while ago.

        I completely agree with your point. It’s always fun to learn new tools, but it does make sense to spend time if the knowledge and use can save time, not just for fun and self-education. In fact, I only use very few of these high-tech tools and that’s pretty enough to complete my tasks. When it comes to a limit and one find himself spending most of the time on repetitive tasks or over-complicated development this might be a sign to review the app or dev approach and learn and use one of the tools in the list (or nosql list, or …).

        BR, Phil

  • Yeah, thx!