From: Dennis Dalessandro <dennis.dalessandro@intel.com>
To: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Honggang LI <honli@redhat.com>,
Gal Pressman <galpress@amazon.com>
Subject: RDMA device renames and node description
Date: Fri, 14 Feb 2020 13:13:53 -0500 [thread overview]
Message-ID: <5ae69feb-5543-b203-2f1b-df5fe3bdab2b@intel.com> (raw)
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.
-Denny
next reply other threads:[~2020-02-14 18:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 18:13 Dennis Dalessandro [this message]
2020-02-18 14:04 ` RDMA device renames and node description Leon Romanovsky
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=5ae69feb-5543-b203-2f1b-df5fe3bdab2b@intel.com \
--to=dennis.dalessandro@intel.com \
--cc=galpress@amazon.com \
--cc=honli@redhat.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--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).