First of all what are containers? In this context we are referring to Linux running inside a “containerised” environment i.e. an environment which is to all intents and purposes isolated from the main operating system. The containerised environment doesn’t have it’s own kernel or virtualised hardware and runs at native speeds because of this.
In what ways could a containerised environment be useful and desirable from a business perspective? The first use that springs to mind is being able to easily move your dedicated server from one hoster to another (which is the way I use it). You can simply “rsync” the contents of the container from the source hoster, then take the container down, run another quick rsync and start the container at the new hoster. This is really useful, saving hours and possibly days rebuilding the server at the new hoster in a more conventional manner.
Continue reading The merits of LXC containers
Whether in a co-location centre or at a remote site, looking after a server when you aren’t there in person can be a challenge, particularly if you are conscientious and update your servers regularly – updating a Windows server almost always requires reboot, updating a Linux server will require reboot if the kernel has been updated. What happens if the server doesn’t come up after said reboot? This happens more often than might be expected, so I find it desirable to have a way of accessing the server even if the operating system isn’t available. Traditionally this would be provided by a KVM over IP switch, which redirects Keyboard, Video and Mouse input/output via a web server integrated into a box. KVM over IP switches are expensive (the cheapest one I could find at time of print was €250 and doesn’t work well with mice IMO). However, there is an alternative which is elegant and affordable …
Continue reading A cost effective alternative to KVM over IP switches