unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <gboskovits@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: "Guix Devel" <guix-devel@gnu.org>,
	"Ludovic Courtès" <ludo@gnu.org>,
	"Christopher Baines" <mail@cbaines.net>,
	"GNU Guix maintainers" <guix-maintainers@gnu.org>,
	guix-europe@gnu.org
Subject: Re: Discontinuing data.guix.gnu.org?
Date: Tue, 9 Jan 2024 20:19:55 +0100	[thread overview]
Message-ID: <CAAqdTgMi3a9koXzx9GKstJvQiLs=TzdRPkKPFJFWWnoC72t7rA@mail.gmail.com> (raw)
In-Reply-To: <A167C2D7-BC83-4D2B-AE97-A687A4A97C8B@lepiller.eu>

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

Hello,

Julien Lepiller <julien@lepiller.eu> ezt írta (időpont: 2024. jan. 9., K
19:33):

> In terms of finance, our last blocker is that I still don't have access to
> the account, but Andreas does, so we should be able to take responsibility
> for the cost relatively easily.
>
> Ideally, we would take ownership of the machine(s), so we don't
> overcomplicate our finances by having to reimburse someone regularly.
>
> Le 9 janvier 2024 19:12:44 GMT+01:00, "Ludovic Courtès" <ludo@gnu.org> a
> écrit :
> >Hello Christopher,
> >
> >Christopher Baines <mail@cbaines.net> skribis:
> >
> >> Ludovic Courtès <ludo@gnu.org> writes:
> >
> >[...]
> >
> >>> Christopher Baines <mail@cbaines.net> skribis:
> >>>
> >>>> As previously set out, I'm planning to stop hosting the data service
> >>>> instances this year. While I would like to stop hosting the server for
> >>>> data.guix.gnu.org,
> >>>
> >>> I forgot the outcome of previous discussions, but it seems to me that
> >>> the service itself and all the data it accumulated over the years are
> >>> super valuable.  I would be sad to see it go!
> >>
> >> There was a discussion back in April, but no action came directly from
> >> it.
> >>
> >> Just having data.qa.guix.gnu.org was discussed, and at least
> >> concentrating on getting to a sustainable hosting situation there seemed
> >> like a sensible priority. The longer history provided by
> >> data.guix.gnu.org does have value though in my view.
> >>
> >>> Is there something we can do to not lose it all?  It could be
> >>> distributing responsibility, reducing the scope, ensuring hosting is
> >>> managed collectively by the project, etc.  WDYT?
> >>
> >> Since that discussion, I have disabled the database dumps and backups,
> >> which has reduced (to 62€ per month) the hosting costs (although
> >> obviously not having backups isn't ideal). It's possible to further
> >> reduce the hosting costs as well by switching away from a VM to a
> >> physical machine at Hetzner.
>

If we decide to go down this path what would be a reasonable hardware
specification for the physical machines (I guess we are talking about at
least two, because of backup). Also in this case it might make sense to see
what else we could run on them. I don't want to hijack the thread, feel
free to start a new one for this line of conversation.

Regards, g_bor

> >>
> >> But yeah, given that having at least one data service instance is a key
> >> part of keeping the bordeaux build farm running, managing the hosting
> >> through the project seems to be the way to go. I'm just not sure how we
> >> can get there, or what I can do to move things in that direction.
> >
> >Like you, I would have hoped for more reactions.  Unfortunately, I’m not
> >offering to help here because I have more than enough on my plate and
> >even a 1+ month backlog on guix-devel…
> >
> >Maintainers, what’s your take on this?
> >
> >Guix Foundation, is there any blocker to taking responsibility for
> >covering hosting expenses, possibly rediscussing the scope and cost?
> >
> >Let 2024 be a thriving Guix year! :-)
> >
> >Ludo’.
> >
>
>

[-- Attachment #2: Type: text/html, Size: 4732 bytes --]

  reply	other threads:[~2024-01-09 19:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 13:32 November/December update on qa.guix.gnu.org and related things Christopher Baines
2023-12-09 10:39 ` Discontinuing data.guix.gnu.org? Ludovic Courtès
2023-12-09 11:14   ` Christopher Baines
2024-01-09 18:12     ` Ludovic Courtès
2024-01-09 18:33       ` Julien Lepiller
2024-01-09 19:19         ` Gábor Boskovits [this message]
2024-01-10  0:38       ` Maxim Cournoyer
2023-12-09 10:54 ` Shutting down qa.guix? Ludovic Courtès
2023-12-09 12:16   ` Christopher Baines
2023-12-09 13:30     ` Tobias Geerinckx-Rice
2023-12-10 10:54       ` Christopher Baines
2023-12-10 16:05         ` Maxim Cournoyer
2023-12-11 13:30           ` Christopher Baines
2023-12-10 18:50   ` Simon Tournier
2023-12-13 16:43   ` RFC (was Re: Shutting down qa.guix?) Simon Tournier
2024-01-18 12:39   ` [Guix-europe-sac] Shutting down qa.guix? Andreas Enge
2024-01-20 12:57     ` Christopher Baines

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='CAAqdTgMi3a9koXzx9GKstJvQiLs=TzdRPkKPFJFWWnoC72t7rA@mail.gmail.com' \
    --to=gboskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=guix-europe@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=ludo@gnu.org \
    --cc=mail@cbaines.net \
    /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).