From: Ricardo Wurmus <rekado@elephly.net>
To: 74389@debbugs.gnu.org
Subject: [bug#74389] [PATCH] services: add cloud-init service
Date: Thu, 21 Nov 2024 19:25:47 +0100 [thread overview]
Message-ID: <87serkzbo4.fsf@elephly.net> (raw)
In-Reply-To: <c907e459d6898df885e3aac67c8446a1c15d62b2.1731824739.git.alex@infiniteadaptability.org>
Hi Alexander,
thank you for the patch!
I'm interested in a cloud-init service because I think we need a way to
have Guix System images be configured dynamically when using them in AWS
or in Openstack environments. The dynamic configuration I'm most
interested in is user credentials and networking.
Last I looked into this, the Python library for cloud init had explicit
support for various distributions to modify system configuration files
and run tools (e.g. to configure and bring up networking, or to set the
hostname). It did not generate a central configuration file that could
be processed. It just triggered explicit per-distro actions.
We couldn't actually use any of that stuff for Guix System. What I
investigated a few months back was to see if there was a way to generate
some sort of configuration file that our services could then consult.
Sadly there was no such thing as a central configuration file containing
all necessary bits of information. From what I can tell cloud-utils
does not have what it takes to configure networking or user accounts.
It's probably useful for other bits, though I haven't ever used those.
Could you please expand on what your service does---and what it cannot
or does not aim to do---and how it would be used?
Thanks!
--
Ricardo
next prev parent reply other threads:[~2024-11-21 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 6:26 [bug#74389] [PATCH] services: add cloud-init service Alexander Joss
2024-11-21 18:25 ` Ricardo Wurmus [this message]
2024-11-22 19:20 ` Alex
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=87serkzbo4.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=74389@debbugs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).