All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"Hajnoczi, Stefan" <stefanha@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: OSUOSL in trouble
Date: Thu, 1 May 2025 16:51:02 +0100	[thread overview]
Message-ID: <aBOYZsfT0retojQf@redhat.com> (raw)
In-Reply-To: <CAJSP0QVpxQDfuBOQiMyP41ufaJ=56Xh2sRhWSON=FvVuxDabaw@mail.gmail.com>

On Thu, May 01, 2025 at 11:43:28AM -0400, Stefan Hajnoczi wrote:
> On Thu, May 1, 2025, 01:11 Paolo Bonzini <pbonzini@redhat.com> wrote:
> 
> > From LWN
> >
> > > Lance Albertson writes that the Oregon State University Open Source Lab,
> > the home of many prominent free-software projects over the years, has run
> > into financial trouble:
> > >
> > > I am writing to inform you about a critical and time-sensitive situation
> > facing the Open Source Lab. Over the past several years, we have been
> > operating at a deficit due to a decline in corporate donations. While OSU's
> > College of Engineering (CoE) has generously filled this gap, recent changes
> > in university funding have led to a significant reduction in CoE's budget.
> > As a result, our current funding model is no longer sustainable and CoE
> > needs to find ways to cut programs.
> > > Earlier this week, I was informed that unless we secure $250,000 in
> > committed funds, the OSL will be forced to shut down later this year.
> >
> > I propose migrating the two VMs we have to Digital Ocean and scrapping the
> > DO Kubernetes cluster. However that means we need to move CI to Amazon in
> > the next 1-2 months, before the Microsoft credits expire.
> >
> 
> I agree. I will also apply for the next round of Amazon funding.
> 
> Paolo, please let me know how I can help with migrating VMs or setting up a
> CI Kubernetes cluster on Amazon.

Please ensure the any new CI machines for gitlab have persistent cache
enabled. Our functional test jobs are still downloading images on every
run due to lack of configured cache, which makes them unreliable when
sites have transient outages, as well as making jobs slower.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2025-05-01 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-01  5:10 OSUOSL in trouble Paolo Bonzini
2025-05-01 15:43 ` Stefan Hajnoczi
2025-05-01 15:51   ` Daniel P. Berrangé [this message]
2025-05-01 16:20     ` Paolo Bonzini
2025-05-01 16:31       ` Daniel P. Berrangé
2025-05-01 17:39         ` Stefan Hajnoczi

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=aBOYZsfT0retojQf@redhat.com \
    --to=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    /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 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.