From: Jakub Kicinski <kuba@kernel.org>
To: David Ahern <dsahern@kernel.org>
Cc: netdev@vger.kernel.org
Subject: Re: [TEST] The no-kvm CI instances going away
Date: Wed, 7 Feb 2024 12:07:13 -0800 [thread overview]
Message-ID: <20240207120713.68686bca@kernel.org> (raw)
In-Reply-To: <1dddd3ba-aabe-4ad8-aefa-fd5e337c88d0@kernel.org>
On Wed, 7 Feb 2024 12:45:00 -0700 David Ahern wrote:
> I have no such ability :-) I cover the costs myself when I use VMs on
> DigitalOcean and Vultr for Linux development and testing.
>
> Kernel builds and selftests just need raw compute power, none of the
> fancy enterprise features that AWS provides (and bills accordingly).
>
> The first question about who is covering the cost is to avoid
> assumptions and acknowledge the service (and costs) provided to the
> community. Having the selftests tied to patchsets is really helpful to
> proactively identify potential regressions.
Thanks! Meta is pretty great at covering various community costs.
I try to keep the asks reasonable, but I haven't been told "no",
yet. The reason why it'd be great to have more supporters is that
(at a cost of slightly more paperwork) we could externalize the
whole shebang, and give out SSH keys more freely :(
I also heard that some clouds or LF have free cloud credits for open
source CI. But IDK how I could connect those to my corporate account..
Anyway. In my ideal world we'd write a check for LF and get a bunch
of VMs in DO or alike. In the present reality we have AWS which only
I can access 🥴️
Good thing is the system is distributed. Hopefully over time more
people will join in by reporting the results (like Mojatatu does
with TCD).
prev parent reply other threads:[~2024-02-07 20:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 1:41 [TEST] The no-kvm CI instances going away Jakub Kicinski
2024-02-06 11:16 ` Matthieu Baerts
2024-02-07 1:44 ` Jakub Kicinski
2024-02-07 9:44 ` Matthieu Baerts
2024-02-07 14:25 ` Jakub Kicinski
2024-02-07 14:37 ` Matthieu Baerts
2024-02-07 15:29 ` Jakub Kicinski
2024-02-07 16:06 ` Matthieu Baerts
2024-02-07 17:45 ` David Ahern
2024-02-07 18:55 ` Jakub Kicinski
2024-02-07 19:45 ` David Ahern
2024-02-07 20:07 ` Jakub Kicinski [this message]
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=20240207120713.68686bca@kernel.org \
--to=kuba@kernel.org \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.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 NNTP newsgroup(s).