Virtio disk drivers provide increased performance on virtualised systems by allowing the guest operating system to co-operate directly with the hypervisor – in effect, the drivers “know” they are running in a virtual environment, and can operate more efficiently as a result. If you have a Linux server already running on the OpenHosting cloud, this short tutorial is designed to help you optimize performance by switching your drives to Virtio block devices. Drivers for Virtio are built into most modern versions of Linux as standard, so switching disk devices over can be as simple as editing two configuration files and rebooting the server with the drives attached as virtio block devices. Editing boot settings can be daunting, so it’s important to know that any problems can be quickly and easily corrected using only a Linux LiveCD.
If you find yourself frequently connecting to your servers via SSH, having the ability to do that quickly is sometimes essential and always welcome. SSH keys will automatically log you into your server from a particular computer without needing to enter a password.
When you generate an SSH key, you’re given a public and private key. The public key sits on the server you’re trying to connect from, and the private key on the server you’re connecting to. If the two keys match, you’re connected without the need for additional credentials. You can choose to protect the private key by adding a passphrase on top of it, for an additional layer of security.
Let’s get started.
While Ruby makes creating web applications a breeze, getting Ruby set up is somewhat time-consuming. Below we outline the steps needed to get Ruby installed on an Ubuntu 12.04 server pretty simply.
Let’s get started.
** Successfully Completed ** – We are planning to upgrade our control panel and network on East1. This upgrade will result in disruptions to both public and private network infrastructure: your servers will have their connections to the Internet and to their VLANs disrupted. In addition, the host servers will be rebooted, which will in turn reboot your servers.
The scheduled downtime is from March 10, 2013 at 4:00AM to 5:00AM EST , during which period your servers will be unavailable and rebooted. We don’t expect to need the entire hour, and will make every effort to ensure a quick upgrade.
This is our first planned downtime at East1 for 2013 and we hope it is the last. Once the cluster is back online, you’ll enjoy a much improved control panel!