Dave Pigott dave.pigott@linaro.org writes:
On 1 Oct 2012, at 09:48, Michael Hudson-Doyle wrote:
Dave Pigott dave.pigott@linaro.org writes:
On 1 Oct 2012, at 03:06, Michael Hudson-Doyle wrote:
Michael Hudson-Doyle michael.hudson@canonical.com writes:
Hi all,
Just a quick note to say that I'm restoring the staging database from the latest production snapshot. Staging will be down for however long this takes (maybe an hour).
Now done. We're a little tight for disk space on staging -- I had to delete the logs and bundles to get the restore to complete. Can that be upped without trashing the instance?
Rats. Looks like you can't do this on a live instance. Let me know when,
Well, if you're working, I'm probably not :-) So whenever is fine as far as I'm concerned.
OK. Shut down the old ones and created a new flavor, m1.lava, which has 8GB RAM, 50GB HD, 4CPUs and 80GB ephemeral storage. Two new instances, dogfood and staging, still at the same ip addresses.
Um. That wasn't what I was expecting! I thought you were going to shut the instance down, resize the root volume and bring the same instance up again. Is that not possible?
Luckily lava-deployment-tool makes the set up pretty easy :-)
Cheers, mwh
If someone walks me through it or point me at a wiki it would be quite good to know how to deploy a lava server from scratch.
Dave
and I'll restart it with more space. Would 100GB be enough?
Given 10 Gb is tight but workable, 100 Gb almost seems excessive :) But if we have the capacity, sure, sounds good.
Cheers, mwh