unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Christopher Allan Webber <cwebber@dustycloud.org>,
	help-guix <help-guix@gnu.org>
Subject: Re: Hosting a GuixSD server on commodity hosting platforms, a journey
Date: Wed, 30 Nov 2016 16:08:03 +0100	[thread overview]
Message-ID: <87bmwxt38s.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <871sxt1sho.fsf@dustycloud.org>

[-- Attachment #1: Type: text/plain, Size: 3633 bytes --]

Christopher Allan Webber <cwebber@dustycloud.org> writes:

> Christopher Allan Webber writes:
>
>> What am I doing wrong?  I'm not totally sure... I feel like I'm
>> navigating a jungle out here in the OpenStack / Rackspace docs.  Here's
>> one thing I found:
>>
>>   https://community.rackspace.com/products/f/25/t/7186
>>
>> So I probably need to execute this "import" command.  I guess that's
>> what's next...
>
> Well, I did a bit more exploration tonight with *some* progress, but
> still not success.  I followed the above link and got a task to generate
> an image based off my file.  Looks like the task took!  And it showed up
> in "image-list" with the glance command line client.  Sounds like
> progress!
>
> And hey, if I try to create the server now via the web UI... if I look
> to create an image based off the images list from
> "Saved -> Deleted Servers (!!!)" menu, I indeed see my image listed.
> Cool!  So I select that and click "create server".
>
> Ok... I wait a bit.  It says it's initializing it!
>
> Uhoh, suddenly the status turns to ERROR.  What's ERROR?  I don't know.
> It says ERROR, and it's red.  Hovering over it suggests I ask support.
> Hm.
>
> I wonder if I used the Nova command line client if I'd get more
> information, or if there's a way to query the API to get more info.
>
> Still, that's *some* progress... I kicked off generating an image
> generated via GuixSD, even if it didn't work at all... :)
>
> Relatedly!  User dvc in #guix on freenode suggests looking at
> https://www.vultr.com/ which looks quite affordable and hey!  It has a
> "custom ISO" option.  If we can convert our USB boot stick thingy
> (presumably via xorriso) we could try generating a base server image
> from there.  I'd prefer to have a workflow where I go from handing off
> something made with "guix system vm-image" to some API, but maybe in the
> meanwhile Vultr would be a lower barrier to entry.
>
> In the meanwhile, anyone familiar enough with Nova or Rackspace want to
> give me hints on how to find out more about what ERROR means, more
> specifically? ;)

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..

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.

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.

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.

Make sure to use (title 'label) and appropriate FS labels, since the
root device path may vary between cloud platforms.

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 :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2016-11-30 15:08 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 [this message]
2016-11-30 18:18     ` Christopher Allan Webber
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=87bmwxt38s.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --cc=cwebber@dustycloud.org \
    --cc=help-guix@gnu.org \
    /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).