From: Leon Romanovsky <leon@kernel.org>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Honggang LI <honli@redhat.com>,
Gal Pressman <galpress@amazon.com>
Subject: Re: RDMA device renames and node description
Date: Tue, 18 Feb 2020 16:04:44 +0200 [thread overview]
Message-ID: <20200218140444.GB8816@unreal> (raw)
In-Reply-To: <5ae69feb-5543-b203-2f1b-df5fe3bdab2b@intel.com>
On Fri, Feb 14, 2020 at 01:13:53PM -0500, Dennis Dalessandro wrote:
> Was there any discussion on the upgrade scenario for existing deployments as
> far as device-rename changing node descriptions?
>
> If someone is running an older version of rdma-core they are going to have a
> certain set of node descriptions for each node. This could be in logs, or
> configuration databases, who knows what. Now if they upgrade to a new
> version of rdma-core their node descriptions all automatically change out
> from under them by default.
>
> Of course the admin could disable the rename prior to upgrade and as Leon
> pointed out previously the upgrade won't remove the disablement file. The
> problem is they would have to know to do that ahead of time.
Dennis,
It was discussed and the conclusion was that most if not all users are
using one of two upgrade and strategy.
First option is to rely on distro and every distro behaves differently
in such cases, some of them won't change anything till their last user
dies :) and others more dynamic with more up-to-date packages already
adopted our default.
Second option is to use numerous OFED stacks, which are expected to
provide full upgrade to all components which will work smoothly.
Users who upgrade their system from live upstream repo are expected to
be proficient enough to be deal with change of defaults.
Thanks
>
> -Denny
next prev parent reply other threads:[~2020-02-18 14:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 18:13 RDMA device renames and node description Dennis Dalessandro
2020-02-18 14:04 ` Leon Romanovsky [this message]
2020-02-18 17:11 ` Dennis Dalessandro
2020-02-18 20:08 ` Jason Gunthorpe
2020-02-19 7:11 ` Leon Romanovsky
2020-02-19 14:14 ` Dennis Dalessandro
2020-02-19 14:35 ` Gal Pressman
2020-02-19 15:10 ` Leon Romanovsky
2020-02-19 16:54 ` Jason Gunthorpe
2020-02-19 14:48 ` Leon Romanovsky
2020-02-19 15:34 ` Dennis Dalessandro
2020-02-19 16:58 ` Jason Gunthorpe
2020-02-19 19:35 ` Dennis Dalessandro
2020-02-19 23:18 ` Ira Weiny
2020-02-20 2:26 ` Dennis Dalessandro
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=20200218140444.GB8816@unreal \
--to=leon@kernel.org \
--cc=dennis.dalessandro@intel.com \
--cc=galpress@amazon.com \
--cc=honli@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.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).