Bug 2001024
| Summary: | [RFE] RHEL9 support fence agent based on NVME reservation | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | vincent chen <vincent.chen1> |
| Component: | fence-agents | Assignee: | Oyvind Albrigtsen <oalbrigt> |
| Status: | CLOSED MIGRATED | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 9.0 | CC: | cluster-maint, jmeneghi, kazen, linux-bugs, vincent.chen1 |
| Target Milestone: | rc | Keywords: | FutureFeature, MigratedToJIRA, Reopened, Triaged |
| Target Release: | 9.3 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | NVMe_P2 | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-22 20:47:35 UTC | Type: | Story |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2116239, 2188515 | ||
|
Description
vincent chen
2021-09-03 14:58:40 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. Karl, this is a public requirement. not dell specific. thinking about RHCS support scsi_fence mechanism which depending on storage vender supporting scsi reservation standards. now nvme-F is more and more popular and dell storage already support nvme reservation standard too. so we ask if rhel has a plan support to support nvme_fence agent. The nvme replacement for sg3_utils with is the nvme-cli utility. This utility is fully supported by RHEL. [root@rhel-storage-105 ~]# rpm -qi nvme-cli Name : nvme-cli Version : 2.4 Release : 1.el9 Architecture: x86_64 Install Date: Tue 18 Apr 2023 05:40:34 PM EDT Group : Unspecified Size : 4982802 License : GPLv2+ Signature : RSA/SHA256, Wed 12 Apr 2023 03:55:03 AM EDT, Key ID 199e2f91fd431d51 Source RPM : nvme-cli-2.4-1.el9.src.rpm Build Date : Thu 06 Apr 2023 06:25:43 AM EDT Build Host : x86-64-06.build.eng.rdu2.redhat.com Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> Vendor : Red Hat, Inc. URL : https://github.com/linux-nvme/nvme-cli Summary : NVMe management command line interface Description : nvme-cli provides NVM-Express user space tooling for Linux. So, instead of using the `sg_persist` command you would use the `nvme` command to manage reservations on the nvme device. resv-acquire Submit a Reservation Acquire, return results resv-register Submit a Reservation Register, return results resv-release Submit a Reservation Release, return results resv-report Submit a Reservation Report, return results This means: sg_persist --out --register --param-rk=123456 /dev/sdb becomes: nvme resv-register /dev/nvme1n1 --rrega=0 --nrkey=123456 --iekey Example: [root@rhel-storage-105 ~]# nvme resv-register /dev/nvme1n1 --rrega=0 --nrkey=123456 --iekey NVME Reservation success [root@rhel-storage-105 ~]# nvme resv-report /dev/nvme1n1 NVME Reservation status: gen : 1 rtype : 0 regctl : 1 ptpls : 1 regctl[0] : cntlid : 1 rcsts : 0 hostid : 0 rkey : 1e240 yes, the nvme-cli utility is supported by RHEL. RHCS supply scsi_fence agent for cluster fencing. it only serve for scsi3 reservation. there don't have a agent used for nvme reservation. there need a similar agent for nvme reservation Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |