[gpfsug-discuss] Samba (rid) -> CES (autorid) migration

[Fey, Christian]

Hi all,

I'm just doing a migration from a gpfs cluster with samba/ctdb to CES protocol nodes. The old ctdb cluster uses rid as idmap backend. Since CES officially supports only autorid, I tried to choose the right values for the idmap ranges / sizes to get the same IDs but was not successful with this.

The old samba has a range assigned for their Active directory (idmap config XYZ : range = 1000000-1999999)

My idea was to set autorid to the following during mmuserauth create:

idmap config * : backend = autorid
idmap config * : range = 200000-2999999
idmap config * : rangesize = 800000

With that it should use the first range for the builtin range and the second should then start with 1000000 like in the old rid config.

Sadly, the range of the domain is the third one:

/usr/lpp/mmfs/bin/net idmap get ranges
RANGE 0: ALLOC
RANGE 1: S-1-5-32
RANGE 2: S-1-5-21-123456789-123456789-123456789

Does anyone have an idea how to fix this, maybe in a supported way and without storing the IDs in the domain?

Further on, does anyone use rid as backend, even if not officially supported? Maybe we could file a RPQ or sth. Like this.


Mit freundlichen Grüßen / Best Regards

Christian Fey


SVA System Vertrieb Alexander GmbH
Borsigstraße 14
65205 Wiesbaden

Tel.: +49 6122 536-0
Fax: +49 6122 536-399
E-Mail: christian.fey at sva.de<mailto:christian.fey at sva.de>
http://www.sva.de


Geschäftsführung: Philipp Alexander, Sven Eichelbaum
Sitz der Gesellschaft: Wiesbaden
Registergericht: Amtsgericht Wiesbaden, HRB 10315

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170511/3657ed91/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5467 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170511/3657ed91/attachment-0001.bin>