From: Steve French <smfrench@gmail.com>
To: "Aurélien Aptel" <aaptel@suse.com>
Cc: David Howells <dhowells@redhat.com>,
trond.myklebust@hammerspace.com,
Anna Schumaker <anna.schumaker@netapp.com>,
Steve French <sfrench@samba.org>,
linux-nfs@vger.kernel.org, CIFS <linux-cifs@vger.kernel.org>,
linux-afs@lists.infradead.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Making the in-kernel DNS resolver handle server lists
Date: Thu, 13 Sep 2018 11:30:26 -0700 [thread overview]
Message-ID: <CAH2r5mu72XVSBp48BYWcg_tmioC8feHmwzNM8UnzaZ=g3g9UZw@mail.gmail.com> (raw)
In-Reply-To: <87lg854ws2.fsf@suse.com>
On Thu, Sep 13, 2018 at 1:39 AM Aurélien Aptel <aaptel@suse.com> wrote:
>
> David Howells <dhowells@redhat.com> writes:
> > Is this something that NFS or CIFS (or anything else for that matter) could
> > find useful?
>
> That sounds useful indeed. I'm currently thinking about a failover
> mechanism for DFS (symbolic links across servers in cifs). The protocol
> supports multiple possible targets for the link in case one is down. The
> targets are usually using hostnames so with your change we could have a
> second layer of failover at the DNS level.
>
> > I also have this loading information from a configuration file as a
> > backup/override of the DNS. Could that also be useful to NFS/CIFS?
>
> Cheers,
> --
> Aurélien Aptel / SUSE Labs Samba Team
Yes - the idea that Aurelien notes above is VERY important for some
improving some recovery scenarios, and if this helps us get there
faster it will greatly improve reliability of some common user scenarios.
--
Thanks,
Steve
next prev parent reply other threads:[~2018-09-13 23:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 11:11 Making the in-kernel DNS resolver handle server lists David Howells
2018-09-12 20:53 ` Steve French
2018-09-12 21:18 ` David Howells
2018-09-12 22:27 ` Steve French
2018-09-13 8:38 ` Aurélien Aptel
2018-09-13 18:30 ` Steve French [this message]
2018-09-13 9:14 ` David Howells
2018-09-13 20:01 ` David Howells
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='CAH2r5mu72XVSBp48BYWcg_tmioC8feHmwzNM8UnzaZ=g3g9UZw@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=aaptel@suse.com \
--cc=anna.schumaker@netapp.com \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sfrench@samba.org \
--cc=trond.myklebust@hammerspace.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 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).