From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Hosting a GuixSD server on commodity hosting platforms, a journey
Date: Wed, 30 Nov 2016 12:18:21 -0600 [thread overview]
Message-ID: <87twaozv9u.fsf@dustycloud.org> (raw)
In-Reply-To: <87bmwxt38s.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
Marius Bakke writes:
> I've had the questionable privilege of working on Openstack for some
> time, and indeed have a GuixSD system running on it. I can tell you that
> any errors you see are not necessarily representative of what's
> happening in the back-end, although it does sound like the Rackspace GUI
> just spits out a generic message, instead of a flat-out lie..
Yeah it was pretty generic, so I have no idea what happened. :)
> The image I used was created by installing a bare-bones GuixSD to an LVM
> device (e.g. with Qemu), then dumping this with `dd` before first boot
> to create a "RAW" image. RAW is supported (required, actually) by Glance
> if Ceph is used as the backing storage, but Rackspace only supports VHD.
Interesting!
> I haven't looked into the fstab of the generated VM image, but it may be
> hard-coded to '/dev/vda' whereas Xen creates '/dev/xvda' (IIRC). Though
> it should at least try to boot if that was the case.
Yeah, my configuration was set up for /dev/sda I think. I guess I could
do a system reconfigure switching it out to /dev/vda or whatever at
least minute... I dunno.
> My best advice is to try doing a normal install in a VM from the USB
> image (qcow2 probably works) and then convert it to the format your
> cloud platform expects, instead of booting the VM image directly. I used
> GPT with a "bios_grub" partition FWIW.
Out of curiosity, why do you think this would be an improvement?
> Make sure to use (title 'label) and appropriate FS labels, since the
> root device path may vary between cloud platforms.
Right, though labels might vary between platforms too, correct?
> On a vaguely related note, I'm slowly working on a "native" GuixSD
> hosting platform, where you will be able to submit (and share!)
> configuration files and get a VM and/or disk image back. It's still a
> long way off, but I could use some help building the web front-end once
> the back-end is ready. Feel free to contact me for more details :)
Now this I'm really interested in! I'll ping you off-list to discuss
this more. :)
next prev parent reply other threads:[~2016-11-30 18:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 19:59 Hosting a GuixSD server on commodity hosting platforms, a journey Christopher Allan Webber
2016-11-30 4:50 ` Christopher Allan Webber
2016-11-30 15:08 ` Marius Bakke
2016-11-30 18:18 ` Christopher Allan Webber [this message]
2016-11-30 16:41 ` Chris Marusich
2016-12-01 16:52 ` Christopher Allan Webber
[not found] ` <87r35t42qe.fsf@we.make.ritual.n0.is>
[not found] ` <87r35szth9.fsf@dustycloud.org>
2016-11-30 22:00 ` ng0
2016-12-02 4:06 ` Christopher Allan Webber
2016-12-02 6:22 ` Chris Marusich
2016-12-02 17:39 ` Christopher Allan Webber
2016-12-02 19:51 ` Christopher Baines
2016-12-02 23:20 ` Tobias Geerinckx-Rice
2016-12-03 19:13 ` Christopher Allan Webber
2016-12-03 18:24 ` Christopher Allan Webber
2016-12-02 20:53 ` Christopher Allan Webber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87twaozv9u.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=help-guix@gnu.org \
--cc=mbakke@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).