Posts

UPDATE 26/07/2015 In typical fashion, a few weeks after posting this Docker themselves released a much better version than mine, you can install it using the following commands; Update to CentOS 7 Docker install one-liner 1/2 curl -sSL https://get.docker.com/ | sh systemctl enable docker && systemctl start docker docker run hello-world What follows is the original, now mostly redundant post. It’s been a while since I touched the code for the one-liner Docker installer I wrote a while back....

As I have mentioned a few times on this blog I tend to use DigtialOcean↗ to spin up servers for testing and to host some of my projects. I also still use CentOS 7 as my preferred OS. Each time I boot a droplet I run few a couple of tasks to get the server how I prefer it. Run a yum update Enable swap Install & configure Fail2Ban Enable firewalld Install vim-enhanced, deltarpm & enable EPEL↗ As I am lazy and sometimes re-launch instances several times when working on a project I decided to write a quick script to do the above so I don’t have to↗ ....

I am going to be playing with OpenStack over the next few weeks so I decided to create a Vagrant script which would bootstrap a working OpenStack Kilo↗ installation using RedHat RDO↗ . It uses my CentOS 7 Vagrant box↗ and works with both VirtualBox and VMWare Fusion. To get it up and running create a folder for the Vagrantfile to live; Quick OpenStack Kilo Installation 1/4 mkdir -p ~/Machines/OpenStack/ Download a copy of the Vagrantfile;...

After being nagged by the gaffer to try OpenShift Origin V3 I finally got round to running a test server using Vagrant on my Mac. I must say, going into this that the documentation at this stage is struggling a little to keep up with the development and these instructions are the results of much trial, error & Googling. Also, the product is very much still in active development and there have been several bugs, like this one↗ , which have caused the instructions below not to work....

I haven’t installed an ELK stack since CentOS 7 came out, all of the components which go to make up the stack have been updated quite bit since then so I decided to have a go at installing the stack on a clean CentOS 7 installation. ELK? ELK is a term used for a combination of three Open Source products from Elastic↗ ; Elasticsearch↗ — Search & Analyze Data in Real Time Logstash↗ — Collect, Parse, & Enrich Data Kibana↗ — Explore & Visualize Your Data All three products can be used independently, but when they are used together you find yourself with both a powerful and scaleable central logging service....

I spent Wednesday out of the office at the 2015 AWS Summit in London. It was the first time I had been to a full on AWS event and I must say I was impressed by the scale (pun intended). The main keynote was interesting, and it was great to hear all about new Elastic File System↗ which is going to be a godsend for those who need to have some level of shared storage....

As everyone who knows me will already know, I am a little bit opinionated when it comes to music. However, I haven’t really had a decent sound system for quite a few years. I decided mid last year that I would do something about it and not only start getting back into vinyl (I know, such a hipster) but also get a decent sound system, so started saving. For quite a while I was looking an all-in-one system like the Teac LP-P1000↗ however, I decided I would end up painting myself into a corner with it as I would be only be able to use it in one room, I then started looking at other options....

One of the first things I do on a new server is install fail2ban↗ . I have written about it before, but that was back when I was still using CentOS 6. Now I am using CentOS 7 the installation has a few more steps. Firstly, as EPEL is not enabled by standard on most CentOS 7 installations enable the repo and then install fail2ban. Fail2Ban on CentOS 7 1/8 yum install -y epel-release && yum install -y fail2ban Once installed you can run the following to setup a check and block for failed SSH logins (it bans for 24 hours after three login failures);...