all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: Advice about GuixSD on Serveraptor?
Date: Wed, 22 Mar 2017 21:01:06 +0000	[thread overview]
Message-ID: <20170322210106.f6z7vwavsna3qfg4@abyayala> (raw)
In-Reply-To: <20170322192023.ij2mzykimne7lfii@abyayala>

ng0 transcribed 1.3K bytes:
> Leo Famulari transcribed 2.0K bytes:
> > On Tue, Mar 21, 2017 at 09:06:09PM +0000, ng0 wrote:
> > > IN-Berlin wants a raw image (they have read our documentation).
> > > The way their system works is that you sent
> > > them your ssh pubkey, they initialize a basic Debian system depending on
> > > the size you chose, and you can login once you get the hostname etc.
> > > They have an out-of-band consoleserver where the ssh key is placed
> > > aswell for the machine.
> > > I don't work with this non-profit organization, but having a way to
> > > define ssh pubkeys in the system config would be super useful for this.
> > > Right now I'm about to create my own system and just sent it to them as
> > > soon as I feel up to it.
> > > If they could simply create the system in their infrastructure, that
> > > would be an incredible speedup and reproducible.
> > > I don't know much about the out of band consoleserver, I have to ask
> > > if that's somehow relevant or if it simply needs some initrd settings to
> > > expose it to the server.
> > 
> > Interesting! I'll probably take a look at this when I got some free
> > time.
> 
> I'll write an email to IN-Berlin asking about the consoleserver this
> week.
> If it's nothing special, we could provide this bare image, and people
> could download it as the GuixSD with ssh + whatever is needed for it to
> work out in server context as a start.
> 
I just realized the last sentence is not good.
Correction:
If IN-Berlin uses (or needs) nothing special for the consoleserver to
make use of the virtual servers within IN-Berlin infrastructure, I think
it would be best if we (as Guix) could provide an extended bare image
for servers which would include ssh-daemon on default port with password
login enabled, where the password is not empty. That's a workaround I
can imagine to be generic enough for all use cases.
For the one of IN-Berlin and maybe similar hosters who use ssh pubkeys,
it would be great to document for them how to recreate this image in
easy steps and insert the clients ssh pubkey for the root account (or an
named user) on the system.

What do you think about this?

  reply	other threads:[~2017-03-22 20:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09 18:36 GuixSD on commodity hosting platforms, hoster: IN-Berlin ng0
2017-02-09 20:38 ` Jan Nieuwenhuizen
2017-02-10 15:35   ` Ludovic Courtès
2017-02-10 22:48   ` ng0
2017-02-10 22:59     ` ng0
2017-02-11 10:37     ` Jan Nieuwenhuizen
2017-02-11 13:35       ` ng0
2017-02-13 21:47 ` Leo Famulari
2017-02-14  9:24   ` Ludovic Courtès
2017-02-14 10:10     ` ng0
2017-02-14 16:42     ` Leo Famulari
2017-02-16 15:34   ` Christopher Allan Webber
2017-03-13  0:32   ` Advice about GuixSD on Serveraptor? Leo Famulari
2017-03-21 18:06     ` Leo Famulari
2017-03-21 20:22       ` Christopher Allan Webber
2017-03-21 20:46         ` Leo Famulari
2017-03-21 20:53           ` Leo Famulari
2017-03-22  7:36             ` Thomas Danckaert
2017-03-22 17:17               ` Leo Famulari
2017-03-22 12:04             ` Ricardo Wurmus
2017-03-22 17:20               ` Leo Famulari
2017-03-22 17:23                 ` Leo Famulari
2017-03-24  9:36                   ` Ludovic Courtès
2017-03-24 15:26                     ` Leo Famulari
2017-03-26 10:20                       ` Ludovic Courtès
2017-03-21 21:06           ` ng0
2017-03-22 17:15             ` Leo Famulari
2017-03-22 19:20               ` ng0
2017-03-22 21:01                 ` ng0 [this message]
2017-03-24  4:35                   ` Chris Marusich
2017-03-24 16:34                     ` ng0
2017-03-25  9:01                       ` Chris Marusich
2017-03-26 10:26                         ` Ludovic Courtès
2017-03-26 11:54                         ` ng0

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170322210106.f6z7vwavsna3qfg4@abyayala \
    --to=contact.ng0@cryptolab.net \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.