What Kutoken will Offer

Posted on June 11, 2009 at 22:05

I've been asked a few times on twitter and elsewhere for some more details of what Kutoken will provide. We're still working on everything, so we don't have specifics on the plans available, but here's what will definitely be offered from day 1:

  • A Xen powered virtual dedicated server running Debian Lenny
  • Access to the Kutoken apt repository
  • Easy site deployment scripts
  • A proper SLA

In more detail:

The Virtual Machine

A virtual machine running Debian Lenny. You'll have complete control over this - root access, even the ability to compile your own kernel, although Xen support must be compiled in if you want it to work ;)

Data for this will be stored on a Dell Equalogic SAN device, but this will be entirely transparent to you. Using the SAN means the VM be fault tolerant, automatically restarting on another physical node should one fail, as well as providing excellent performance.

The VM will come with Apache, Django, mod_wsgi and python-mysqldb already installed, so all you need to do is deploy your app and you're up and running. In addition, we've written easy to use deployment scripts which will create basic Apache and mod_wsgi configs for you. You are of course free to tweak these as much as you want afterwards, or write your own from scratch if you prefer.

All VMs also have access to the Kutoken apt repository, which makes a number of Django apps a simple 'apt-get' away.

Kutoken

Kutoken is a project of Bashton Ltd. We have providing Linux-related consultancy for almost five years, with a particular emphasis on highly scalable, highly available solutions. Kutoken is our way of bringing the high-end solutions we provide for those with very deep pockets to the more cost-concious.

Because we expect the Kutoken service to be used by real companies with real consequences for downtime, we'll be offering a proper service level agreement. We want Kutoken to be a service you can feel confident in depending on.

Comments are turned on for this blog, so if you've got any more questions, please feel free to add them to this post.

Tags details

Comments

Johan

Posted on June 12, 2009 at 8:39

Sounds great - but can I ask why mysql and not postgres? Myself I much prefer postgres but I suppose django makes is easy to use either.

Sam

Posted on June 12, 2009 at 9:26

We're using MySQL rather than Postgres because of the mature replication. We've been using MySQL replication for years; Postgres replication hasn't made it into the stable release yet.

Post a new comment