| 2021-10-25 06:32:09 |
Reshmi Aravind |
bug |
|
|
added bug |
| 2021-10-25 06:32:23 |
Reshmi Aravind |
information type |
Public |
Private |
|
| 2021-10-25 06:35:00 |
Reshmi Aravind |
bug |
|
|
added subscriber Sujith Pandel |
| 2021-10-25 06:51:26 |
Reshmi Aravind |
bug |
|
|
added subscriber Charles Rose |
| 2021-10-25 14:06:10 |
Sujith Pandel |
bug |
|
|
added subscriber Michael Reed |
| 2021-10-26 17:14:51 |
Michael Reed |
bug |
|
|
added subscriber Jeff Lane |
| 2021-10-26 17:20:42 |
Michael Reed |
nominated for series |
|
Ubuntu Jammy |
|
| 2021-10-26 17:20:42 |
Michael Reed |
bug task added |
|
linux (Ubuntu Jammy) |
|
| 2022-03-09 08:54:22 |
Sujith Pandel |
description |
NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis.
Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/ |
NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis.
Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas |
|
| 2022-03-09 14:22:03 |
Sujith Pandel |
information type |
Private |
Public |
|
| 2022-03-09 14:30:06 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2022-04-21 00:49:26 |
Michael Reed |
summary |
Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 |
[SRU] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 |
|
| 2022-04-21 00:51:24 |
Michael Reed |
description |
NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis.
Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas |
[Impact]
NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis.
Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas
[Fix]
1. Update kernel with TP8010 kernel patches:
a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907
b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0
[Test Case]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches |
|
| 2022-04-21 00:52:58 |
Michael Reed |
description |
[Impact]
NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis.
Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas
[Fix]
1. Update kernel with TP8010 kernel patches:
a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907
b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0
[Test Case]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches |
[Impact]
NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis.
Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas
[Fix]
1. Update kernel with TP8010 kernel patches:
a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907
b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0
c.
nvme: add CNTRLTYPE definitions for 'identify controller
https://lore.kernel.org/all/66FC4F03-ED5C-4727-BA94-C23DAF7D6D76@oracle.com/
[Test Case]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches |
|
| 2022-04-21 00:54:39 |
Michael Reed |
linux (Ubuntu Jammy): assignee |
|
Michael Reed (mreed8855) |
|
| 2022-04-22 13:44:48 |
Michael Reed |
description |
[Impact]
NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis.
Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas
[Fix]
1. Update kernel with TP8010 kernel patches:
a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907
b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0
c.
nvme: add CNTRLTYPE definitions for 'identify controller
https://lore.kernel.org/all/66FC4F03-ED5C-4727-BA94-C23DAF7D6D76@oracle.com/
[Test Case]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches |
[Impact]
NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis.
Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas
[Fix]
1. Update kernel with TP8010 kernel patches:
a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907
b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0
c.
nvme: add CNTRLTYPE definitions for 'identify controller
https://lore.kernel.org/all/66FC4F03-ED5C-4727-BA94-C23DAF7D6D76@oracle.com/
[Test Case]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches_2 |
|
| 2022-06-14 01:37:06 |
Michael Reed |
description |
[Impact]
NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis.
Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas
[Fix]
1. Update kernel with TP8010 kernel patches:
a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907
b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0
c.
nvme: add CNTRLTYPE definitions for 'identify controller
https://lore.kernel.org/all/66FC4F03-ED5C-4727-BA94-C23DAF7D6D76@oracle.com/
[Test Case]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches_2 |
[Impact]
NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis.
Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas
[Fix]
1. Update kernel with TP8010 kernel patches:
a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907
b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0
c.
nvme: add CNTRLTYPE definitions for 'identify controller
https://lore.kernel.org/all/66FC4F03-ED5C-4727-BA94-C23DAF7D6D76@oracle.com/
[Test Case]
1. Test NVMe/TCP initiator support with the kernel
2. Create nvme
3. Connect and mount the luns
4. Complile and test libnvme and nvme-stas packages from github
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches_2 |
|
| 2022-06-21 21:19:44 |
Michael Reed |
description |
[Impact]
NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis.
Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas
[Fix]
1. Update kernel with TP8010 kernel patches:
a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907
b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0
c.
nvme: add CNTRLTYPE definitions for 'identify controller
https://lore.kernel.org/all/66FC4F03-ED5C-4727-BA94-C23DAF7D6D76@oracle.com/
[Test Case]
1. Test NVMe/TCP initiator support with the kernel
2. Create nvme
3. Connect and mount the luns
4. Complile and test libnvme and nvme-stas packages from github
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches_2 |
[Impact]
NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis.
Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas
[Fix]
1. Update kernel with TP8010 kernel patches:
a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907
b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0
c.
nvme: add CNTRLTYPE definitions for 'identify controller
https://lore.kernel.org/all/66FC4F03-ED5C-4727-BA94-C23DAF7D6D76@oracle.com/
[Test Case]
1. Test NVMe/TCP initiator support with the kernel
2. Create nvme
3. Connect and mount the luns
4. Complile and test libnvme and nvme-stas packages from github
[Where problems could occur]
Regression risk for these patches are low
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches_2 |
|
| 2022-06-21 21:30:33 |
Michael Reed |
description |
[Impact]
NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis.
Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas
[Fix]
1. Update kernel with TP8010 kernel patches:
a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907
b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0
c.
nvme: add CNTRLTYPE definitions for 'identify controller
https://lore.kernel.org/all/66FC4F03-ED5C-4727-BA94-C23DAF7D6D76@oracle.com/
[Test Case]
1. Test NVMe/TCP initiator support with the kernel
2. Create nvme
3. Connect and mount the luns
4. Complile and test libnvme and nvme-stas packages from github
[Where problems could occur]
Regression risk for these patches are low
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches_2 |
[Impact]
NVMe-oF suffers from a well-known discovery problem that fundamentally limits the size of realistic deployments. To address this discovery problem, the FMDS working group (within nvme.org) is working on two proposals that will allow NVMe-oF to be managed via a “network centric” provisioning process instead of an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP Network and will prevent an end-user from needing to manually configure the IP Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery Controller (CDC) and will allow end-users to manage connectivity from a single point of management on an IP Fabric by IP Fabric basis.
Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/ which now got pulled into upstream - https://github.com/linux-nvme/nvme-stas
[Fix]
1. Update kernel with TP8010 kernel patches:
a. https://git.infradead.org/git/nvme.git/commit/647b2e01fb2d3394090ed11d1b5238157c52f907
b. https://git.infradead.org/git/nvme.git/commit/de87c02ea9b4d93d1114b912b621ead81f6738e0
c.
nvme: add CNTRLTYPE definitions for 'identify controller
https://lore.kernel.org/all/66FC4F03-ED5C-4727-BA94-C23DAF7D6D76@oracle.com/
[Test Case]
1. Compile libnvme and nvme-stas packages from github using the kernel
with these patches.
2. Test libnvme and nvme-stas packages
[Where problems could occur]
Regression risk for these patches are low
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/nvme_tcp_patches_2 |
|
| 2022-07-11 10:36:15 |
Stefan Bader |
linux (Ubuntu Jammy): importance |
Undecided |
Medium |
|
| 2022-07-11 10:36:15 |
Stefan Bader |
linux (Ubuntu Jammy): status |
Incomplete |
Fix Committed |
|
| 2022-07-11 10:36:21 |
Stefan Bader |
linux (Ubuntu): status |
Incomplete |
Invalid |
|
| 2022-07-15 13:26:30 |
Ubuntu Kernel Bot |
tags |
|
verification-needed-jammy |
|
| 2022-07-18 06:42:00 |
Reshmi Aravind |
bug |
|
|
added subscriber Sheik Ajith Ali Mohammed Farook |
| 2022-07-19 11:28:07 |
Sheik Ajith Ali Mohammed Farook |
attachment added |
|
sosreport-linux-2022-07-19-5.15.0-43.46.tar.xz https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+attachment/5604036/+files/sosreport-linux-2022-07-19-5.15.0-43.46.tar.xz |
|
| 2022-07-19 12:27:44 |
Sujith Pandel |
tags |
verification-needed-jammy |
verification-done-jammy |
|
| 2022-07-28 10:25:44 |
Launchpad Janitor |
linux (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2022-07-28 10:25:44 |
Launchpad Janitor |
cve linked |
|
2022-1652 |
|
| 2022-07-28 10:25:44 |
Launchpad Janitor |
cve linked |
|
2022-1679 |
|
| 2022-07-28 10:25:44 |
Launchpad Janitor |
cve linked |
|
2022-28893 |
|
| 2022-07-28 10:25:44 |
Launchpad Janitor |
cve linked |
|
2022-34918 |
|
| 2022-11-01 13:41:10 |
Michael Reed |
bug |
|
|
added subscriber Christian Ehrhardt |
| 2022-11-01 14:45:13 |
Michael Reed |
bug |
|
|
added subscriber Matthieu Clemenceau |
| 2023-01-31 15:31:03 |
Michael Reed |
bug |
|
|
added subscriber Andrey Grebennikov |
