Project

General

Profile

Actions
Copy link

Feature #63344

open

Set and manage nvmeof gw - controller ids ranges

Added by Aviv Caro 6 months ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
v19.0.0
% Done:

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

Each nvmeof gw which is deployed should get a unique range of controller ids. The controller id is a number between 1..65519. We will set a range of 4k ids by default for every GW that we deploy. So for example the first GW should get 1..4096, the second GW should get 4097..8192, and so on. If we get up to 61400 (15 GWs), we should fail any attempt to deploy more GWs. If any of the GW are removed, we should manage the deallocated free ranges and provide it to newly deployed GWs.
The range for each GW is set in the ceph-nvmeof.conf file, under [gateway] section. The fields are:
- min_controller_id
- max_controller_id

Actions
Copy link
 #1

Updated by Aviv Caro 6 months ago

The ranges fields should also be configurable via spec file.

Actions
Copy link
 #2

Updated by Aviv Caro 6 months ago

Another change to this request. By default the ceph adm should set 2K ids per GW. I.e. GW 1 will get 1..2048, GW 2 will get 2049..4096, ... this will allow 31 GWs.
This min/max controller ids fields should be configurable via spec file.

Actions
Copy link
 #3

Updated by Aviv Caro 5 months ago

This is no longer needed. We will manage the controller ids ranges from the nvmeof monitor.

Actions
Copy link

Also available in: Atom PDF