The public git repository seems to be at git://
git.whamcloud.com/fs/lustre-release.git
This was not working yesterday, but it appears to be working now.
Jim
On Fri, Jun 22, 2018 at 10:47 AM, Peter Jones wrote:
> Yes - all the development infrastructure is moving. This is a work in
> progress
Mark,
Hmm.
I’m adding the list back on here, because that *seems* like it’s wrong. Don’t
have time to check right now, but I’m curious if others can weigh in.
* Patrick
From: Mark Roper
Date: Friday, June 22, 2018 at 2:29 PM
To: Patrick Farrell
Subject: Re: [lustre-discuss] Lustre 2.11
Hi Lustre Admins,
I am hoping someone can help me understand what I'm doing wrong with SSK
setup. I have set up a lustre 2.11 server and worked through the steps to
use shared secret keys (SSKs) to encrypt data in transit between client
nodes and the MDT and OSS. I followed the manual instruction
Yes - all the development infrastructure is moving. This is a work in progress
and there are definitely stale links to tidy up too.
On 2018-06-22, 11:28 AM, "lustre-discuss on behalf of Mark Dixon"
wrote:
Does that mean the public git repository (and anything else?) has also
moved?
Hello,
I am sending Lustre-related patches to ext4 e2fsprogs now and have a question.
There are two patches:
- "e2scan: a tool for fast namespace/inode scanning”
- "tests: add basic test case for e2scan”
They are ready to be send to the list, but probably currently e2scan utility is
not actual
Does that mean the public git repository (and anything else?) has also
moved?
$ git clone git://git.hpdd.intel.com/fs/lustre-release.git
Cloning into 'lustre-release'...
fatal: remote error: access denied or repository not exported:
/fs/lustre-release.git
Tried replacing hpdd.intel.com w
