#1126 SMF: Implementer-names must be re-used.

[Hrishikesh]

changeset : 5697
Setup : 4 nodes cluster with SLES 64bit.

Problem:

Campaign object DN with more than 255 chars is created using immcfg.
Upon executing the campaign, after starting campaign thread, saImmOiImplementerSet DN=safSmfCampaign=campaignroc..... , returned ERR_LIBRARY saying Implementer name too long, size: 395 max:255.

With ticket #930, Longer DNs in SMF are supported, and Campaign object name is of type SaNameT.

[Robert Apanowicz]

Currently IMM does not support object implementer names longer then 255.
SMF needs to handle long OI names when IMM supports them.

[Anders Bjornerstedt]

This is an enhancement ticket on SMF .. apaprently.

The enhancement SMF I suggest should implement is to not use such long
implementer-names.

Does SMF run several campaigns in paralell ?
Is that why SMF needs a separate OI (unique OI name) for each such
concurrenlty existing campaign ?

/AndersBj

[Anders Bjornerstedt]

Changing this to a defect.

Implementer names are not discarded by the immsv. This is clearly
documented in both the IMMSV_PR.doc and the immsv README.

Thus using an obviously transient name such as the DN for a campaign
is a design error.

Every new campaign will add a new implementer-name that is only used
during the campaign and thereafter just wastes memory in the imm server.
Implementer-names are cleared at a cluster restart but that is not any
"solution".

The SMF design needs to be changed so that a re-usable implementername
is used, i.e. where the campaign-id is not part of the name.
Something like 'saSmfCampaign'

[Ingvar Bergström]

changeset: 6448:f3f0141f63cf
tag: tip
user: Robert Apanowicz robert.apanowicz@ericsson.com
date: Wed Mar 04 09:06:11 2015 +0100
summary: smf: implementer names reused [#1126]