From: Andreas Dilger <adilger@whamcloud.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] client-server wire protocol
Date: Wed, 2 Oct 2019 17:45:28 +0000 [thread overview]
Message-ID: <4E10628E-75DE-4BAA-84EF-47E871BABAC1@whamcloud.com> (raw)
In-Reply-To: <CAKSyJXdF6m5D0w5oFpyEFsTK_0PzJn2-cNsV3QZbH9UrYOtVTQ@mail.gmail.com>
On Sep 28, 2019, at 14:35, Bradley C. Kuszmaul <kuszmaul at gmail.com<mailto:kuszmaul@gmail.com>> wrote:
Is there a well-defined client-server wire protocol so that one could imagine building a different client or a different server that would interact with lustre?
I took a quick look through the lustre sources and documentation, but didn't find it.
There is a partially-completed wire protocol document in Git: https://git.whamcloud.com/?p=doc/protocol.git
However, I seriously doubt that it would be sufficient to implement a different client/server than the existing one,
since it is unfortunately both incomplete and already somewhat out of date.
Since Lustre is open-source software, there is little motivation to spend the huge amount of time & effort to
reimplement the client or server. Also, the Lustre protocol changes over time in order to add new functionality,
so a full reimplementation would become obsolete over time without continuous effort equal to all of the other
Lustre developers combined.
It would be better to add/fix/port existing code as needed rather than implementing everything from scratch.
If I might ask, what is your interest in this area? We're always looking to grow the number of developers and
contributors in the Lustre community.
Cheers, Andreas
--
Andreas Dilger
Principal Lustre Architect
Whamcloud
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20191002/2ccdcfbc/attachment.html>
prev parent reply other threads:[~2019-10-02 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-28 20:35 [lustre-devel] client-server wire protocol Bradley C. Kuszmaul
2019-10-01 16:01 ` Doug Oucharek
2019-10-02 17:45 ` Andreas Dilger [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=4E10628E-75DE-4BAA-84EF-47E871BABAC1@whamcloud.com \
--to=adilger@whamcloud.com \
--cc=lustre-devel@lists.lustre.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 read-only IMAP folder(s) and NNTP newsgroup(s).