[LU-13055] add ability for named Changelog consumers

• Type: Improvement
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.12.8, Lustre 2.15.0
• Assignee: Mikhail Pershin
• Reporter: Andreas Dilger

Description

Currently Lustre Changelog consumers are always named e.g. "cl1" or "cl14". It would be useful to be able to declare the changelog username (e.g. "cl-rbh" or "cl-audit") so that it is clear who the Changelog users are, and to avoid duplicate changelog registrations. Otherwise, it can happen that the original Changelog user registration can be lost, and the application registers a new user, and the old user causes the Changelog records to accumulate.

Issue Links

• is duplicated by: LU-8517 Changelog Users
• is duplicated by: LU-13338 add changelog mask per registered user
• is related to: LU-14699 changelog garbage collection is too lax
• is related to: LU-16268 per-server changelog mask change doesn't change effective mask in some cases
• is related to: LU-13338 add changelog mask per registered user

Comments

[Gerrit Updater]

"Oleg Drokin <[e-mail]>" merged in patch https://review.whamcloud.com/43710/
Subject: LU-13055 mdd: don't assert on unknown changelog lrh_type
Project: fs/lustre-release
Branch: b2_12
Current Patch Set:
Commit: 7759078c2be6df278bcdfab3eced738496f87331

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/44022/
Subject: LU-13055 doc: update changelog manpages
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 393885c027793d27ec948fd4fccb47aa530d2bf8

[Gerrit Updater]

Mike Pershin ([e-mail]) uploaded a new patch: https://review.whamcloud.com/44404
Subject: LU-13055 changelog: use default mask if server has no mask
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 17994d3fd5f294931ab30289c0dd565d08fb89ec

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/43380/
Subject: LU-13055 mdd: per-user changelog names and mask
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: a15eb4f13224e148810015896101b2950c85adff

[Gerrit Updater]

Mike Pershin ([e-mail]) uploaded a new patch: https://review.whamcloud.com/44022
Subject: LU-13055 doc: update changelog manpages
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 7bdb0af8f93a70ebf7f465da6c0ca49109aae723

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/43741/
Subject: LU-13055 libcfs: allow comma-separated masks
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 6b6fde1026311a28595ea43af56392ca6ad24d79

[Gerrit Updater]

Mike Pershin ([e-mail]) uploaded a new patch: https://review.whamcloud.com/43892
Subject: LU-13055 mdd: make current changelog mask writable
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 11e30ad4770811df392870e09a92dda022574ee6

[Gerrit Updater]

Andreas Dilger ([e-mail]) uploaded a new patch: https://review.whamcloud.com/43741
Subject: LU-13055 libcfs: allow comma-separated masks
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 17ed95152ff513dcfe4c1a8f36e66b8bfeeba895

[Gerrit Updater]

Mike Pershin ([e-mail]) uploaded a new patch: https://review.whamcloud.com/43710
Subject: LU-13055 mdd: don't assert on unknown changelog lrh_type
Project: fs/lustre-release
Branch: b2_12
Current Patch Set: 1
Commit: 1259811054a0e41f7fe646e8ad05307d693549f7

[Mikhail Pershin]

Patch is updated. For now name uniqueness is not provided, if you think it must be - let me know. The another patch for b2_12 branches is on its way to provide better compatibility during downgrade

[Mikhail Pershin]

well, I was asking mostly because having unique names means changelog scan for all registered names upon new user registration, while right now the only ID is increased. That would require patch modification.

Another problem I have right now is backward compatibility. New name format like 'cl$ID-$NAME' means that our scripts and any other one on customer side will get changelog user name in that format from the new server and later call to 'lfs changelog_clear' would return error because of sscanf() format in chgl_write(). That is not problem to change it or 'lfs' to skip '-$NAME' addition and still use cl$ID part after all but that is client side changes which means old client is not compatible with a new server changelog names. I am not sure if a client wants to work with any name registered from other client, so probably that is not problem, but if it is problem then I have no good solution except compatibility patch to an older Lustre client