linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <steved@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Cc: NFSv4 IETF <nfsv4@ietf.org>
Subject: Virtual Bakeathon: Reminder
Date: Thu, 30 Sep 2021 12:37:06 -0400	[thread overview]
Message-ID: <7e24d80d-56b2-68af-5351-ad42dc4d0a18@redhat.com> (raw)

Hello,

Just a quick reminder the VBAT coming up next week
The details are here [1].

We are again going to be using an IPv6
based VPN as the testing network. Details on
how to set it up are at [2]. Any question
reach out to Ben Coddington <bcodding@redhat.com>

Here at Red Hat we have been using vm
in the Digital Ocean cloud [3]...
I have found them to be really easy to
work with and relatively inexpensive.

We will again use discord [4] to communicate.
Look for the VBaT channel. The contact for that is
Alice Mitchell <ajmitchell@redhat.com>

Finally I would like to propose that every day at
2:00pm (EST) we get together on the discord voice
channel 'General Chat' and talk about the topics
of the day:

* TLS (user vs kernel)
* FS-cache (Trond's favorite subject)
* QUIC (Chuck's favorite subject ;-) )
* Allowing hung mount to reboot
* re-export
* Session-Truncking
* ???

Basically anything we wan to talk about relative
to what is going on in the community...
or not... :-)

Ideally, as Rick suggested, reaching out to people
like Google and MS.. people who  might have a better
insight of these networking technologies... would
be good... Just let them where we will be.

If I have forgotten anything... I'm sure you will
let me know! :-) See you Monday!

steved

[1] http://www.nfsv4bat.org/Events/2021/Oct/BAT/index.html
[2] https://vpn.nfsv4.dev/
[3] https://www.digitalocean.com/
[4] https://discord.com


                 reply	other threads:[~2021-09-30 16:37 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

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

  git send-email \
    --in-reply-to=7e24d80d-56b2-68af-5351-ad42dc4d0a18@redhat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@ietf.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).