IPv6 by default
We’ve now enabled IPv6 by default for all customers hosted on either onza or yali. The control panels for these machines have been running IPv6 for over a year, we’ve now enabled it for all customer websites too.
We’ve now enabled IPv6 by default for all customers hosted on either onza or yali. The control panels for these machines have been running IPv6 for over a year, we’ve now enabled it for all customer websites too.
Behind the scenes we’ve been expanding and improving our VDS platform. We’ve just added a second cluster (Telecity HEX) that you can now order VMs in and we’re about to add a third cluster (Cambridge) too. You’ll be able to specify which zone your virtual server runs in if you have a preference and each one is independently routed.
We’ve had a long association with the Cambridge Cycle Campaign and Cyclestreets. Cyclestreets are borrowing a 64GB VM in our HEX cluster to run some of their data import jobs and to test out how well it works. Shortly after that we’ll be launching bigger VM sizes, 16GB, 24GB, 32GB, 48GB, 64GB and 80GB with corresponding disk and bandwidth increases. Initially these will be available in the London zones only (SOV/HEX) but we expect to follow through with Cambridge in the near future.
So I had reason to transfer 350GB of data from a server hosted by Mythic Beasts to a USB drive in order to back up and ship the data to a bandwidth deprived customer. For reasons of my convenience I thought I’d do this from my home office where I have a 10Mbit ADSL connection provided by a small reputable and non bargain basement ISP and a 60Mbit connection provided with an entirely different technology. I split the source files roughly 2:1 between the connections and downloaded them with rsync tunnelled over ssh. Over the next 26 hours the download ran, 99.6GB over the DSL line (average speed 8Mbits),150GB over the cable (average speed 12Mbits).
I’ve taken the bandwidth graph from the server and included it above. The blue box is the DSL line data, the wavy line the cable. You’ll notice the DSL line runs flat out the whole time with it’s performance never wavering, the cable is clearly limited by congestion. This isn’t an issue on the server side – we’ve 100Mbits from the server up to to the router then 1Gbit out to the peering exchanges (LoNAP and Edge-IX) where we pick up the DSL and cable providers.
The main difference here is the incentive scheme. My DSL provider gives me a bandwidth cap and charges me for additional bandwidth over that limit. Consequently they have an incentive to make my line as fast as possible because that makes it easier for me to pay them more. It also means the only other users of the network who are using large quantities of traffic are paying their fair share which provides the money to upgrade the network. My cable connection is ‘unlimited’ which means performance is constrained by congestion caused by other users. The flat-lines are caused by the rate limiting confusing ssh and the connection essentially stopping until I had to intervene restart the transfer. I’ve included these because fast though 60Mbits may be, I’m not going to sit and babysit for the full 350GB download to complete.
This is why servers supplied by Mythic Beasts come with fast connections, bandwidth allowances and excess fees. We want to make your connection as fast as possible so you can easily spend more money with us.
Yesterday Mythic Beasts and selected friends went to the Cambridge beer festival. Whilst there we saw a poster put up by the Son Of Sid brewery for a beer called codebreaker with a mysterious set of non-sensical characters at the bottom. It took about a minute of staring knowingly before one of us said ‘well it’s not a substitution cipher’, followed by ‘I wish I had a laptop with me’ and before we knew it we had a crack team trying to break the cipher.
If you’d like to have a go yourself we suggest you get down to the beer festival, the breweries twitter feed says you have until Saturday to work it out. At the end there’s going to be a draw from all the successful entries to win a polypin of beer.
I don’t think we managed to save the world from a Hollywood style alien invasion but we had fun and drank beer at the same time.
EDIT: The official brewery twitter feed says,
Bob Mitchell @sonofsidbrewery One entry so far in the codebreaker competition @cambeerfest 12:27 PM - 22 May 12 via web · Details
that was team Mythic.
A customer wanted to use Django (this is a web application framework for the Python language), but found it wasn’t installed on their hosting server (which happened to be sphinx in this case). A couple of emails to support@mythic-beasts.com later, and they were up and running within 24 hours.
The moral of this story: if you’re trying to do something with a Mythic Beasts service, and seem to have hit a brick wall, do get in touch. If it’s at all sensible, we’ll try to make it possible, and if it’s not sensible, we’ll let you know!
Nominet is the domain name registry that ultimately controls .co.uk, .org.uk, and most other second-level domains under .uk. Till now, they have only allowed domain names to be registered for 2 years – no more, no less.
That changed today, 1st May 2012, and so we pleased to be able to offer Nominet domain registrations for up to 10 years. As well as receiving a discount for the longer registration period, you can rest assured that your domain is yours with no need to renew till 2022!
Or, going in the other direction, if you have a short-term project that deserves a .uk domain name, you could register for just 1 year.
We’ve also today added a bunch of new Top Level Domains that we can support, including .tel, .au, .nz, and extending our coverage of European countries: here are the full details of supported domains and prices. (Even more Top Level Domains may be available on request – email us if you don’t see what you’re after!)
Matt Smith has very handily also written a guide for installing Debian on our VDS service, which is particularly helpful for end users running Windows on their local machine.
One of our braver customers who wishes to remain anonymous has been trying out NetBSD on our KVM based virtual server platform. This is unsupported but he’s written us the following advice that any future customers might appreciate.
Firstly, the default network device is not going to work under NetBSD, so running netdev rtl8139 before installing is needed. Because of the default realtek driver in NetBSD, the install will be a bit choppy - recommended pulling packages from CD instead of network. After that recompiling the kernel is needed, with 2 modifications. I've based my config on GENERIC, so simply copying the GENERIC config file and commenting out the re* driver. This will make the kernel use the older rtk driver, which will work. Mind that /etc/ifconfig.re0 will need to be copied to /etc/ifconfig.rtk0 to make sure it comes up with network enabled after boot. Just find the line starting with re* and comment it out. Before recompiling, edit /usr/src/sys/netinet/if_arp.c and lookup the line matching "arp info overwritten". Simply delete the line (3 lines in total ending ";") as having this being logged is a nuisance as your router IP keeps changing between interfaces (so arp table is constantly updating).
NetBSD isn’t an officially supported distribution as we have minimal direct experience with it, but if you’re happy to support yourself we hope this helps you get set up.
We’ve offered privacy on domain name registrations for some time, I’ve just deployed an update which makes it possible to enable or disable it for every supported domain through our control panel.
Earlier this year we installed some new hardware for our Virtual Dedicated Server cluster. This has allowed us to not just double, but quadruple the amount of memory available on each of our VDS options. Our base level VDS now comes with 1GB of RAM and is priced at £15/month including VAT. In fact, if you pay for a year up front you can get it for the equivalent of just £12.50/month.
Naturally we’ll be offering these upgrades free of charge to our existing customers, but in order to do this we do need to move some servers onto different hardware. We’ll be in touch shortly with a migration plan, although if you’re particularly keen to get an upgrade please drop support an email.