Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	Cake List <cake@lists.bufferbloat.net>,
	make-wifi-fast@lists.bufferbloat.net,
	 "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] bufferbloat.net cutting expenses and retiring servers
Date: Sat, 8 Apr 2017 21:09:00 -0700	[thread overview]
Message-ID: <CAA93jw54Bom1t2sioMObbGeUXMCW5e_9kG+E_aDx3VSkVxbUZA@mail.gmail.com> (raw)

Due to no funding for the past 9 months, and nothing in the foreseeable
future, and the essential conclusion of phase I of the make-wifi fast
project, I am going to be shutting down a few underused servers and
other infrastructure.

The lede build server (650/month) will be shut down at the end of the
month if not earlier.

flent-bbr, flent-tokoyo, flent-dallas, flent-atlanta, flent-newark,
flent-de will be shut down shortly. (I will try to upgrade kernels
on the machines remaining to also support BBR)

I will look for files on them that need to get moved first.

There are a pair of other servers in newark that I no longer have idea
what they do, also planned to go.

flent-fremont might get retired for a newer more capable box.

flent-london, lists/www.bufferbloat.net and www.cerowrt.org will remain
up, but might end up all merged into one.

I am not responsible for the upkeep of the two other flent servers in
the pool, but I've lost track of which ones are which, mapped to
netperf-west, east, and so on, I'll figure out which of those are which
at some point.

netperf-eu is toke's server... can't remember what rich's server is
mapped to. But we'll end up with netperf-west being a machine
in fremont, and no coverage of the central US.

If anyone is actually using the servers I plan to retire for anything,
(more than a few here have accounts) please let me know soon.

-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org

                 reply	other threads:[~2017-04-09  4:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAA93jw54Bom1t2sioMObbGeUXMCW5e_9kG+E_aDx3VSkVxbUZA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=make-wifi-fast@lists.bufferbloat.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox