Linux 🐧

Last week I posted about upgrading my servers to CentOS 7, one of the main factors about upgrading to CentOS 7 was the jump in kernel version (from 2.6.x to 3.10.x). Also, it was so that I could use more modern versions core of software without having to worry about installing numerous additional repos. The funny thing is that all of the software I have been waiting to use have been available in both Fedora↗ and Ubuntu↗ for quite a while, so why have I waited? ...

==PLEASE NOTE: THESE INSTRUCTIONS ARE NOW OUTDATED, SEE THIS POST FOR AN UPDATE== After I dabbled with CentOS 7 a few weeks ago I decided to take the plunge and upgrade the few servers I run at DigitalOcean↗ to CentOS 7. I run two machines, one is a Puppet and Salt Master, the second runs Docker. Puppet Master Server A while back I added a few bash scripts to deploy both a Puppet Master & Agent↗ to GitHub, as Puppet provide a repo for CentOS 7 I decided to just update the installation script to use this repo and then give ago. I use stephenrjohnson/puppet↗ to deploy the Puppet Master. the Puppet part worked, however it failed to install Passenger and its Apache module because there is no mod_passenger available for CentOS 7 yet. To get around this I grabbed the require packages from The Foremans nightly builds↗ repo. This turned the initial yum install line into the following; ...

As I didn’t get chance to have a play with the pre-release CentOS 7.0 builds I decided to wait until DigitalOcean↗ lauched their image↗ which they did just in time for the weekend. Check the IP Address First thing I did was type in ifconfig and got ….. First play with CentOS 7.0 1/5 [root@server ~]# ifconfig -bash: ifconfig: command not found ….. not a good start, have dabbled with a Fedora↗ when I installed OpenShift I remembered about the ip command ….. ...

I have been missing in action for a while, busy with work and other “stuff”. Since I last posted ….. Docker 1.0 has been released.↗ CentOS↗ 7 has been released↗ . I have updated the sites theme again to use So Simple↗ . Aphex Twin’s Long Lost Caustic Window LP was released.↗ Also new albums from Neil Finn↗ , Anathema↗ and Crippled Black Phoenix↗ have all been released. I have written a blog post for work↗ on MFA in AWS. ….. suppose I had better make more of an effort to post now that everything has caught up. ...

Having ran a local copy of OpenShift Origin↗ using VirtualBox↗ I decided to have a go at running it on a Digital Ocean↗ Droplet running CentOS 6.5. This should be easy as there is an installer↗ which claims; You’re one shell command away from deploying your own Platform as a Service. Well, sort of, after a few failed installs I finally managed it using the following (this assumes you are running a clean and minimal CentOS 6.5 installation) ...

Sysdig↗ looks like it could be a useful addition to a sysadmins list of tools, it is described as; Sysdig is open source, system-level exploration: capture system state and activity from a running Linux instance, then save, filter and analyze. Think of it as strace + tcpdump + lsof + awesome sauce. With a little Lua cherry on top. It’s easy to install↗ …. Sysdig 1/1 curl -s https://s3.amazonaws.com/download.draios.com/stable/install-sysdig | sudo bash …. and even easier to run …. ...

I have been playing my Digital Ocean↗ server a lot recently. Breaking it, fixing it and then rebuilding it, while I had documented my puppet installation it was getting to be a pain to copy and paste with each rebuild, so I pulled together a few scripts↗ from various sources to make the rebuilds a little less of a chore. To install fresh Puppet Master all I need to do now is run the following command; ...

Vagrant allows developers to bring up local development machines in a controlled method using pre-built configuration files called boxes. Once a box has been installed on the developers local machine it can be powered on with the following command; Vagrant & Puppet 1/2 vagrant up When the box is brought up it automatically provisions itself using a number of provisioners including Puppet, this means that the production deployment scripts can also be run on local development copies of the instances. The instances on the local machines are powered by Virtualbox and there Windows, Linux and Mac versions of Vagrant. ...